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
Active-Active disaster recovery configuration
Once the catalog replication is configured, you can use site specific backup policies to perform local backup and use duplication policies to replicate backup images to remote cluster for protection against site outage. The clients communicate with the primary server on the primary site for sending metadata and communicate with media servers available on local cluster for sending backup data. The clients that are located at the primary site should use the local STU available at the primary site for backup and use the remote site's STU for duplication. Similarly, the clients that are located at the secondary site should use the local STU available at the secondary site for backup and use the remote site's STU for duplication. This way, it is ensured that duplications are performed across the sites for local backups. After disaster recovery configuration, the STUs of both the sites are always available for backups and duplications. Default SLPs are created as a template to configure backups and duplications at each site. The NetBackup administrator can use the default SLPs or can create new SLPs based on the template to perform backup and duplication.
Active-Active disaster configuration can be done from the NetBackup primary server using the web UI or the NetBackup Java GUI.
When any disaster happens, such as the primary site goes down for some reason, the clients at the primary site will not be able to continue the backups at the primary site as the local STU will not be available. The clients at the secondary site will also not be able to perform duplications as the remote STU will not be available for duplications. The backup jobs for primary site clients will fail or remain in waiting state for the STU to become available. The duplications jobs from secondary site clients will also fail or remain in waiting state for the STU to become available. The same situation arises when the secondary site is down due to any disaster.
When any disaster happens at a primary site, the secondary site is the only available site and must become the primary site so that the NetBackup primary server is available for the clients and pending jobs can be resumed or restarted. The takeover operation needs to be performed to make the secondary site as the primary site. Once the site becomes primary, the duplication jobs of old primary site are resumed/restarted and completed. The clients at secondary site continue to perform backup as the local STU is available for backups, but duplication jobs will remain in failed/waiting state.
Note:
The NetBackup administrator can make the backup storage as the new primary site's STU until the old primary site is available so that the client backup jobs of the old primary site can be completed. This can be done by making the primary site's SLPs to point to the new primary site's STU as backup storage.
Important: When the site role changes, the clients residing in domains other than the NetBackup Flex Scale disaster recovery domain may be required to update the host entries in the NetBackup configuration to connect to the media servers of the site.
If disaster recovery is configured and the primary site requires maintenance or updates, it can be switched to the role of secondary site using migrate operation. When the migrate operation is performed, the primary site becomes the secondary site and the secondary site becomes the primary site without affecting the backup and duplication jobs of the client. The NetBackup administrator does not have to change the SLPs since both the sites are up and the NetBackup primary service is also available. The clients at both sites will continue to do backups (to the local site STU) and duplication (to the remote site STU).