Previous topic |
Next topic |
Contents |
Contact z/OS |
Library |
PDF
Data integrity considerations for full or tracks restore operations z/OS DFSMSdss Storage Administration SC23-6868-01 |
|
For a full or tracks restore operation, DFSMSdss serializes the VTOC to prevent DADSM functions such as ALLOCATE, EXTEND, RENAME, and SCRATCH from changing the contents of the VTOC on the volume during the restore operation. Data sets are not serialized on these restore operations and thus, some data sets can be opened by other jobs during the restore operations. The result might be that partially updated data sets are restored. Full data integrity can always be guaranteed by performing restore operations by data set only when TOLERATE(ENQFAILURE) or SHARE is not specified. During full or tracks restore operations, and stand-alone restore, it is possible to duplicate a volume serial number in the sysplex. If there is data in the coupling facility for the duplicated volume serial number, data integrity can be compromised. The recommended procedure before restoring a suspected volume is as follows:
During full or tracks restore operations, DFSMSdss resets the data-set-changed indicator for each data set being restored. Because the data set has not changed since the backup was performed, DFSMSdss resets the data-set-changed indicator. Attention: Use
caution when using DFSMSdss Full Volume
Restore in an environment in which other data set applications or
backup applications are used. If the applications rely on the data-set-changed
indicator to mean that the data set has not changed since earlier
processing, a data integrity issue can result when using DFSMSdss
to Restore full volumes when other applications are tracking the data
sets on that volume.
|
Copyright IBM Corporation 1990, 2014
|