NetBackup™ 10.1 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 a media server instance
- Running NetBackup commands on a primary or a 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 a media server instance
- Modifying or disabling the nbdeployutil utility on a primary server instance
- Disabling SMB server signing on a media server instance
- Using a primary server instance for disaster recovery
- Accessing NetBackup WORM storage server instances for management tasks
- Managing users from the deduplication shell
- Adding and removing local users from the deduplication shell
- Adding MSDP users from the deduplication shell
- Connecting an Active Directory domain to a WORM storage server for Universal Shares and Instant Access
- Disconnecting an Active Directory domain from the deduplication shell
- Changing a user password from the deduplication shell
- Managing VLAN interfaces from the deduplication shell
- Viewing the lockdown mode on a WORM storage server
- Managing the retention policy on a WORM storage server
- Managing images with a retention lock on a WORM storage server
- Auditing WORM retention changes
- Managing certificates from the deduplication shell
- Managing FIPS mode from the deduplication shell
- Encrypting backups from the deduplication shell
- Configuring an isolated recovery environment on a WORM storage server
- Managing an isolated recovery environment on a WORM storage server
- Tuning the MSDP configuration from the deduplication shell
- Setting the MSDP log level from the deduplication shell
- Managing NetBackup services from the deduplication shell
- Managing the cyclic redundancy checking (CRC) service
- Managing the content router queue processing (CRQP) service
- Managing the online checking service
- Managing the compaction service
- Managing the deduplication (MSDP) services
- Managing the Storage Platform Web Service (SPWS)
- Managing the Veritas provisioning file system (VPFS) mounts
- Managing the NGINX service
- Managing the SMB service
- Monitoring and troubleshooting NetBackup services from the deduplication shell
- Managing users from the deduplication shell
Operational notes
This topic explains important aspects of the NetBackup 10.1 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.