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
- Backing up data to Data Domain storage
- 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 the Fibre Channel ports
- Requirements
- Enabling BOM (Bill of Materials) configuration for Fibre Channel
- Assigning Fibre Channel ports
- Discovering attached devices
- Rescanning Fibre Channel cards
- Cleaning Fibre Channel ports
- Unassigning Fibre Channel ports
- Viewing details about the Fibre Channel ports
- Disabling BOM (Bill of Materials) configuration for Fibre Channel
- Managing hardware vendor packages
- Updating credentials for HPE iLO administrator users
- User management
- NetBackup Flex Scale network management
- About network management
- Modifying DNS settings
- Configuring MTU on public interfaces
- Configuring the console FQDN
- 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
- About the security meter
- 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
- Configuring isolated recovery environment (IRE)
- Configuring multifactor authentication
- About multifactor authentication
- Considerations before configuring multifactor authentication
- Configuring multifactor authentication for your user account
- Disabling multifactor authentication for your user account
- Enforcing multifactor authentication for all users
- Configuring multifactor authentication for your user account when it is enforced in the cluster
- Resetting multifactor authentication for a user
- Single Sign-On (SSO)
- 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 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
- Replacement procedure for SFP port
- Replacement procedure for chassis
- Replacement procedure for a hard disk drive
- Replacement procedure for a Fibre Channel card for a cluster node
- Replacement procedure for a Fibre Channel card for a node that is not in a cluster
- Appendix B. Configuring NetBackup optimized duplication
- Appendix C. Disaster recovery terminologies
- Appendix D. Configuring Auto Image Replication
About site-based disaster recovery in NetBackup Flex Scale
The NetBackup Flex Scale provides a disaster recovery solution. The NetBackup catalog is replicated using Veritas Volume Replicator (VVR). NetBackup optimized duplication is used to replicate the backup images.
Protect NetBackup catalog and backup data against a site failure.
Support for dual site and single NetBackup domain configuration.
Mechanism to takeover and migrate the primary service from one site to another.
Configuration, management, failover, and migration using RESTful APIs and GUI.
Asynchronous continuous replication for NetBackup catalog and backup data.
The NetBackup Flex Scale primary site and the secondary site should be in the same NetBackup domain.
At any given time, the NetBackup primary service is active on one site only. The media service is active on both the sites.
Clients on the primary site backup to the primary site and then the backup images are duplicated to the secondary site.
You can configure disaster recovery on an active NetBackup Flex Scale Appliance (which has existing backup data and acts as the primary site).
The secondary site that is added must be a freshly installed or configured NetBackup Flex Scale Appliance. Else, any data present on the secondary site is lost when you set up disaster recovery.
The node names and the cluster names in the primary and secondary sites should not be the same.
As part of the initial configuration of the secondary site, only the primary data network should be configured on the secondary site. Secondary data network should not be configured on the secondary site before disaster recovery configuration.
As part of initial configuration pre-requisites, the secondary site must be in Normal lockdown mode only. The primary site can have any lockdown mode configured. After disaster recovery configuration, you can configure any lockdown mode on any of the clusters as per the lockdown mode guidelines.
You can choose to automatically update the NetBackup primary service host name mapping on the DNS servers that are configured with valid credentials. If you have not configured the DNS servers to be updated automatically then ensure that you have updated the DNS entries of the NetBackup primary service FQDNs to resolve to the secondary site.
Primary site can have the secondary data network configured before disaster recovery configuration.
While configuring disaster recovery, ensure that you configure ECA on the site that is going to act as the primary site.
If ECA is deployed on the primary site before adding the secondary site, then you must redeploy ECA from the primary site after disaster recovery configuration is complete.
After disaster recovery is configured between two sites, disaster recovery configuration cannot be removed.
Note:
Disaster recovery can also be configured if one or both the clusters are in non-DNS configurations.
If disaster recovery is configured:
The cluster from which the disaster recovery configuration is initiated is called the primary site and other cluster is called the secondary site.
If you want to add a node to the cluster, See Considerations for adding a node when disaster recovery is configured.
If you want to configure VLAN, See Support for multiple VLAN when disaster recovery is configured.
If disaster recovery is configured in a non-DNS environment, ensure that you add the NetBackup Client host entries in at both sites.
Note:
If a cloud LSU is present before the entire cluster on which the NetBackup Flex Scale software resides is destroyed, refer to the About the disaster recovery for cloud LSU section in the Veritas NetBackup Deduplication Guide.
Note:
Disaster recovery can be configured between a cluster with HPE model 5551 and a cluster with HPE model 5561.