In the following example, snapshots of all devices in a storage group are created and retained for 2 days. This provides for up to 2 days of snapshots without consuming any additional device numbers or the cache overhead.
To create snapshots, enter:
symsnapvx -sid 001 -sg StorageGroup1 -name snapshot establish -ttl -delta 2
To list snapshots, enter:
symsnapvx -sid 001 list -sg StorageGroup1 -snapshot_name snapshot -detail -GB
NOTE:In this example, to create snapshots every 15 minutes, use a script or schedule to run the
symsnapvx establish command at 15 minute intervals.
Output:
Storage Group (SG) Name : StorageGroup1
SG's Symmetrix ID : 000196700001 (Microcode Version: 5977)
------------------------------------------------------------------------
Total
Sym Flgs Deltas Non-Shared
Dev Snapshot Name Gen FLRG TSEB Snapshot Timestamp (Tracks) (Tracks) Expiration Date
----- -------------- ---- --------- ------------------------- ----- ------ ------------------
00212 snapshot 0 .... .... Mon Jun 15 16:15:00 2015 142 11 Tue Jun 17 16:15:00 2015
snapshot 1 .... .... Mon Jun 15 16:00:00 2015 222 11 Tue Jun 17 16:00:00 2015
snapshot 2 .... .... Mon Jun 15 15:45:00 2015 272 0 Tue Jun 17 15:45:00 2015
------ -------
636 22
Flags:
(F)ailed : X = General Failure, . = No Failure,
S = SRP Failure, R = RDP Failure,
(L)ink : X = Link Exists, . = No Link Exists
(R)estore : X = Restore Active, . = No Restore Active
(G)CM : X = GCM, . = Non-GCM
(T)ype : Z = zDP snapshot, . = normal snapshot
(S)ecured : X = Secured, . = No Secure
(E)xpanded : X = Source Device Expanded, . = Source Device Not Expanded
(B)ackground: X = Background define in progress, . = No Background define
NOTE:Data Protector for z Systems (zDP™) snapshots, created and managed through Mainframe Enabler products, are reported in Solutions Enabler by the flag (T) when issuing the
symsnapvx list command. Automated zDP snapshots taken by Mainframe Enabler are reported with the snapshot name
_zDP_XYZ, where XYZ is the internal zDP schedule id used by zDP for that snapshot.
Any of the snapshots created in the previous example can be used to restore the source volumes. Before issuing any restore, unmount the source volume from the application server to ensure that the data is fully refreshed on the host. Before issuing any restore, unmount the source volume from the application server to ensure that the data is fully refreshed on the host.
To restore directly to the production volumes from snapshot generation 2 taken at 15:45pm, enter:
symsnapvx -sid 001 -sg StorageGroup1 -snapshot_name snapshot -gen 2 restore
Execute Restore operation for Storage Group StorageGroup1 (y/[n]) ? y
Restore operation execution is in progress for the storage group StorageGroup1. Please wait...
Polling for Restore..................................................Started.
Polling for Restore..................................................Done.
Restore operation successfully executed for the storage group StorageGroup1
When the restore command completes, the volumes are read/write accessible to the host and the restored data is instantly available to the host. Therefore, the production volumes can be remounted and used immediately, and copying of any remaining tracks, from the snapshot delta to the source volume, is done as a background task. The snapshot data is always preserved and can be used again for a future restore, if needed, so writing to the source volume while restore operation is still copying data does not affect the snapshots.
Typically the restore command completes in a few seconds, but the time to complete is dependent on the number of devices involved in the restore operation. Use the
verify option to verify that all devices are restored.
To verify that the snapshot is restored, enter:
symsnapvx -sid 001 -sg StorageGroup1 -snapshot_name snapshot -gen 2 verify -restored
All of the devices are in the restored state
To terminate the restore session, enter:
symsnapvx -sid 001 -sg StorageGroup1 -snapshot_name snapshot -gen 2 terminate -restored
Execute Terminate operation for Storage Group StorageGroup1 (y/[n]) ? y
Terminate operation execution is in progress for the storage group StorageGroup1. Please wait...
Polling for Terminate.............................................Started.
Polling for Terminate.............................................Done.
Terminate operation successfully executed for the storage group StorageGroup1