NetBackup 22.214.171.124 Application Guide
- Product overview
- Geting started
- Creating NetBackup application instances
- Managing NetBackup application instances
- Accessing NetBackup master and media server instances for management tasks
- Managing users on a master or media server instance
- Running NetBackup commands on a master or media server application instance
- Accessing NetBackup WORM storage server instances for management tasks
Creating a NetBackup WORM storage server instance
NetBackup WORM (Write Once Read Many) storage server instances prevent your data from being encrypted, modified, or deleted. Any data that is saved on these instances is protected with the following security measures:
This protection ensures that the backup image is read-only and cannot be modified, corrupted, or encrypted after backup.
This property protects the backup image from being deleted before it expires. The data is protected from malicious deletion.
See the NetBackup Administrator's Guide, Volume I for more information about WORM storage.
Use the following procedure to create a NetBackup WORM storage server instance on Flex Appliance.
Your appliance must be in lockdown mode before you can create a WORM storage instance.
See the topic "Changing the lockdown mode" in the Flex Appliance Getting Started and Administration Guide for the steps to enable lockdown mode.
To create a NetBackup WORM storage server instance
- Make sure that the NetBackup WORM storage server application you want to use is located in the repository.
- Perform the following tasks if you have not already:
Configure at least one network interface. You can configure a physical interface, add a VLAN tag, or create a bond.
Add at least one tenant.
Verify that the appliance is in lockdown mode. You can check or change the lockdown mode from the Lockdown mode page on the Flex Appliance Console. See the topic "Changing the lockdown mode" in the Flex Appliance Getting Started and Administration Guide for details.
- Gather the following information for the new instance:
The hostname and IP address must not be in use anywhere else in your domain.
Tenant that you want to assign it to
Hostname (maximum of 63 characters including the domain name)
Master server hostname (must be version 126.96.36.199 or later)
Media server hostname if applicable (must be version 188.8.131.52 or later)
Username for storage
NetBackup requires this username to connect to the deduplication storage. The username must be between 4 and 30 characters and can include uppercase letters, lowercase letters, and numbers.
Password for storage
NetBackup requires this password to connect to the deduplication storage. The password must be between 15 and 32 characters and must include at least one uppercase letter, one lowercase letter, one number, and one special character (_./@*!%#&).
KMS key group
Certificate Authority (CA) information for one of the following:
For a NetBackup CA:
CA certificate fingerprint
If the master server is a Flex instance, you can locate this information from the instance details page of the master server instance. Click on the instance name under Application instances on the System topology page.
If the master server is not a Flex instance, see the NetBackup Security and Encryption Guide for the steps to locate this information from NetBackup.
(Optional) Token for host ID-based certificate
Depending on the master server security level, the host may require an authorization or a reissue token. If you do not specify a token when you create the instance, the wizard attempts to automatically obtain the certificate.
For an external CA:
Trust store, in PEM format
Host certificate, in PEM format
Private key, in PEM format
(Optional) Passphrase of the private key
A passphrase is required if the key is encrypted.
(Optional) Password for host name-based certificate
A host name-based certificate is mandatory if Enhanced Auditing is enabled on the master server. You can specify the password when you create the instance, or you can deploy the certificate from the master server later.
- On the master server, use the nbsetconfig command or manually edit the NetBackup backup configuration (
bp.conf) file to add the following entry:
Where <MSDP hostname> is the hostname of the new WORM storage server instance.
- If a firewall exists between the master server and the new instance, open the following ports on the master server to allow communication:
If the master server is a NetBackup appliance that uses TCP, open the following ports:
443, 5900, and 7578.
- From the System topology page of the Flex Appliance Console, navigate to the Application instances section.
- Click Create instance.
- Select the appropriate storage server application from the repository list that appears, making sure to verify the version number. Click Next.
- Follow the prompts to create the instance. When you are done, you can view the progress in the Activity Monitor, which is accessible from the left pane of the Flex Appliance Console.
If you do not want to use DNS or want to bypass DNS for certain hosts, verify that the hostname resolution information is included in the Hosts file entries field. You must include entries for the master server and any other NetBackup hosts that you want to communicate with the instance.
- Once the instance has been created successfully, you must change the password from the known default password. To change the password, open an SSH session to the instance and log in with the following credentials:
Follow the prompt to enter a new password. When the password change is complete, you are logged out. You can log back in with the new password.
- If you plan to or have created multiple instances with deduplication or Cloud Catalyst storage, Veritas recommends that you tune the MaxCacheSize according to the following guidelines:
On each instance, allocate .75 GB to 1 GB of RAM for each TiB of storage that is allocated to deduplication on the instance. For example, if the storage pool has 80 TiB allocated, the MaxCacheSize should be 60 GB to 80 GB of RAM.
The sum of the MaxCacheSize for all instances with deduplication or Cloud Catalyst storage should not exceed 70% of the physical RAM on the appliance.
To tune the deduplication MaxCacheSize on this instance:
From the SSH session, run the following command on the instance:
setting set-MSDP-param max-fp-cache-size value=<percent%>
Where <percent%> is the percentage of the appliance RAM to use for the cache on the instance.
Restart the dedupe process with the following commands:
dedupe MSDP stop
dedupe MSDP start
- The appliance automatically creates a PureDisk storage server for the WORM storage instance that has the same name as the instance. Do one of the following to create a disk pool on that storage server:
From the NetBackup Administration Console, select either NetBackup Management or Media and Device Management, then click Configure Disk Pool in the right pane. Follow the prompts to configure the disk pool.
From the NetBackup web UI, click Storage, click the Disk pools tab, and then click Add. Follow the prompts to configure the disk pool.
- Do one of the following to create a deduplication storage unit for your instance:
From the NetBackup Administration Console, expand NetBackup Management > Storage > Storage Units, then click New > Storage Unit. Complete the fields and select the Use WORM check box.
From the NetBackup web UI, click Storage, navigate to the Storage Units tab, and then click Add. Follow the prompts and make sure that the Enable WORM option is activated.
You are ready to create a backup policy and start using your WORM storage instance. See the NetBackup documentation for more information.