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 GUI
You can use the NetBackup Flex Scale GUI for the recovery of primary service catalog file system from the checkpoints.
The following operations can be performed using the GUI:
List the valid checkpoints for restore
Validate a checkpoint
Restore a checkpoint
You can list all the valid checkpoints for the primary service.
To list all the valid checkpoints
- Go to Settings > NetBackup catalog management.
- A screen with a calendar view gets displayed. Select a date in the calendar. The list of valid checkpoints for that date is displayed in tabular form.
Note:
The green dot below a date in the calendar indicates that there are valid checkpoints available for that date.
You can validate a specific checkpoint. For validation operation to be completed, the primary server services must be running in the cluster.
To validate a checkpoint
- From the list of checkpoints, click the kebab menu for a particular checkpoint. Click Validate to validate the checkpoint.
- A task is initiated in the GUI which can be used to track the status of the validate operation. Once the validate operation is completed, the status of the task changes accordingly.
You can restore a checkpoint. For the restore operation to be completed, the primary server services must be in the ONLINE state in the cluster.
To restore a checkpoint
- From the list of checkpoints, click on the kebab menu for a particular checkpoint. Click Restore to restore the checkpoint.
- A pop up window appears asking for confirmation. Click Restore.
- If a validation checkpoint exists for the selected checkpoint, the restore operation is performed immediately. If a validation checkpoint does not exist, the restore operation first validates the checkpoint and creates a validation checkpoint. Then, it performs a restore from the validation checkpoint.
- The progress of the restore operation is displayed on the progress card that gets created with the restore operation. A task is also initiated in the GUI which can be used to track the status of the restore operation. Once the restore operation is completed, the status of the task changes accordingly.