Your Browser is not longer supported

Please use Google Chrome, Mozilla Firefox or Microsoft Edge to view the page correctly
Loading...

{{viewport.spaceProperty.prod}}

RESUME-REMOTE-COPY Resumes remote copy mode

&pagelevel(3)&pagelevel

Storage system:

ETERNUS DX/AF

Domain:

DEVICE

Privileges:

TSOS


/RESUME-REMOTE-COPY reactivates remote copy mode after it has been interrupted (for example using /HOLD-REMOTE-COPY).

The command is effective in both synchronous and asynchronous processing modes (COPY-MODE).

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 REC

While remote copy mode is interrupted (remote copy status IN-HOLD), data on the source unit and target unit can be modified. The RESTORE operand can be used to specify the copy direction for subsequent synchronization of the remote copy pair. WAIT=*UNTIL-SYNCHRONIZATION ensures that the command waits for synchronization to terminate in both synchronous and asynchronous processing mode.

REC replication can be resumed immediately after use of the target unit has terminated (READY status). It is not necessary to explicitly detach the target units (to the NOT-READY status).

Original units can be reconstructed directly from the target units in synchronous processing mode (RESTORE=*TO-SOURCE).

Reconstruction is performed internally in SHC-OSD in the following individual steps:

  1. /SWAP-REMOTE-COPY to swap the source/target relationship

  2. /RESUME-REMOTE-COPY to reconstruct the "new" source on the "new" target

  3. /HOLD-REMOTE-COPY as a prerequisite for another swap

  4. /SWAP-REMOTE-COPY to restore the source/target relationship

  5. /RESUME-REMOTE-COPY to resume the original remote replication

Following reconstruction, the remote copy pair is once again in the ACTIVE state.

RESUME-REMOTE-COPY

UNIT = *BY-VOLUME(...) / *BY-PUBSET(...) / *BY-STORAGE(...) /




list-poss(256): <alphanum-name 2..2> / <x-text 4..4>


*BY-VOLUME(...)



|

VOLUME = <vsn 1..6>


*BY-PUBSET(...)



|

PUBSET = <cat-id 1..4>



|

,RENAME-PUBSET = *NO / *SAME / <cat-id 1..4>


*BY-STORAGE(...)



|

SERIAL-NUMBER = <alphanum-name 3..14>



|

,LOGICAL-VOLUME = *ALL-SOURCE-UNITS(...) / <x-text 1..4>



|


*ALL-SOURCE-UNITS(...)



|



|

SELECT = *ANY / *ALL-DEFINED / *ATTACHED

,RESTORE = *FROM-SOURCE / *TO-SOURCE(...)


*TO-SOURCE(...)



|

CONCURRENT-TARGET = *REJECT-IF-ACTIVE / *ALLOW

,WAIT = *STD / *NO / *UNTIL-SYNCHRONIZATION

,TARGET-UNIT = *UNIQUE / *ALL / *FIRST-POSSIBLE / *BY-STORAGE(...) /







<alphanum-name 2..2> / <x-text 4..4>


*BY-STORAGE(...)



|

TARGET-SERIAL-NUMBER = <alphanum-name 3..14>


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-STORAGE), or directly by means of the logical volume's mnemonic device name.
If VOLUME or PUBSET is specified, the action is automatically performed for the correct unit (i.e. the source unit). If a mnemonic name or the internal name in the storage system (*BY-STORAGE) was specified, only source units are permissible.

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.

RENAME-PUBSET =
Selects the pubset ID to which the source units of the pubset are to be renamed after /RESUME-REMOTE-COPY when RESTORE=*TO-SOURCE is specified.

RENAME-PUBSET = *NO
The pubset is not renamed, i.e. the catalog ID of the target units remains unchanged.

RENAME-PUBSET = *SAME
The pubset is assigned the catalog ID of the original before /RESUME-REMOTE-COPY.

RENAME-PUBSET = <cat-id 1..4>
Explicit specification of the new pubset ID.

UNIT = *BY-STORAGE(...)
Selects the units by means of the serial number and 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 = *ALL-SOURCE-UNITS(...)
Selects the source units of the specified storage system.

SELECT = *ANY
Selects all source units of the specified storage system.

SELECT = *ALL-DEFINED
Selects all source units (generated in BS2000) of the specified storage system.

SELECT = *ATTACHED
Selects all source units (attached in BS2000) of the specified storage system.

LOGICAL-VOLUME = <x-text 1..4>
Specifies the internal number of the logical volume in the storage system.

UNIT = list-poss(256): <alphanum-name 2..2> / <x-text 4..4>
Selects the unit by means of the mnemonic device name of the logical volume.


RESTORE =
Specifies the copy direction when data on the source unit and target unit differs.

RESTORE = *FROM-SOURCE
Copies from the source unit to the target unit.

RESTORE = *TO-SOURCE(...)
Copies from the target unit to the source unit.

CONCURRENT-TARGET =
Determines the behavior if the source unit has a second target unit with the ACTIVE state.

CONCURRENT-TARGET = *REJECT-IF-ACTIVE
The command is rejected if the source unit has a second target unit with the ACTIVE state.

CONCURRENT-TARGET = *ALLOW
If the source unit has a second target unit with the *ACTIVE state, the latter is also updated.

To ensure data consistency, the copy direction *TO-SOURCE is accepted only if no local pending writes are noted on the target unit.
The source units must not be allocated (export pubset).
*TO-SOURCE is only possible for synchronous REC, also when WAIT=*UNTIL-SYNCHRONIZATION is specified.


WAIT =
Specifies whether or not the command is to wait until synchronization is complete.

WAIT = *STD
WAIT=*UNTIL-SYNCHRONIZATION is used for ETERNUS DX/AF.

WAIT = *NO
The command does not wait until synchronization is complete.

WAIT = *UNTIL-SYNCHRONIZATION
The command waits until synchronization is complete.
WAIT=*UNTIL-SYNCHRONIZATION simplifies the programming of test procedures for recovery because extensive queries regarding the synchronization progress of the remote copy pair are unnecessary. Waiting can be aborted in dialog mode by hitting the K2 key.


TARGET-UNIT =
Controls selection of the target unit for concurrent remote copy.

TARGET-UNIT = *UNIQUE
Remote copy mode is restarted for the one existing target unit.

TARGET-UNIT = *ALL
Remote copy mode is restarted for all target units.

TARGET-UNIT = *FIRST-POSSIBLE
Remote copy mode is restarted for the first target unit which allows /RESUME-REMOTE-COPY.

TARGET-UNIT = *BY-STORAGE(...)
Selects the target unit using the serial number in the storage system.

TARGET-SERIAL-NUMBER = <alphanum-name 3..14>
Specifies the serial number of the storage system (make sure it is unique!) with the target unit.

Command processing

The following messages are output to SYSOUT for each remote copy pair 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 NDE1073

  • For unsuccessful processing NDE2007

Examples

/RESUME-REMOTE-COPY UNIT=*BY-VOLUME(VOLUME=RDF.00),RESTORE=*TO-SOURCE

/RESUME-REMOTE-COPY UNIT=*BY-PUBSET(PUBSET=RDF),RESTORE=*FROM-SOURCE

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

3

0

NDE1067

Remote copy pair not yet synchronized

3

0

NDE1068

Refreshing the remote copy pair not successful

3

0

NDE1069

No current information available about some remote copy pairs


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

NDE1002

Controller not found


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

NDE1020

No remote copy function for the specified unit


64

NDE1021

Device is not a source unit


64

NDE1022

Device is or has no target unit


64

NDE1028

Volume not unique in the unit


64

NDE1061

Remote copy state is not IN-HOLD


64

NDE1062

Access to target unit of the remote copy pair is DIRECT


64

NDE1063

Source unit does not have the state READY


64

NDE1064

Target unit in *READY, *READ-ONLY or *DISABLE state


64

NDE1076

Local pending writes are noted on the target unit in the case of RESTORE=*TO-SOURCE


64

NDE1079

None of the selected devices is attached


64

NDE1081

Synchronous command processing not possible


64

NDE1093

Remote copy state no longer ACTIVE


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

NDE1107

No pubset allocation possible


64

NDE1171

Target unit is not unique


64

NDE1173

Source unit has concurrent target unit with ACTIVE state


64NDE1193 Command not allowed for target unit bigger source unit

64

NDE1800

Device not found or not in 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

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

NDE1822

Reconstruction step RESUME-REMOTE-COPY aborted


64

NDE1823

Reconstruction step HOLD-REMOTE-COPY aborted


64

NDE1824

Reconstruction step SWAP-REMOTE-COPY aborted


64

NDE1833

No suitable Storman server found


64

NDE1853

Storage unit locked


64

NDE1861

Remote copy pair is not in IN-HOLD status


64

NDE1866

No remote link available


64

NDE1890

Management instance not found


64

NDE1899

Command not possible for current status of the mirror pair


64

NDE2000

Execution partially successful


64

NDE2001

Command not executed


64

NDE2009

Command aborted with K2 key


64

NDE2014

StorMan error in command


64

NDE2017

Command not possible for current status of the replication


130

NDE1082

Memory bottleneck during processing of command


130

NDE2005

Command cannot be executed at the moment

Powered by Atlassian Confluence and Scroll Viewport.