Ransomware attackers specifically target and attempt to destroy backup systems to increase the probability of payment. Hardening your system is critical. Please ensure you have reviewed your platform security using the Security Hardening Checklist
Cohesity

COHESITY Documentation

Explore our documentation to get started, discover products & new features, access troubleshooting guides, register sources, platforms support.

Products
Data Security Alliance
Visit Cohesity.com
Demos
Support
Blogs
Developers
Partner Portals
Cohesity Community
© 2026 Cohesity, Inc. All Rights Reserved.
Terms of Use|
Privacy Policy|
Legal|
  1. Home
  2. NetBackup™ Replication Director Solutions Guide
  3. Using NetApp disk arrays with Replication Director
  4. Using NetApp Data ONTAP 7-mode with Replication Director
  5. Considerations when configuring an OnCommand Unified Manager as a NetBackup storage server
NetBackup™ Replication Director Solutions Guide

Considerations when configuring an OnCommand Unified Manager as a NetBackup storage server

The following items are OCUM-specific and are helpful when configuring an OCUM as a storage server.

Storage server type

Select NetApp OnCommand server (7-mode) to create a storage server (for either NAS volumes or SAN devices).

By default, the storage server has 5 minutes to communicate with NetBackup before it times out. When creating a NetApp storage server (type NETWORK_NTAP), more time may be required. To increase the timeout, edit the nbsl.xml file, the configuration file that interacts with the NetBackup Service Layer process (NBSL).

Locate the nbsl.xml file in the following directory:

On Windows: C:\Program Files\Veritas\NetBackup\var\global\nbsl.xml

On UNIX: /opt/openv/var/global/nbsl.xml

Find the entry for TPCommandTimeout and change the default from 300 to a greater value. For example:

TPCommandTimeout="600"

After making the change, restart the NBSL process so that the change takes effect.

Determining whether the OCUM server name is fully qualified or short

Use the bpstsinfo command to verify whether a short name or a fully qualified name is used for the storage server. The command is located in the following directory:

  • Windows: Install_path\NetBackup\bin\admincmd\

  • UNIX: /usr/openv/netbackup/bin/admincmd/

Enter the bpstsinfo command as follows:

bpstsinfo -serverinfo -storage_server known_storage_server_name -stype storage_server_type

For example, to ensure that the name of the OnCommand Unified Manager is OCUMServer, enter the following command:

bpstsinfo -serverinfo -storage_server OCUMServer -stype Network_NTAP

Use the storage server name that is indicated in the output.

Regarding disk pools for OnCommand Unified Manager storage servers

In the Disk Pool Configuration Wizard

  • The total sizes on the primary volume always display as 0 bytes, as indicated by a dash.

  • When the NBUPlugin is installed on the OnCommand Unified Manager, a NetBackup group is automatically created on the OnCommand Unified Manager. On the OnCommand Unified Manager, use the NetApp Management Console to add resource pools to the NetBackup group so that the resource pools are exposed to NetBackup. If the NetBackup group does not contain resource pools, no LSUs display in the disk pool configuration wizard.

    The available size that is listed is the total amount of space available in the pool. The raw size is the total raw, unformatted size of the storage in the disk pool. For OnCommand Unified Managers, the sizes on the primary volume always display as 0 bytes, as indicated by a dash.

Feedback

Was this page helpful?
Previous

If the OnCommand Unified Manager root or administrator password has changed

Next

Importing existing NetApp relationships for NetBackup control

Feedback

Was this page helpful?