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
Notes on Replication Director for virtual machines
Note the following about Replication Director for virtual machines:
For supported vCenter versions and datastores, see the NetBackup Software Compatibility List available from the following location:
For additional support details, see the following Veritas tech note:
Replication Director for virtual machines does not support Accelerator.
Instant Recovery supports disk storage units only. To use Instant Recovery to restore a VM that was backed up with Replication Director for virtual machines, note: The virtual machine backup must have been copied to a disk storage unit.
Although applicable to Replication Director for physical computers, NDMP backup does not apply to Replication Director for virtual machines.
Replication Director supports virtual machines on NetApp NFS datastores only.
To create virtual machines on the NFS datastore, enter anon=0 in the
/etc/exportsNetApp file on the NetBackup storage server. The anon=0 entry is the equivalent of the no_root_squash option. See the following VMware document for more information on the anon=0 entry:Best Practices for running VMware vSphere on Network Attached Storage
The NetApp OnCommand Unified Manager (formerly DataFabric Manager) must be able to resolve the host name that was used to mount the vCenter datastore. Hardware snapshots cannot succeed if the OnCommand server is unable to resolve the host name
If the NetBackup master and media server are UNIX and the backup host is Windows, the backup host must have a fully qualified domain name. Otherwise, the backup fails.
You must have a valid NFS export (share) for each qtree that is mounted as an NFS datastore.
Supports restore of virtual machines and of individual files in virtual machines. Does not support volume-level rollback restore. (In the Replication Director Solutions Guide, references to rollback restore do not apply to virtual machines.)
If the datastore name contains special characters, the datastore name in the backup image contains @ followed by the value of the special character. For example, a datastore that has the name "NFS datastore1" (with a space) appears in the NetBackup catalog as NFS@20datastore1.
If changes occur to virtual machine configuration (such as adding, deleting, or moving VMDKs), it may be necessary to set to 0. ( is on the policy Clients tab.) With a setting of 0, NetBackup rediscovers the virtual machines and their configuration each time the policy runs. Note: If the vmdk files are reconfigured and the next backup runs without rediscovery, NetBackup is not aware of the vmdk changes. It attempts to back up the virtual machines in their previous configuration. The result may be an incorrect backup.
VMware vSphere uses the Space Efficient Virtual Disk (SEsparse) for snapshots of the disks that are larger than 2 TB. VMware's VDDK however does not support backup or restore of SEsparse disks with the host-based file transport mode. Because Replication Director for VMware requires host-based file transport, Replication Director cannot support the vmdk files that are larger than 2 TB. To back up the vmdk files that are larger than 2 TB, use NetBackup for VMware without Replication Director.
When restoring from Replication Director backups, note the following:
If you select more than one image in the Backup, Archive, and Restore interface, it may take longer than expected to display the image contents. NetBackup performs a separate browsing operation for each selected image. You should select one image at a time when browsing for restore.
Do not select files or folders from two different images. The NetBackup Backup, Archive, and Restore interface, and the OpsCenter interface do not support restoring data from two different images in the same restore job. Restore from one image at a time.
When you use the Backup, Archive, and Restore interface to browse for an image to restore, only the primary copy is made available for restore. In the NetBackup Administration Console, use the node to select a different copy (such as a backup image or replica) as the primary copy.
Note:
NetBackup automatically selects the correct hardware (datastore) snapshot to restore, based on the virtual machine snapshot that is designated as the primary copy. Make sure the virtual machine snapshot that you want to restore is set as the primary.