CA Vtape does not directly control replication but can utilize NFS servers that do implement replication. Control over replication is managed by the NFS server.
The following is an illustration example of a simple Triplex only mount point:
During normal operations the NFS Backstore copies are created on Site A and replicated to Site B. Site A’s Backstore copies can also be used for recalls. During DR testing or an actual DR event, the replication mirror between Site A and Site B is turned off. An LPAR on Site B will run an instance of CA Vtape. All DR activity can take place reading and writing Virtual Volumes. When the test is complete the replication can be re-established between Site A and Site B. Anything written on Site B will be lost and changes made to Site A will be copied over to Site B. In this scenario CA Vtape does not participate in the reconfiguration, it is handled by the NFS devices.
Now consider the following possible configuration:
This example illustrates an advanced configuration exploiting additional group mount points along with some NFS servers replicating data and some NFS servers without replication.
In the example, the Triplex file system contains groups03-74 and are replicated between Site A and Site B. Group01 has been given its own dedicated NFS server which is also replicated between Site A and Site B. Finally, group02 has its own NFS server but resides in Site B so the group definition has been setup to write a Primary tape at Site A. Note that writing to group02 requires spanning the entire wide area network and throughput is slower than when writing to the NFS servers locally.
|
Copyright © 2013 CA Technologies.
All rights reserved.
|
|