NetBackup™ 10.0 Application Guide
- Product overview
- Release notes
- Geting started
- Creating NetBackup application instances
- Managing NetBackup application instances
- Managing application instances from Flex Appliance and NetBackup
- Accessing NetBackup primary and media server instances for management tasks
- Managing users on a primary or media server instance
- Running NetBackup commands on a primary or media server application instance
- Monitoring NetBackup services on a NetBackup primary server instance
- Mounting an NFS share on a NetBackup primary server instance
- Setting environment variables on primary and media server instances
- Storing custom data on a primary or media server instance
- Modifying or disabling the nbdeployutil utility on a primary server instance
- Disabling SMB server signing on a media server instance
- Establishing trust with a NetBackup 7.7.3 primary server instance
- Accessing NetBackup WORM storage server instances for management tasks
Operational notes
This topic explains important aspects of the NetBackup 10.0 application that may not be documented elsewhere in the documentation.
The following list contains the notes and the known issues that apply for this release:
If a media server instance restarts due to an appliance operation such as a restart or a power cycle, or if the instance is relocated as part of any operation, the following problems may result:
SAN client backups run over LAN instead of Fibre Transport.
SAN client backups fail.
Backups and restores through Fibre Transport fail.
Remote tape devices become unusable.
To avoid these issues, monitor the Fibre Channel interfaces page of the Flex Appliance Console after an appliance restart or instance relocation. You can also check the Fibre Channel tab of the instance details page. Wait for the link state of the ports to be up before you run any backups. The ports may take up to 10 minutes to become active.
If the ports are up, but you still encounter problems with your backup jobs, do one of the following:
Log in to the NetBackup Java console, navigate to Media and Device Management > Devices > SAN Clients, then choose each SAN client that is affected and trigger a Fibre Channel (FC) rescan.
Log in to the media server instance and run the following command:
sudo /usr/openv/netbackup/bin/admincmd/nbftconfig -rescanallclients
When you create a new application instance, the Application instances section of the System topology page may show the instance status as Partially Deleted while the creation is in progress. The Partially Deleted status displays in error and can be safely ignored. You can track the instance creation progress from the Activity Monitor, and the instance status changes to Online when the instance creation has completed successfully.
When you create an instance, if you enter the IP address before you select a network interface, the IP address field displays the following error message:
"IP address does not belong to the selected network's subnet."
This message still displays after you select the network interface that corresponds to the IP address. To clear the message, click inside the IP address field and then click or tab outside of it.
The username maintenance is no longer supported on application instances. If an existing user has the username maintenance when you upgrade to this release, that user becomes disabled.