Veritas NetBackup™ Flex Scale Administrator's Guide
- Product overview
- Viewing information about the NetBackup Flex Scale cluster environment
- NetBackup Flex Scale infrastructure management
- User management
- Considerations for managing NetBackup Flex Scale users
- Adding users
- Changing user password
- Removing users
- Modifying user roles
- Considerations for configuring AD/LDAP
- Configuring AD server for Universal shares and Instant Access
- Configuring AD/LDAP servers for NetBackup services
- Configuring additional AD/LDAP servers for managing NetBackup services/Universal Shares/Instant Access
- Configuring AD/LDAP servers on clusters deployed with only media servers
- Directory services and certificate management
- Region settings management
- About NetBackup Flex Scale storage
- About Universal Shares
- Cloud bucket support for NetBackup Flex Scale
- Node and disk management
- NetBackup Flex Scale network cabling
- Adding a node to the cluster using the NetBackup Flex Scale web interface
- Adding a node using the REST APIs
- Replacing a node in a cluster
- Starting and stopping nodes
- Rebooting a node
- Adding an excluded node to the cluster
- Replacing a disk
- Adding an excluded disk to the cluster
- Viewing the disk sync status
- Viewing disk details
- Viewing node details
- Switching management console to another cluster node
- License management
- Stopping NetBackup service containers
- Starting NetBackup service containers
- Managing hardware vendor packages
- User management
- NetBackup Flex Scale network management
- About network management
- Modifying DNS settings
- About bonding Ethernet interfaces
- Bonding operations
- Configuring NetBackup Flex Scale in a non-DNS environment
- Data network configurations
- Choosing the correct input method for data network configuration
- Network configuration on plain device (eth5)
- Network configuration on VLAN (eth5)
- Network configuration on bonded interfaces (bond0 on eth5 and eth7)
- VLAN on bond of eth5 and eth7 (bond0)
- Network configuration on management interface (eth1)
- Network configurations for adding a partial data network
- Support for multiple VLAN when disaster recovery is configured
- Configuring static routes on a NetBackup Flex Scale cluster
- NetBackup Flex Scale infrastructure monitoring
- Resiliency in NetBackup Flex Scale
- EMS server configuration
- Site-based disaster recovery in NetBackup Flex Scale
- About site-based disaster recovery in NetBackup Flex Scale
- Configuring disaster recovery using GUI
- Clearing the host cache
- Automated NetBackup SLP management
- DNS key management
- Managing disaster recovery using GUI
- Performing disaster recovery using RESTful APIs
- Active-Active disaster recovery configuration
- NetBackup optimized duplication using Storage Lifecycle Policies
- NetBackup Flex Scale security
- STIG overview for NetBackup Flex Scale
- FIPS overview for NetBackup Flex Scale
- Managing the login banner
- Changing the password policy
- Support for immutability in NetBackup Flex Scale
- Authenticating users using digital certificates or smart cards
- About system certificates on NetBackup Flex Scale
- Deploying external certificates on NetBackup Flex Scale
- Troubleshooting
- Services management
- Audit logs
- Collecting logs for cluster nodes
- Troubleshooting NetBackup Flex Scale issues
- If cluster configuration fails (for example because an IP address that was already in use is specified) and you try to reconfigure the cluster, the UI displays an error but the configuration process continues to run
- Validation error while adding VMware credentials to NetBackup
- NetBackup Web UI incorrectly displays some NetBackup Flex Scale processes as failed
- Unable to create BMR Shared Resource Tree (SRT) on NetBackup Flex Scale Appliance
- NetBackup configuration files are not persistent across operations that require restarting the system
- Appendix A. Maintenance procedures for HPE servers
- Replacement procedure for a chassis fan
- Replacement procedure for power supply
- Replacement procedure for a single OS disk
- Replacement procedure for both OS disks on the management console node
- Replacement procedure for both OS disks on a non- management console node
- Replacement procedure for NVMe disks (SSDs)
- Replacement procedure for RAID controller
- Replacement procedure for an Integrated Lights-Out (iLO) port
- Replacement procedure for quad-port NIC
- Procedure for memory expansion (DIMMs)
- Replacement procedure for memory (DIMMs)
- Replacement procedure for Mellanox port
- Appendix B. Configuring NetBackup optimized duplication
- Appendix C. Disaster recovery terminologies
- Appendix D. Configuring Auto Image Replication
Automated NetBackup SLP management
When you configure primary service replication between two NetBackup Flex Scale clusters, the NetBackup primary service catalog data is replicated between the clusters. You have to configure NetBackup Storage Lifecycle Policies (SLPs) for backup policies and protection plans to duplicate data between the two NetBackup Flex Scale clusters. You also must update the SLPs, backup policies, and protection plans if there is a cluster fault and the replication primary role needs to be changed to failover the NetBackup primary service.
NetBackup Flex Scale supports a mechanism to update the SLPs, backup policies, and protection plans automatically when changing the replication roles after a cluster fault. However, this functionality works only if the SLPs, backup policies and protection plans are using the default Media Server Deduplication Pool storage unit (STU) that is created with the NetBackup Flex Scale cluster configuration. This STU is named stu_<storage_server_fqdn>. If you use the default STU as storage target for your SLPs, backup policies and protection plans, you can select the option when changing replication roles.
Note:
The option is available only when the current replication primary cluster is down and the operation is performed on the replication secondary.
If you select the option, the following changes are performed on the NetBackup primary server:
Backup policies and protection plans that are not using SLPs and are using default STU as backup target:
If the STU is from the faulted NetBackup Flex Scalecluster, it is updated to use the default STU on the new replication primary.
Backup policies and protection plans that are using SLPs with default STU as backup and duplication target:
If the STU used by the backup target is from the faulted NetBackup Flex Scale cluster, it is updated to use the default STU on the new replication primary. The duplication target is updated to use the STU from the faulted NetBackup Flex Scale cluster.
Backup policies and protection plans that are using replication template SLPs:
The following SLP templates are created while configuring primary service replication.
<cluster1>_7days_to_<cluster2>_7days
<cluster1>_30days_to_<cluster2>_30days
<cluster2>_7days_to_<cluster1>_7days
<cluster2>_30days_to_<cluster1>_30days
Here, the first cluster name in the SLP is the backup target and the second cluster name in the SLP is the duplication target. The number of days reflects the retention period of the backup copy on each cluster.
If the backup policies and protection plans are using the template SLPs from cluster1 to cluster2, they are updated to use the corresponding template SLP in the reverse direction if cluster1 is faulted and vice versa.
All of these changes are applied only to newly created NetBackup jobs. Existing, running, and queued backup jobs continue to use the previous backup and duplication targets.
The behavior of the automatic option is to make sure that backup jobs continue to function after a cluster fault. The duplication is reversed to let the backup images duplicated to the remote cluster when the cluster fault is restored.
All the changes to SLPs, backup policies, and protection plans are reverted back to their original configuration when the cluster fault is restored and the original replication primary automatically gets converted as the replication secondary.