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
NetBackup configuration files are not persistent across operations that require restarting the system
The VmTools.cfg and vixDiskLib.ini files do not persist after a node is restarted as a part of an operation such as upgrading or replacing a node.
Workaround:
Use the cp-nbu-config command to copy the NetBackup configuration files from the user's home space to the specified NetBackup configuration destination directory. A NetBackup administrator can use the cp-nbu-config command to create and edit a NetBackup touch configuration file in any of the following directories:
/usr/openv/netbackup/usr/openv/netbackup/bin/usr/openv/java/usr/openv/lib/ost-plugins/usr/openv/netbackup/bin/snapcfg/usr/openv/netbackup/db/cloudSnap/credential/usr/openv/netbackup/db/cloudSnap/proxy/usr/openv/netbackup/db/config/usr/openv/netbackup/db/event/usr/openv/netbackup/db/images/usr/openv/netbackup/db/media/usr/openv/netbackup/ext/db_ext/usr/openv/netbackup/ext/db_ext/db2/usr/openv/var/usr/openv/volmgr/usr/openv/volmgr/database
To create or edit a touch configuration file
- Log in to the node.
- Create a new configuration file in the NetBackup administrator home directory, or use the cp command to copy an existing configuration file from its original location to the home directory. For example:
cp /usr/openv/lib/ost-plugins/pd.conf ~/
- Make changes to the file in the home directory.
- Run the following command to install the file in its original directory or a supported destination directory:
sudo /opt/veritas/vxapp-manage/cp-nbu-config configuration-file destination
where configuration-file is the file that you created or edited, and destination is the directory where it needs to be installed.
sudo /opt/veritas/vxapp-manage/cp-nbu-config ~/pd.conf /usr/openv/lib/ost-plugins