Storage system: | ETERNUS DX/AF, Symmetrix/VMAX3 |
Domain: | DEVICE |
Privileges: | TSOS |
/RESTORE-FROM-SNAP
The original units of the snap pairs are specified in the UNIT operand.
When the original units are selected via a pubset (UNIT=*BY-PUBSET), snap units must exist for all units of the pubset.
The snap units can be selected for reconstruction either explicitly (e.g. via the catid of a renamed pubset) or implicitly according to their relative age (e.g. *FROM-SHOW-OUTPUT(*LAST)).
The original unit can also be the source unit of a remote copy pair. The target unit can also be the original unit of a snap pair. In this case the source unit is specified in the UNIT operand, and the snap pair on the target unit is selected using the SELECT=*TARGET-UNIT operand.
SHC-OSD checks the global and task-specific security settings before this command is executed (see "Security settings of SHC-OSD"). The current security settings can be displayed with /SHOW-SHC-PROCESSING (see also "SHOW-SHC-PROCESSING Displays settings of SHC-OSD"). They can be changed in the SHC-OSD parameter file (see "Configuration of SHC-OSD") for the next time SHC-OSD is started or with /MODIFY-SHC-PROCESSING for ongoing operations (see "MODIFY-SHC-PROCESSING Changes settings of SHC-OSD").
For SnapOPC+ on ETERNUS DX/AF
Data stored on the snap unit is copied to the original unit. The original unit can be accessed again after reconstruction has been completed.
If more than one snap unit is assigned to the same original unit, the other snap sessions are not affected by reconstruction. Multiple reconstructions can take place one after the other. However, no snap session may be included in a reconstruction.
The snap session remains in the COPY-ON-WRITE status. No status change is logged. After the command has been executed, the snap session is resumed using the reconstructed data.
If the original unit is also the clone unit of a clone pair or the target unit of a remote copy pair, /RESTORE-FROM-SNAP is not possible.
In ETERNUS AF and ETERNUS DX S3/S4 and higher, asynchronous reconstruction after command execution or synchronous reconstruction during command execution is possible WAIT operand). The snap pair is in the REST-IN-PROG status during synchronous reconstruction. Waiting can be aborted in dialog mode by hitting the K2 key.
The /STOP-SNAP-SESSION and /START-SNAP-SESSION commands are rejected with return code NDE1820 while reconstruction is being performed. They can only be executed successfully after reconstruction has been completed.
For TimeFinder/Snap on Symmetrix
WAIT=*UNTIL-RESTORED / *NO specifies whether the command waits (synchronous command execution) or not (asynchronous command execution) for reconstruction to be completed.
No other access may take place to the original and snap units. The snap session must be in the COPY-ON-WRITE status.
After the command has been executed the snap session is in the RESTORED status and cannot be used for anything else. Only the /STOP-SNAP-SESSION command is possible.
When multiple snap units are assigned to the same original unit, no snap session may be in the CREATED or RESTORED status. If the original unit also has clone units, the command is rejected.
If the original unit is also the target unit of a remote copy pair, the remote copy status must be IN-HOLD or ERROR, and TARGET-ACCESS must be DIRECT.
For TimeFinder SnapVX on VMAX3
WAIT=*UNTIL-RESTORED always applies, i.e. the command waits for reconstruction to terminate (synchronous command execution).
No other access may take place to the original and snap units. The snap session must be in the COPY-ON-WRITE status.
A temporary snap session is established between the snap unit and original unit for reconstruction. Subsequently the original unit contains the status of the reconstructed snap unit, in other words the status at the time the snapshot was created and all other changes performed on the snap unit since then. All snapshots of the original units continue to exist unchanged. The snap pair is temporarily in the REST-IN-PROG status during reconstruction. After reconstruction has terminated, it is once again in the COPY-ON-WRITE status and can continue to be used on the basis of the reconstructed data. Reconstruction can be repeated multiple times with any snap unit statuses of an original unit.
If more than one snap unit is assigned to the same original unit, the other snap sessions are not affected by reconstruction.
Multiple reconstructions one after another are possible. Parallel reconstructions of multiple snap sessions are not possible.
If the original unit is also the target unit of a remote copy pair, the remote copy status must be IN-HOLD or ERROR, and TARGET-ACCESS must be DIRECT.
RESTORE-FROM-SNAP | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
UNIT =
Selects the units by means of a particular VSN (*BY-VOLUME), a particular catalog ID (*BY-PUBSET), by means of the serial number and the internal number of the logical volume in the storage system (*BY-SYMMETRIX/*BY-STORAGE), or directly by means of the logical volume's mnemonic device name.
UNIT = *BY-VOLUME(...)
Selects the units by means of a particular VSN.
VOLUME = <vsn 1..6>
Specifies the volume’s VSN.
UNIT = *BY-PUBSET(...)
Selects units by means of a pubset ID or volume set ID. The pubset is protected against reconfiguration during command processing.
PUBSET = <cat-id 1..4>
Specifies the pubset ID or volume set ID.
CAUTION!
When a pubset is reconstructed from the snap units using UNIT=*BY-PUBSET(...), it may not have been reconfigured or, in particular, not have been reduced in size in the meantime. The snap units selected must contain a consistent pubset.
RENAME-PUBSET =
Input for pubset-ID or volume set ID of the reconstructed pubset.
RENAME-PUBSET = *NO
No rename for reconstructed pubsets. The pubset-ID of the snap pubsets is taken over implicitly.
RENAME-PUBSET = *SAME
The reconstructed pubset is renamed to pubset-ID or volume set ID of the original pubsets.
RENAME-PUBSET = <cat-id 1..4>
The reconstructed pubset is renamed to the specified pubset ID oder volume set ID.
UNIT = *BY-SYMMETRIX(...)
Only relevant for Symmetrix/VMAX3.
Selects the units by means of the serial number of the storage system and the internal number of the logical volume.
SERIAL-NUMBER = <alphanum-name 3..12>
Specifies the serial number of the storage system (make sure it is unique!).
LOGICAL-VOLUME = <x-text 1..4>
Specifies the internal number of the logical volume in the storage system.
UNIT = *BY-STORAGE(...)
Only relevant for ETERNUS DX/AF.
Selects the unit by means of the internal number of the logical volume in the storage system.
SERIAL-NUMBER = <alphanum-name 3..14>
Specifies the serial number of the storage system (make sure it is unique!).
LOGICAL-VOLUME = <x-text 1..4>
Specifies the internal number of the logical volume in the storage system.
UNIT = <alphanum-name 2..2> / <x-text 4..4>
Selects a unit using the mnemonic device name of the logical volume.
SNAP-UNIT =
Selects the snap units. If more than one snap unit exists for a unit, a specific snap unit must be selected.
SNAP-UNIT = *FIRST-POSSIBLE
Selects the first assigned snap unit possible for the command.
SNAP-UNIT = *FROM-SHOW-OUTPUT(...)
Selects the snap unit via its position in the output list of /SHOW-SNAP-SESSION-STATUS.
POSITION = <integer 1..127>
Specifies the position of the snap unit.
POSITION = *LAST
Selects the last snap unit in the output list.
SNAP-UNIT = *BY-PUBSET(...)
Selects the snap units using the pubset ID of the activated and renamed pubset.
SNAP-PUBSET = <cat-id 1..4>
Specifies the pubset ID.
SNAP-UNIT = *BY-SYMMETRIX(...)
Only relevant for Symmetrix/VMAX3.
Selects the snap unit by means of the internal number of the logical volume in the storage system.
SNAP-LOGICAL-VOLUME = <x-text 1..4>
Specifies the internal number of the logical volume in the storage system.
SNAP-UNIT = *BY-STORAGE(...)
Only relevant for ETERNUS DX/AF.
Selects the snap unit by means of the internal number of the logical volume in the storage system.
SNAP-LOGICAL-VOLUME = <x-text 1..4>
Specifies the internal number of the logical volume in the storage system.
SNAP-UNIT = list-poss(256): <alphanum-name 2..2> / <x-text 4..4>
Specifies the mnemonic device name of the snap units.
WAIT =WAIT=*UNTIL-RESTORED always applies for VMAX3.
Specifies whether or not the command waits for reconstruction to be completed.
WAIT = *NO
The command does not wait for reconstruction to be completed (asynchronous command execution).
WAIT = *UNTIL-RESTORED
The command waits for reconstruction to be completed (synchronous command execution).
This facilitates the programming of test procedures for recovery operations because no complex inquiries regarding the progress of reconstruction are required for the snap pairs.
Waiting can be aborted in dialog mode by hitting the K2 key.
SELECT =
Selects the snap pairs.
SELECT = *STD
Selects the snap pairs which were defined using the UNIT operand.
SELECT = *TARGET-UNIT(...)
Selects the snap pairs which are assigned to the target unit of a remote copy pair. The relevant source unit is specified in the UNIT operand.
RA-GROUP =
Only relevant for Symmetrix/VMAX3.
Selects the target unit using the RA group in the case of concurrent target units.
RA-GROUP = *UNIQUE
Selects the one existing target unit.
RA-GROUP = <integer 1..250>
Specifies the RA group for selecting the target unit.
FORCE =
Only relevant for Symmetrix.FORCE controls the reconstruction of a unit which is also an SRDF source unit in the ACTIVE status.
FORCE = *NO
Reconstruction is rejected.
FORCE = *YES
Reconstruction is executed.
Command processing
The following messages are output to SYSOUT for each director and distributed via routing code 0, i.e. they are logged in the CONSLOG file only. You will find detailed information on the CONSLOG file (log file) in the “Introduction to System Administration” manual [5].
For successful processing
NDE1073For unsuccessful processing
NDE2007
Examples
/RESTORE-FROM-SNAP UNIT=*BY-PUBSET(PUBSET=TFS),
SNAP-UNIT=*FROM-SHOW-OUTPUT(POSITION=*LAST)
/RESTORE-FROM-SNAP UNIT=*BY-VOLUME(VOLUME=TFS.00)
Command return codes
(SC2) | SC1 | Maincode | Meaning |
0 | CMD0001 | Command executed successfully | |
1 | 0 | NDE2003 | Command successfully executed, no processing necessary |
2 | 0 | NDE2004 | Command successfully executed but not yet completed |
1 | CMD0202 | Syntax error | |
32 | NDE2002 | Internal error | |
64 | CMD0087 | Function not permitted in the current input mode or with the current task privileges | |
64 | CMD0216 | Required privilege not available | |
64 | NDE1000 | Device not found or not in the storage system | |
64 | NDE1001 | Device not attached | |
64 | NDE1003 | Data medium not online or not unique | |
64 | NDE1004 | Pubset not found or wrong pubset type | |
64 | NDE1005 | Pubset not homogeneous | |
64 | NDE1006 | Pubset/volume is allocated | |
64 | NDE1008 | Volume cannot be allocated | |
64 | NDE1010 | Enginuity version is not supported (too low) | |
64 | NDE1015 | Device not defined in BS2000 | |
64 | NDE1043 | Pubset type not supported | |
64 | NDE1100 | Invalid pubset state | |
64 | NDE1102 | Not all volumes could be allocated | |
64 | NDE1103 | No reconfiguration lock for pubset | |
64 | NDE1105 | Inconsistent pubset | |
64 | NDE1108 |
| |
64 | NDE1109 |
| |
64 | NDE1114 | Serial number not found | |
64 | NDE1115 | Serial number not unique | |
64 | NDE1116 | Storage system’s logical volume not found | |
64 | NDE1153 | Symmetrix device lock set | |
64 | NDE1154 | Disk belongs to a meta-disk | |
64 | NDE1171 | Target unit is not unique | |
64 | NDE1172 | RA group invalid for the specified unit | |
64 | NDE1430 | No Snap function for device | |
64 | NDE1431 | Different number of devices for units and snap units | |
64 | NDE1434 | Virtual snap unit already used in other pair | |
64 | NDE1435 | Device is a virtual unit | |
64 | NDE1440 | Incorrect state of unit (of a snap pair) | |
64 | NDE1441 | Incorrect state of snap unit | |
64 | NDE1442 | Unit is an SRDF target unit and unit is not in | |
64 | NDE1449 | No snap unit assigned to specified snap unit | |
64 | NDE1453 | Device is not a snap unit | |
64 | NDE1454 | Device is unused snap unit | |
64 | NDE1702 | Connection to SYMAPI server aborted | |
64 | NDE1800 | Device not found or not in the storage system | |
64 | NDE1802 | Error communicating with StorMan server | |
64 | NDE1803 | Management instance not available | |
64 | NDE1810 | Storage system’s operating system version not supported | |
64 | NDE1811 | Function not supported for storage system | |
64 | NDE1812 | StorMan server switched off by command | |
64 | NDE1814 | Storage system’s serial number not found | |
64 | NDE1815 | Storage system’s serial number not unique | |
64 | NDE1816 | Storage system’s logical volume not found | |
64 | NDE1833 | No suitable Storman server found | |
64 | NDE1853 | Storage unit locked | |
64 | NDE2009 | Command aborted with K2 key | |
64 | NDE2011 | Symmetrix license not entered | |
64 | NDE2013 | SYMAPI error in command | |
64 | NDE2014 | StorMan error in command | |
64 | NDE2017 | Command not possible for current status of the replication | |
64 | NDE2018 | Error on SYMAPI server during the current editing | |
64 | NDE2020 | No license for local replication (ETERNUS DX/AF) | |
130 | NDE1082 | Memory bottleneck during processing of command | |
130 | NDE2005 | Command cannot be executed at the moment |