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
- Adding a node to the cluster using the NetBackup Flex Scale web interface
- License management
- Managing the Fibre Channel ports
- Requirements
- Managing hardware vendor packages
- User management
- NetBackup Flex Scale network management
- Bonding operations
- Data network configurations
- Network configuration on plain device (eth5)
- Network configuration on bonded interfaces (bond0 on eth5 and eth7)
- 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
- STIG overview for NetBackup Flex Scale
- FIPS overview for NetBackup Flex Scale
- Support for immutability in NetBackup Flex Scale
- Deploying external certificates on NetBackup Flex Scale
- Configuring multifactor authentication
- Single Sign-On (SSO)
- Appendix A. Maintenance procedures for HPE servers
- Appendix B. Configuring NetBackup optimized duplication
- Appendix C. Disaster recovery terminologies
- Appendix D. 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.