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
- 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
- Node and disk management
- License management
- 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
- 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
- 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
- Troubleshooting
- Services management
- Collecting logs for cluster nodes
- Checking and repairing storage
- 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. Configuring NetBackup optimized duplication
- Appendix B. Disaster recovery terminologies
- Appendix C. Configuring Auto Image Replication
Node and disk management
At a minimum, you must deploy four nodes in a cluster and can scale up to a maximum of sixteen nodes. All the nodes must have the same hardware and the same software version.
A cluster with up to five nodes provides resiliency of one node and a disk. The cluster can tolerate a loss of one node and a disk and continue to perform NetBackup jobs. A cluster with six or more nodes provides resiliency of two nodes, or two SSDs, or four HDDs. If the loss of cluster nodes is more than the supported resiliency, either due to node failure or nodes are stopped or shut down, the cluster goes in an inconsistent state. If a cluster is in an inconsistent state, check the NetBackup Flex Scale Release Notes to see if a related issue and the resolution is mentioned; else call Veritas Technical Support for assistance with resolving the inconsistent cluster state.
Replace a faulted node or disk in the cluster to recover from a node or a disk failure. Add a new node to the cluster to increase the usable cluster storage and compute resources. When you add a node or replace a faulted node, the NetBackup operations continue to run on the cluster nodes.