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
- About Universal Shares
- Node and disk management
- License management
- User management
- NetBackup Flex Scale network management
- Bonding operations
- Data network configurations
- NetBackup Flex Scale infrastructure monitoring
- Resiliency in NetBackup Flex Scale
- EMS server configuration
- Site-based disaster recovery in NetBackup Flex Scale
- Performing disaster recovery using RESTful APIs
- NetBackup Flex Scale security
- Troubleshooting
- Collecting logs for cluster nodes
- Troubleshooting NetBackup Flex Scale issues
- Appendix A. Configuring NetBackup optimized duplication
- Appendix B. Disaster recovery terminologies
- Appendix C. Configuring Auto Image Replication
Considerations for performing other operations when ECA is deployed
If ECA is deployed and you want to add a new node to the cluster:
Before starting an add node operation, generate a new certificate request which has the new node's storage FQDN as an additional SAN entry.
Upload the new certificate and then add the new node. Otherwise, the add node operation will fail.
If ECA is deployed on a cluster where disaster recovery is configured and you want to add a new node to the cluster:
The ECA has to be renewed on the primary irrespective of whether you add the new node on the primary or secondary cluster.
The new certificate must contain FQDN of the storage server of the node which is going to be added.
A new CSR has to be generated which contains the FQDN of the new storage server as a SAN entry. A new certificate is generated with the new CSR which is used for ECA deployment/renewal.