Veritas NetBackup™ OpenStorage Solutions Guide for Disk
- Introducing disk appliance storage solutions
- Planning your deployment
- Planning your OpenStorage deployment
- About OpenStorage requirements and limitations
- About OpenStorage storage servers for backups
- About OpenStorage server credentials
- About OpenStorage data movers for backups
- About the OpenStorage plug-in
- About OpenStorage disk pools for backups
- About OpenStorage optimized duplication and replication
- About OpenStorage optimized synthetic backups
- About storage unit groups for OpenStorage
- About OpenStorage direct to tape
- Provisioning the storage
- Licensing OpenStorage
- Configuring OpenStorage in NetBackup
- Configuring OpenStorage disk appliance storage
- Configuring an OpenStorage storage server for backups
- Configuring an OpenStorage disk pool for backups
- Configuring an OpenStorage storage unit
- Configuring OpenStorage optimized synthetic backups
- Configuring OpenStorage direct to tape
- Configuring optimized duplication to an OpenStorage device within the same NetBackup domain
- Configuring replication to an OpenStorage device in a different domain
- About storage lifecycle policies
- About the storage lifecycle policies required for Auto Image Replication
- Creating a storage lifecycle policy
- Creating a backup policy
- Adding OpenStorage functionality to an existing environment
- Managing OpenStorage
- Managing OpenStorage storage servers
- Viewing OpenStorage storage servers
- Determining OpenStorage storage server state
- Changing OpenStorage storage server properties
- Setting OpenStorage storage server attributes
- Removing OpenStorage storage server attributes
- Updating an OpenStorage storage server to reflect plug-in updates
- Deleting an OpenStorage storage server
- Managing OpenStorage server credentials
- Managing OpenStorage data movers
- Managing OpenStorage disk pools
- Viewing OpenStorage disk pools
- Determining OpenStorage disk pool state
- Changing OpenStorage disk pool state
- Determining OpenStorage disk volume state
- Changing OpenStorage disk volume state
- Changing OpenStorage disk pool properties
- Setting OpenStorage disk pool attributes
- Removing OpenStorage disk pool attributes
- Adding volumes to an OpenStorage disk pool
- Merging OpenStorage disk pools
- Removing a volume from an OpenStorage disk pool
- Updating an OpenStorage disk pool to reflect plug-in updates
- Deleting an OpenStorage disk pool
- Monitoring OpenStorage storage capacity and usage
- Viewing OpenStorage disk reports
- Reporting on Auto Image Replication jobs
- About catalog backups to OpenStorage devices
- About restoring from OpenStorage backup copies
- About restoring from a backup at a target master domain
- Managing OpenStorage storage servers
- Troubleshooting
Cascading Auto Image Replication model
Replications can be cascaded from the originating domain to multiple domains. Storage lifecycle policies are set up in each domain to anticipate the originating image, import it and then replicate it to the next target master.
Figure: Cascading Auto Image Replication represents the following cascading configuration across three domains.
The image is created in Domain 1, and then replicated to the target Domain 2.
The image is imported in Domain 2, and then replicated to a target Domain 3.
The image is then imported into Domain 3.
In the cascading model, the originating master server for Domain 2 and Domain 3 is the master server in Domain 1.
Note:
When the image is replicated in Domain 3, the replication notification event indicates that the master server in Domain 2 is the originating master server. However, after the image is imported successfully into Domain 3, NetBackup correctly indicates that the originating master server is in Domain 1.
The cascading model presents a special case for the Import SLP that replicates the imported copy to a target master. (This master server that is neither the first nor the last in the string of target master servers.)
The Import SLP must include at least one operation that uses a Fixed retention type and at least one operation that uses a Target Retention type. So that the Import SLP can satisfy these requirements, the import operation must use a Target Retention.
Table: Import operation difference in an SLP configured to replicate the imported copy shows the difference in the import operation setup.
Table: Import operation difference in an SLP configured to replicate the imported copy
Import operation criteria | Import operation in a cascading model |
|---|---|
The first operation must be an import operation. | Same; no difference. |
A replication to target master must use a Fixed retention type | Same; no difference. |
At least one operation must use the Target retention. | Here is the difference: To meet the criteria, the import operation must use Target retention. |
The target retention is embedded in the source image.
In the cascading model that is represented in Figure: Cascading Auto Image Replication, all copies have the same Target Retention - the Target Retention indicated in Domain 1.
For the copy in Domain 3 to have a different target retention, add an intermediary replication operation to the Domain 2 storage lifecycle policy. The intermediary replication operation acts as the source for the replication to target master. Since the target retention is embedded in the source image, the copy in Domain 3 honors the retention level that is set for the intermediary replication operation.
