Veritas NetBackup™ Replication Director Solutions Guide
- Introduction
- 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
- Creating disk pools for snapshot replication
- Updating disk pools after volumes are added, are deleted, or are changed
- Updating an OpenStorage disk pool to reflect plug-in updates
- How to resolve snapshot disk volume changes
- 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
- About configuring storage lifecycle policies for snapshots and snapshot replication
- Creating a storage lifecycle policy for snapshots and snapshot replication
- Operation types in a storage lifecycle policy
- Snapshot operation in an SLP
- Primary snapshot storage unit
- Primary + Replication source snapshot storage unit
- Replication source + Replication target snapshot storage unit
- Replication target snapshot storage unit
- Replication source + Replication target + Mirror snapshot storage unit
- Replication target + Mirror snapshot storage unit
- Replication operation in an SLP
- Index From Snapshot operation in an SLP
- Backup From Snapshot operation in an SLP
- Duplication 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 configuring a backup policy for Replication Director
- Configuring an NDMP policy to protect a NAS host
- Configuring a Standard or MS-Windows policy to protect clients using NDMP with Data Mover
- Configuring a Standard or MS-Windows policy to protect NAS volumes or SAN-connected devices
- About NDMP support for Replication Director
- Restoring from a snapshot
- About restores from array-based snapshots
- Restoring files and folders from an array-based snapshot
- About restores from array-based snapshots of virtual machines
- Using OpsCenter to restore from array-based snapshots
- How NetApp performs a volume-level rollback restore
- Restoring (rolling back) from an array-based snapshot
- OpsCenter reporting
- Using NetApp disk arrays with Replication Director
- Using NetApp disk arrays with Replication Director
- Supported NetApp topologies
- Using NetApp Data ONTAP 7-mode with Replication Director
- Configuration overview: NetApp 7-Mode with Replication Director
- Licenses required for NetApp Data ONTAP 7-Mode with Replication Director
- Software required to use NetApp Data ONTAP 7-Mode with Replication Director
- About using NetApp SAN-connected storage with Replication Director
- If the OnCommand Unified Manager root or administrator password has changed
- Considerations when configuring an OnCommand Unified Manager as a NetBackup storage server
- Importing existing NetApp relationships for NetBackup control
- Enabling Unicode and language settings on NetApp disk arrays
- Using NetApp Clustered Data ONTAP with Replication Director
- Configuration overview: NetApp Clustered Data ONTAP with Replication Director
- Licenses required for NetApp Clustered Data ONTAP with Replication Director
- Software required to use NetApp Clustered Data ONTAP with Replication Director
- Configuring Replication Director to work with Clustered Data ONTAP
- About creating backup policies for Clustered Data ONTAP with Replication Director
- Protecting volumes with nested junctions for Clustered Data ONTAP
- Limitations to using Clustered Data ONTAP with Replication Director
- Using Oracle with Replication Director
- Using Virtual Machines with Replication Director
- Terminology
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.
Select 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.
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.
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.