NetBackup™ 10.4 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
- Adding and removing local users on a primary or a media server instance
- Connecting an Active Directory user domain to a primary or a media server instance
- Connecting an LDAP user domain to a primary or a media server instance
- Changing a user password on a primary or a media server instance
- Using SSH keys for authentication on a primary or a media server instance
- Configuring the multi-factor authentication on NetBackup primary and 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
- Enabling extra OS STIG hardening on a primary or a media server instance
- Using a login banner on a primary or a media server instance
- Using a primary server instance for disaster recovery
- Authorizing a primary or a media server instance for deletion
- Managing users on a primary or a media server instance
- 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
- Configuring the multi-factor authentication on NetBackup WORM storage server instance
- 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
- Protecting the NetBackup catalog on a WORM storage server
- Managing certificates from the deduplication shell
- Managing FIPS mode from the deduplication shell
- Encrypting backups from the deduplication shell
- Configuring an isolated recovery environment using the web UI
- 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) configuration parameters
- 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 the health monitor
- Viewing information about the system
- Viewing the deduplication (MSDP) history or configuration files
- Viewing process information in the pseudo-file system
- Viewing the deduplication rate of a Veritas provisioning file service (VPFS) share
- Viewing the log files
- Collecting and transferring troubleshooting files
- Managing S3 service from the deduplication shell
- Authorizing a WORM storage server for deletion
- Managing users from the deduplication shell
Using a primary server instance for disaster recovery
If a NetBackup primary server application instance is lost in a disaster scenario, you can create a new instance to recover the identity of the instance that was lost. To recover the instance identity, you need the following information:
The configuration details of the lost instance
The NetBackup disaster recovery package
For more information about the disaster recovery package, see the chapter "Disaster recovery" in the NetBackup Troubleshooting Guide.
To recover a primary server instance identity
- Create a primary server instance with the same configuration as the instance that was lost. During instance creation, select the option Use instance for disaster recovery.
- Open an SSH session to the instance. If you have not already, change the default password.
- Copy the following NetBackup disaster recovery files to a local folder on the instance:
PolicyName_XXXXXXXX_FULLPolicyName_XXXXXXXX_FULL.drpkg
- Run the following command to import the disaster recovery package:
sudo /usr/openv/netbackup/bin/admincmd/nbhostidentity -import -infile PolicyName_XXXXXXXX_FULL.drpkg
- Run the following command to start all NetBackup services:
sudo /usr/openv/netbackup/bin/goodies/netbackup start
- From the NetBackup web UI, reissue a token for each associated media server and WORM storage server. Use the following steps:
On the left, click Security > Hosts.
Click NetBackup certificates.
Select the host and click Generate reissue token.
Enter a token name and indicate how long the token should be valid for.
Click Create.
- Add the media servers to the primary server's host properties. Use the following steps:
On the left, click Hosts > Host properties.
Select the primary server, then click Edit primary server > Servers.
For a media server with MSDP storage, navigate to the Additional servers tab and click Add.
For a media server with AdvancedDisk storage, navigate to the Media servers tab and click Add.
- Run the Catalog Recovery Wizard. For instructions, see the section "Recovering the entire NetBackup catalog using the Catalog Recovery Wizard" in the NetBackup Troubleshooting Guide.
- Once the catalog recovery completes successfully, run the following commands on the primary server instance to stop and start all primary server daemons:
sudo /usr/openv/netbackup/bin/goodies/netbackup stop
sudo /usr/openv/netbackup/bin/goodies/netbackup start
- Log in to the media server instances and run the following command to stop and restart all media server daemons:
sudo /usr/openv/netbackup/bin/goodies/netbackup stop
sudo /usr/openv/netbackup/bin/goodies/netbackup start
- From the NetBackup web UI, navigate to Hosts > Host Properties. Select each media server and click Connect.
- On the left, click Storage > Media servers. Then click the Media servers tab. Select each media server and click Activate.
- Perform a backup and restore test to each media server to verify that everything is working correctly.