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
NetApp storage server sample bpstsinfo output
The following examples show sample output from the bpstsinfo command for a NetApp storage server named plinko which contains four LSUs. The generic syntax for the command is as follows:
bpstsinfo -lsuinfo -storage_server storage_server_name -stype storage_type
The following is an example of the command, run on the NetBackup media server, for storage server plinko:
bpstsinfo -lsuinfo -storage_server plinko -stype Network_NTAP
Output for first LSU:
LSU Info: Server Name: Network_NTAP:plinko LSU Name: PrimarySnapshot Allocation : STS_LSU_AT_STATIC Storage: STS_LSU_ST_NONE Description: Configuration: Media: (STS_LSUF_REP_ENABLED | STS_LSUF_REP_SOURCE) Save As : (STS_SA_PRIMARY | STS_SA_SNAPSHOT) Replication Sources: 0 ( ) Replication Targets: 3 ( Network_NTAP:plinko:Netapp3140a2_SnapVault Network_NTAP:plinko:Netapp3140a2_SnapMirror Network_NTAP:plinko:Netapp3140a2_SecondSnapMirror ) . . .
The bpstsinfo output provides the following information about the volume:
Storage server name (Server Name). | plinko The name preceding the server name is the storage server type. For example, Network_NTAP. |
Volume name (LSU Name). | PrimarySnapshot |
Volume properties (Media, Save As). | The volume has the following properties:
|
Replication sources of the volume (Replication Sources). | The volume has no replication sources. It cannot receive replication from any other volume. |
Replication targets of the volume (Replication Targets). | The volume has three replication targets. It can replicate to the following volumes:
|
Output for second LSU:
LSU Info:
Server Name: Network_NTAP:plinko
LSU Name: Netapp3140a2_SnapVault
Allocation : STS_LSU_AT_STATIC
Storage: STS_LSU_ST_NONE
Description:
Configuration:
Media: (STS_LSUF_REP_ENABLED | STS_LSUF_REP_SOURCE |
STS_LSUF_REP_TARGET | STS_LSUF_MIRROR_FLEXIBLE)
Save As : (STS_SA_SNAPSHOT | STS_SA_MIRROR)
Replication Sources: 3 ( Network_NTAP:plinko:PrimarySnapshot
Network_NTAP:plinko:Netapp3140a2_SnapMirror
Network_NTAP:plinko:Netapp3140a2_SecondSnapMirror )
Replication Targets: 2 ( Network_NTAP:plinko:Netapp3140a2_SnapMirror
Network_NTAP:plinko:Netapp3140a2_SecondSnapMirror )
.
.
.The bpstsinfo output provides the following information about the volume:
Storage server name (Server Name). | plinko The name preceding the server name is the storage server type. |
Volume name (LSU Name). | Netapp3140a2_SnapVault |
Volume properties (Media, Save As). | The volume has the following properties:
Since the LSU is MirrorFlexible, it can be configured as Mirror-capable or not Mirror-capable as specified by the user. |
Replication sources of the volume (Replication Sources). | The volume has three replication sources. It can receive replications from the following three volumes:
|
Replication targets of the volume (Replication Targets). | The volume has two replication targets. It can replicate to the following two volumes:
|
Output for third LSU:
LSU Info:
Server Name: Network_NTAP:plinko
LSU Name: Netapp3140a2_SnapMirror
Allocation : STS_LSU_AT_STATIC
Storage: STS_LSU_ST_NONE
Description:
Configuration:
Media: (STS_LSUF_REP_ENABLED | STS_LSUF_REP_SOURCE |
STS_LSUF_REP_TARGET | STS_LSUF_MIRROR_FLEXIBLE)
Save As : (STS_SA_SNAPSHOT | STS_SA_MIRROR)
Replication Sources: 3 ( Network_NTAP:plinko:PrimarySnapshot
Network_NTAP:plinko:Netapp3140a2_SnapVault
Network_NTAP:plinko:Netapp3140a2_SecondSnapMirror )
Replication Targets: 2 ( Network_NTAP:plinko:Netapp3140a2_SnapVault
Network_NTAP:plinko:Netapp3140a2_SecondSnapMirror )
.
.
. Output for fourth LSU:
LSU Info:
Server Name: Network_NTAP:plinko
LSU Name: Netapp3140a2_SecondSnapMirror
Allocation : STS_LSU_AT_STATIC
Storage: STS_LSU_ST_NONE
Description:
Configuration:
Media: (STS_LSUF_REP_ENABLED | STS_LSUF_REP_SOURCE |
STS_LSUF_REP_TARGET | STS_LSUF_MIRROR_FLEXIBLE)
Save As : (STS_SA_SNAPSHOT | STS_SA_MIRROR)
Replication Sources: 3 ( Network_NTAP:plinko:PrimarySnapshot
Network_NTAP:plinko:Netapp3140a2_SnapVault
Network_NTAP:plinko:Netapp3140a2_SnapMirror )
Replication Targets: 2 ( Network_NTAP:plinko:Netapp3140a2_SnapVault
Network_NTAP:plinko:Netapp3140a2_SnapMirror )
.
.
.