NetBackup IT Analytics System Administrator Guide
- Introduction
- Preparing for updates
- Backing up and restoring data
- Best practices for disaster recovery
- Oracle database backups
- File system backups
- Oracle database: Cold backup
- Oracle database: Export backups
- Scheduling the oracle database export
- Oracle database: On demand backup
- Restoring the NetBackup IT Analytics system
- Import the Oracle database
- Manual steps for database import / export using data pump
- Monitoring NetBackup IT Analytics
- Accessing NetBackup IT Analytics reports with the REST API
- Defining NetBackup estimated tape capacity
- Automating host group management
- About automating host group management
- Task overview: managing host groups in bulk
- Preparing to use PL/SQL utilities
- General utilities
- Categorize host operating systems by platform and version
- Identifying a host group ID
- Move or copy clients
- Organize clients by attribute
- Move host group
- Delete host group
- Move hosts and remove host groups
- Organize clients into groups by backup server
- Merge duplicate backup clients
- Merge duplicate hosts
- Bulk load utilities
- Veritas NetBackup utilities
- Automate NetBackup utilities
- Organize clients into groups by management server
- Set up an inactive clients group
- Set up a host group for clients in inactive policies
- Set up clients by policy
- Set up clients by policy type
- IBM Tivoli storage manager utilities
- Set up clients by policy domain
- Set up clients by IBM Tivoli storage manager instance
- Scheduling utilities to run automatically
- Host matching identification for single-domain multi-customer environments
- Attribute management
- Attribute bulk load utilities
- Attribute naming rules
- Rename attributes before upgrading
- Load host attributes and values
- Load attributes and values and assign to hosts
- Load array attributes and values and assign to arrays
- Overview of application attributes and values
- Load application database attributes and values
- Load MS Exchange organization attributes and values
- Load LUN attributes and values
- Load switch attributes and values
- Load port attributes and values
- Load Subscription attributes and values
- Importing generic backup data
- Backup job overrides
- Managing host data collection
- System configuration in the Portal
- System configuration in the Portal
- System configuration: functions
- Navigation overview
- System configuration parameter descriptions: Additional info
- Anomaly detection
- Data collection: Capacity chargeback
- Database administration: database
- Host discovery: EMC Avamar
- Host discovery: Host
- Events captured for audit
- Custom parameters
- Adding/editing a custom parameter
- Portal customizations
- Configuring global default inventory object selection
- Restricting user IDs to single sessions
- Customizing date format in the report scope selector
- Customizing the maximum number of lines for exported reports
- Customizing the total label display in tabular reports
- Customizing the host management page size
- Customizing the path and directory for File Analytics database
- Configuring badge expiration
- Configuring the maximum cache size in memory
- Configuring the cache time for reports
- Performance profile schedule customization
- LDAP and SSO authentication for Portal access
- Change Oracle database user passwords
- Integrate with CyberArk
- Tuning NetBackup IT Analytics
- Working with log files
- About debugging NetBackup IT Analytics
- Turn on debugging
- Database logging
- Portal and data collector log files - reduce logging
- Database SCON logging - reduce logging
- Refreshing the database SCON log
- Logging user activity in audit.log
- Logging only what a user deletes
- Logging all user activity
- Data collector log files
- Data collector log file organization
- Data collector log file naming conventions
- General data collector log files
- Find the event / meta collector ID
- Portal log files
- Database log files
- Installation / Upgrade log files
- Defining report metrics
- SNMP trap alerting
- SSL certificate configuration
- SSL certificate configuration
- SSL implementation overview
- Obtain an SSL certificate
- Update the web server configuration to enable SSL
- Configure virtual hosts for portal and / or data collection SSL
- Enable / Disable SSL for a Data Collector
- Enable / Disable SSL for emailed reports
- Test and troubleshoot SSL configurations
- Create a self-signed SSL certificate
- Configure the Data Collector to trust the certificate
- Keystore file locations on the Data Collector server
- Import a certificate into the Data Collector Java keystore
- Keystore on the portal server
- Add a virtual interface to a Linux server
- Add a virtual / secondary IP address on Windows
- Portal properties: Format and portal customizations
- Introduction
- Configuring global default inventory object selection
- Restricting user IDs to single sessions
- Customizing date format in the report scope selector
- Customizing the maximum number of lines for exported reports
- Customizing the total label display in tabular reports
- Customizing the host management page size
- Customizing the path and directory for file analytics database
- Configuring badge expiration
- Configuring the maximum cache size in memory
- Configuring the cache time for reports
- Configuring LDAP to use active directory (AD) for user group privileges
- Data retention periods for SDK database objects
- Data retention periods for SDK database objects
- Data aggregation
- Find the domain ID and database table names
- Retention period update for SDK user-defined objects example
- SDK user-defined database objects
- Capacity: default retention for basic database tables
- Capacity: default retention for EMC Symmetrix enhanced performance
- Capacity: Default retention for EMC XtremIO
- Capacity: Default retention for Dell EMC Elastic Cloud Storage (ECS)
- Capacity: Default retention for Windows file server
- Capacity: Default retention for Pure Storage FlashArray
- Cloud: Default retention for Amazon Web Services (AWS)
- Cloud: Default retention for Microsoft Azure
- Cloud: Default retention for OpenStack Ceilometer
- Configure multi-tenancy data purging retention periods
- Troubleshooting
- Appendix A. Kerberos based proxy user's authentication in Oracle
- Appendix B. Configure TLS-enabled Oracle database on NetBackup IT Analytics Portal and data receiver
- About Transport Layer Security (TLS)
- TLS in Oracle environment
- Configure TLS in Oracle with NetBackup IT Analytics on Linux in split architecture
- Configure TLS in Oracle with NetBackup IT Analytics on Linux in non-split architecture
- Configure TLS in Oracle with NetBackup IT Analytics on Windows in split architecture
- Configure TLS in Oracle with NetBackup IT Analytics on Windows in non-split architecture
- Configure TLS in user environment
- Appendix C. NetBackup IT Analytics for NetBackup on Kubernetes and appliances
Organize clients into groups by management server
This utility enables you to create a hierarchy of management servers and links all clients that are members of the management server into the respective host group. For example, in a NetBackup environment if you have two primary servers called primary 1 and primary 2, this utility creates host groups named primary 1 and primary 2 and links the primary server's clients into the corresponding group. Two versions of this utility are available:
Move clients into a Primary Server Group:
Move clients into a Primary Server Group & Exclude the Policy Client & Cascade to Sub-groups:
Basic Usage with 4 Parameters | execute nbu_adaptor_pkg.moveClientsIntoPrimaryGroups ( <source_group_id>,<destination_group_id>, <move_clients>, <latest_primary_only> ); Example: exec nbu_adaptor_pkg.moveClientsIntoPrimaryGroups(300000, 300010, 1, 1); source_group_id is the internal group ID of the host group hierarchy to traverse. destination_group_id is the group ID in which the host group for your primary servers groups will be created. Create a host group under source_group_id called Primaries or Management 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 primary server, if a host group exists anywhere under the source group hierarchy with the name of the primary 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, the routine will create (if it does not exist already) a group called "NetBackup" under the Source group ID. It then creates a host group called "Primary Servers" under the "NetBackup" group. move_clients If set to 0, the clients link into the respective host group and remain in their original host group location. If set to 1, all the clients move from the source host group and into the respective host groups. The utility processes and organizes all clients of the source group hierarchy into the target primary server grouping. However, if the move_clients flag is set to 1, the utility removes only clients in the top level source_group_id group--and those already organized in lower level sub-groups remain. latest_primary_only defaults to 0, but can be set to 1, indicating organization by the latest primary server. If a client is backed up by two primary servers, or if a client was backed up by primary server A in the past, but is now backed up by primary server B, setting this flag to true will result in the client being organized by the latest primary server. |
Usage with 6 Parameters | execute nbu_adaptor_pkg.moveClientsIntoPrimaryGroups ( <source_group_id>,<destination_group_id>, <cascade_source_group>, <move_clients>, <latest_primary_only>, <exclude_policy_client>); Example: exec moveClientsIntoPrimaryGroups(300000, 300010, 1, 1, 1, 0); source_group_id is the internal group ID of the host group hierarchy to traverse. destination_group_id is the group ID in which the new host group for your primary servers will be created. Create a host group under source_group_id called Primaries or Management 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 primary server, if a host group exists anywhere under the source group hierarchy with the name of the primary 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, the routine will create (if it does not exist already) a host group called "NetBackup" under the Source group ID. It then creates a host group called "Primary Servers" under the "NetBackup" host group. cascade_source_groupcan be set to 0= Do not include sub-groups, 1= Include sub-groups. Use cascade_source_group to find and re-sort all of the defined host groups that are under the source group. Use this parameter so that you do not have to move all of your clients to the top before re-sorting. move_clients If set to 0, the clients link into the respective host group and remain in their original host group location. If set to 1, all the clients move from the source group and into the respective management server host groups. The utility processes and organizes all clients of the source group hierarchy into the target primary server grouping. However, if the move_clients flag is set to 1, the utility removes only clients in the top-level source_group_id group--and those already organized in lower-level sub-groups remain. latest_primary_only defaults to 0, but can be set to 1, indicating organization by the latest primary server. If a client is backed up by two primary servers, or if a client was backed up by primary server A in the past, but is now backed up by primary server B, setting this flag to true will result in the client being organized by the latest primary server. exclude_policy_client defaults to 0, but can be set to 1, indicating that you want to organize the clients based on backups and exclude policy-based clients. If this flag is set to 0, the utility finds the clients that are backed up by the primary server and also clients that are in the policy that is controlled by the primary server. |