to the same cloud object store as the production cluster to access the specified production virtual volume on that cloud object store without copying the data through the grid links. 

The DR cluster that is attached to the same cloud object store as the production cluster does not allow it to access the data that is stored in the cloud object store by the production cluster unless the CLDHHOST  keyword is used with the COPYRFSH  command on a per volume basis. The best way to think about a cloud object store (as it relates to functionality from a DR perspective) is that it is synonymous with a TS7700T. 

## 14.4 DR for FlashCopy concepts and command examples 

When enabled, FlashCopy allows two instances of a volume to exist on the same DR cluster. The DR host accesses the content of a virtual volume from time zero, while an active copy of the logical volume can be updated with new copies pulled from the production cluster. You do not need a break of the grid links to ensure that only data from time zero is available to the DR host. 

For more information, see  IBM Virtualization Engine TS7700 Series Best Practices - FlashCopy for Disaster Recovery Testing , WP102415. 

The following terms apply to FlashCopy: 

GLYPH<SM590000> Live Copy: A real-time instance of a virtual tape within a grid that can be modified and replicated to peer clusters. This live instance of a volume that is in a cluster is the most recent version of the volume on that cluster. If the Live Copy is also consistent relative to the grid, it can be altered by a production host or from a DR host when it is in the exclusion list of write protect. 

GLYPH<SM590000> FlashCopy: A snapshot of a live copy at time zero. The content in the FlashCopy is fixed and does not change, even if the original copy is modified or if replication events occur. A FlashCopy might not exist at a particular cluster if a live volume was not present within that cluster at time zero. In addition, a FlashCopy does not imply consistency because the live copy might be down level to the grid, or incomplete at time zero. An active FlashCopy indicates that Write Protect Mode is active. 

GLYPH<SM590000> DR Family: A set of TS7700 clusters (most likely those clusters at the DR site) that serve the purpose of DR. A total of 1 - 7 clusters can be assigned to a DR Family. The DR Family is used to determine which clusters should be affected by a flash request or write-protect request by using a host console request command (HCR). A DR Family needs at least one TS7760 or TS7770. 

GLYPH<SM590000> Write Protect Mode (existing function): When Write Protect Mode is enabled on a cluster, host commands fail if they are sent to virtual devices in that cluster and attempt to modify a volume’s data or attributes and that volume is not excluded from write protect. The FlashCopy is created on a cluster when it is in the Write Protect Mode only. Also, only write-protected virtual tapes are flashed. Virtual tapes that are assigned to the excluded categories are not flashed. 

GLYPH<SM590000> Time Zero: The time when the FlashCopy is taken within a DR Family. The time zero mimics the time when a real disaster occurs. Customers can establish the time zero by using a host console request command. 

## 14.4.1 Basic requirements and concepts 

The FlashCopy for DR testing function is supported on TS7700 Grid configurations where at least one TS7760 or TS7770 cluster exists within the DR location. 

