Veritas NetBackup™ Replication Director Solutions Guide
- Additional configuration topics
- Creating a NetBackup storage server for snapshot replication
- Configuring disk pools for snapshot and replication
- About disk pools for snapshots and snapshot replication
- Using bpstsinfo to view the replication topology of a device
- Configuring storage units and storage unit groups for snapshots and snapshot replication
- Configuring storage lifecycle policies for snapshots and snapshot replication
- Operation types in a storage lifecycle policy
- Snapshot operation in an SLP
- Index From Snapshot operation in an SLP
- Snapshot operation in an SLP
- Retention types for storage lifecycle policy operations
- Configuring backup policies for snapshots and snapshot replication
- About NDMP support for Replication Director
- Restoring from a snapshot
- About restores from array-based snapshots of virtual machines
- OpsCenter reporting
- Using NetApp disk arrays with Replication Director
- Supported NetApp topologies
- Using NetApp Data ONTAP 7-mode with Replication Director
- About using NetApp SAN-connected storage with Replication Director
- Using NetApp Clustered Data ONTAP with Replication Director
- Using Oracle with Replication Director
- Using Virtual Machines with Replication Director
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.
Selectto 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
After making the change, restart the NBSL process so that the change takes effect.
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:
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.
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.