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
Configuring disaster recovery
The user has to invoke RESTful API calls to configure disaster recovery between the clusters. The NetBackup Flex Scale cluster that is to be used as the primary may already have backup data. Before you run the API, ensure that the NetBackup Flex Scale cluster is in healthy state. The NetBackup Flex Scale cluster that is used as secondary must be a freshly configured cluster. Any changes made after the initial configuration is lost, including any backup images.
For the list of ports that should be open, see Firewall and network port requirements section in the Veritas NetBackup™ Flex Scale Best Practices and Troubleshooting Guide on SORT.
To configure disaster recovery:
Four virtual IP addresses are required, two on each cluster in the data network. One set of IP addresses are used for VVR replication and another set of IP addresses are used for heartbeat between clusters.
The API call to set up disaster recovery is asynchronous. Once the primary site receives the call, it creates a task and returns a task ID. You can find the status of the replication setup by querying the task with the task ID using the following API:
GET /api/appliance/v1.0/tasks/{taskId}Run the API to configure disaster recovery by specifying the primary and secondary site parameters. This API should be executed on the primary site.
POST /api/appliance/v1.0/disaster-recovery
This API can be retried if you encounter any network or timeout failures during disaster recovery configuration. But, do not attempt to retry it if disaster recovery is already configured.
For more information, see the Veritas NetBackup Flex Scale APIs on SORT.
The API sets up replication of the NetBackup catalog using VVR. For replicating the NetBackup policies, use NetBackup optimized duplication (SLP).
See Configuring a Storage Lifecycle Policy for optimized duplication.