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 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
- 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 Flex Appliance WORM storage server instance
- Managing an isolated recovery environment on a Flex Appliance WORM storage server instance
- 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
Storing custom data on a primary or media server instance
Flex Appliance does not generally support adding or editing directories and files on application instances. If you create or edit a directory or file and the instance is relocated or stopped for any reason, the changes are not maintained when the instance restarts.
However, if you have critical data that you must store on a NetBackup primary or media server application instance, use the following procedure to add it to the /mnt/nblogs directory.
Warning:
The /mnt/nblogs directory is used for NetBackup logs and has 250GB of storage space that cannot be resized. The data that you add to this directory must be critical and small in size. If you use too much storage space, the instance may be affected.
To store custom data on a NetBackup primary or media server instance
- Log in to the instance as the appadmin user.
- Run the following command to create a directory under
/mnt/nblogs:sudo mkdir /mnt/nblogs/<directory>, where <directory> is the name of the new directory.
For example, if you need to store SSH
authorized_keyfiles on the instance, you can make the following directory:sudo mkdir /mnt/nblogs/authorized_keys
- If required, run the following command to create a subdirectory:
sudo mkdir /mnt/nblogs/<directory>/<subdirectory>, where <directory> is the name of the directory that you created in the previous step and <subdirectory> is the name of the subdirectory.
In the
authorized_keysexample, you can create the following subdirectory to store a specific user'sauthorized_keyfile:sudo mkdir /mnt/nblogs/authorized_keys/example_user
- Add the required information to the new directory.