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
Adding a node using the REST APIs
You can use REST APIs to add a node to an existing cluster.
You can find the RESTful APIs at https://ManagementServerIPorFQDN:14161/swagger/infra/v1.0/ where ManagementServerIPorFQDN is the public IP address or FQDN that you specified for the NetBackup Flex Scale management server and API gateway during the cluster configuration.
If you are using IPv6 addresses, use the following URL syntax:https://[ManagementServerIP]:14161/swagger/infra/v1.0
See Working with NetBackup Flex Scale APIs. for more details.
Before you use the APIs, power on the node and install the NetBackup Flex Scale ISO image on the node that you want to add to the cluster. For more details, see the NetBackup Flex Scale Installation and Configuration Guide. After the ISO is installed, perform a factory reset to reset the node to its default factory settings. Ensure that the management network interface (eth1) of the node is not configured with the management IP address.
You must format the disks and ensure that no data is present on the disks; else the add node operation will fail.
Use the following APIs in the sequence listed below to add a node. For more details about the APIs, see the Veritas NetBackup Flex Scale APIs on SORT.
Note:
You can add only one node at a time using REST APIs. Use the NetBackup Flex Scale web interface to add multiple nodes simultaneously.
- Authenticate the user. The user must be assigned an Appliance Administrator role.
POST /api/appliance/v1.0/authentication/login
Specify the user name and password. The API returns a token. Copy the generated token and specify in the following format:
Authorize: Bearer generated token
You can also generate an API key that is valid for 10 years after the user is authenticated successfully:
POST /api/appliance/v1.0/api-keys
After the API key is generated, generate the token again using the following API and by specifying the user name and the generated API key:
POST /api/appliance/v1.0/authentication/login
Note:
If both the password and the API key is provided with the user name to generate the token, the API considers only the password and generates the token.
- Discover all the spare nodes that are in the same private network as the existing cluster.
GET /api/appliance/v1.0/storage/new-nodes
- Get details of a particular node that was discovered in step 1 by using its Avahi IP address.
GET /api/appliance/v1.0/storage/new-nodes/{ipAddress} - Synchronize the patch version on the cluster with the new node. All the patches that are installed on the cluster nodes are installed on the new node.
POST /api/appliance/v1.0/upgrade
With {"eebType": "normal"}: Payload for synchronizing patch upgrade version on new node with the cluster.
- Add the node to the cluster.
POST /api/appliance/v1.0/storage/nodes
- Rebalance the data across all the nodes to free space on the existing cluster nodes. Rebalancing spreads data evenly across the nodes by moving the data from existing nodes to the new node.
POST /api/appliance/v1.0/storage/rebalance
- Configure NetBackup on the newly added node.
POST /api/appliance/v1.0/netbackup/add
- Synchronize data EEBs on the cluster with the newly added node.
POST /api/appliance/v1.0/upgrade
With {"eebType": "data"}: Payload for synchronizing patch upgrade version on new node with the cluster.