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
- 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
- NetBackup Flex Scale security
- Troubleshooting
- Services management
- Collecting logs for cluster nodes
- 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
- Appendix A. Configuring NetBackup optimized duplication
- Appendix B. Disaster recovery terminologies
Services management
You can use the Settings > Services management tab to manage your storage services.
When there is a device failure or a new device is added, the device information may not be consistent. In such a scenario, you can to update the database with latest system settings and usage data.
You can fix service-related faults in the nodes of the cluster that are in running state. If a service has faulted because of issues in services such as the volume manager, NFS, FTP, CIFS, NLM, deduplication, or the management console, you can and bring the service online after the issue has been resolved. No other operation should be initiated when you run AutoFix.
You can also call the POST/api/appliance/v1.0/management/autofix RESTful API to run auto fix.