NetBackup IT Analytics System Administrator Guide
- Introduction
- Preparing for updates
- Backing up and restoring data
- Monitoring NetBackup IT Analytics
- Accessing NetBackup IT Analytics reports with the REST API
- Defining NetBackup estimated tape capacity
- Automating host group management
- Categorize host operating systems by platform and version
- Bulk load utilities
- Automate NetBackup utilities
- Scheduling utilities to run automatically
- Attribute management
- Importing generic backup data
- Backup job overrides
- Managing host data collection
- System configuration in the portal
- Custom parameters
- Performance profile schedule customization
- Configuring AD/LDAP
- Configuring single sign-on (SSO) using security assertion markup language (SAML)
- Change Oracle database user passwords
- Integrate with CyberArk
- Tuning NetBackup IT Analytics
- Working with log files
- Portal and data collector log files - reduce logging
- Data collector log file naming conventions
- Portal log files
- Defining report metrics
- SNMP trap alerting
- SSL certificate configuration
- Configure virtual hosts for portal and / or data collection SSL
- Keystore on the portal server
- Portal properties: Format and portal customizations
- Data retention periods for SDK database objects
- Troubleshooting
- Appendix A. Configure TLS-enabled Oracle database on NetBackup IT Analytics Portal and data receiver
Organize clients into groups by backup server
This utility can be used for any backup product, such as IBM Tivoli Storage Manager, Veritas Backup Exec, or HP Data Protector.
Description | This utility enables you to create a hierarchy of servers and links all clients that are members of a server into the respective host group. For example, in an IBM Tivoli Storage Manager environment if you have two IBM Tivoli Storage Manager servers called TSM1, TSM2, this utility creates two host groups, TSM1 and TSM2, and links the IBM Tivoli Storage Manager server's clients into the corresponding IBM Tivoli Storage Manager host group. |
Usage | execute common_package.moveClientsIntoServerGroups ( <source_group_id>,<destination_group_id>, <move_or_copy_flag>, <latest_server_only>); Example: exec common_package.moveClientsIntoServerGroups (300000, 300010, 1, 1), ; Where: source_group_id is the internal group ID of the group hierarchy to traverse. destination_group_id is the group ID in which host groups by management server will be created. Create a host group under source_group_id called <vendor_name> Servers and use the group ID of this new host group for the second parameter. See Identifying a host group ID. When you organize by server, if a host group exists anywhere under the source group hierarchy with the name of that server, the routine associates the clients with that folder and does not create a new folder under the destination folder. This association occurs whether you explicitly specify the destination folder or if the destination is NULL. However, if you pass a source folder that is at a lower level, the routine only checks for a folder under that hierarchy. If you specify NULL as the destination folder, the routine creates a host group under the source_group_id called Primary Servers. move_or_copy_flag can be set to 0=Link (copy) clients or 1=Move clients. If set to 0, the utility links the clients to their respective host groups and keeps the clients in their original group location. If set to 1, the utility moves all clients from the source host group and to their respective host groups. The utility processes and organizes all clients of the source group hierarchy into the target server grouping. However, if the move_or_copy flag is set to 1, the utility removes only clients in the top level source_group_id group--and does not remove those already organized in lower-level sub-groups. latest_server_only, when set to 1, indicates the last server to back up the client; otherwise, set this flag to 0. |