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
- Directory services and certificate management
- Region settings management
- About NetBackup Flex Scale storage
- About Universal Shares
- Creating a Protection Point for a Universal Share
- Node and disk management
- License management
- NetBackup Flex Scale network management
- About network management
- Modifying DNS settings
- About bonding Ethernet interfaces
- 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
- 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
Performing a recovery of the catalog file system using REST APIs
You can use REST APIs for the recovery of primary service catalog file system from the checkpoints. The REST API calls should be made in the following order:
Get the list of checkpoints for the primary service catalog file system. This API returns a list of all the available checkpoints for the primary catalog file system. The checkpoints can be used to recover the data.
GET /api/appliance/v1.0/netbackup/checkpoints URI : /api/appliance/v1.0/netbackup/checkpoints Type : GET Response Body: { "links": { "self": { "href": "/api/appliance/v1.0/netbackup/checkpoints" } }, "data": [ { "type": "netbackup", "id": "1", "links": { "self": { "href": "/api/appliance/v1.0/netbackup/checkpoints/ checkpoint1" } } } ] }The checkpoint name which is returned by this API should be passed as input to the API which is called to restore the catalog.
Validate a checkpoint. This API validates the checkpoint by creating a new checkpoint from the selected checkpoint and runs the NetBackup database validation on the newly created checkpoint. After validation completes the new checkpoint can be used for restore.
POST /api/appliance/v1.0/netbackup/checkpoints/restore-catalog/ {checkpointName} URI: /api/appliance/v1.0/netbackup/checkpoints/restore-catalog/{ checkpointName} Type : POST Input Parameter for Request : Checkpoint name Response: { "taskId": "string", "message": "string" }This is an asynchronous API and it returns a task ID when API execution is successful. You can find the execution status and details by providing this taskID as input in the GET {taskId} API. The task is also visible in the icon in the top navigation bar in the GUI.
Restore the data to the primary service catalog file system. This API restores the data (from the checkpoint that is created in the previous step) to the primary service catalog file system.
POST /api/appliance/v1.0/netbackup/checkpoints/sync-catalog URI : /api/appliance/v1.0/netbackup/checkpoints/sync-catalog Type : POST Input Parameters : None Response : { "taskId": "string", "message": "string" }This is an asynchronous API and it returns a task ID when API execution is successful. You can find the execution status and details by providing this taskID as input in the GET {taskId} API. The task is also visible in the icon in the top navigation bar in the GUI.