RESTORE-PUBSET-FROM-SNAPSET

Restore a pubset on the basis of a Snapset

Component:	BS2000 OSD/BC
Functional area:	Pubset and MRSCAT management
Domain:	MULTI-CATALOG-AND-PUBSET-MGMT SNAPSET
Privileges:	TSOS HSMS-ADMINISTRATION

Function

The RESTORE-PUBSET-FROM-SNAPSET command resets a pubset which is in the INACCESSIBLE state to the status of a Snapset.

This command is executed only if the pubset has not been reduced by one or more volumes since the Snapset to be used for restoration was created.

If the system run aborts while this command is being executed, the pubset can remain in an intermediate state which corresponds to partial execution of the command. In this case restoration can be completed by calling the command again. The pubset is locked until the command has been executed fully.

When remote mirroring is being used and snap copies are also generated in the remote storage system, the pubset is restored using the snap units of the original units which are directly attached. These are identified automatically by the Snapset management.

Note on the disk storage systems

• For EMC with TimeFinder/Snap
  Reconstruction of a pubset can only be executed from the most recent of the Snapsets which exist for this pubset.
  The Snapset used for reconstruction can then not be used anymore, and is automatically deleted after the reconstruction process has been completed. Older Snapsets, however, are retained, and can then still be used.
  When a pubset is to be reset to the status of an older Snapset, this can only be done by means of repeated reconstruction, each time based on the most recent Snapset, through to the required Snapset.

• For ETERNUS and EMC with TimeFinder/SnapVX
  Reconstruction of a pubset can be executed on any Snapset version in one step. All Snapset versions, also the version used for reconstruction, are retained and can still be used, e.g. also for another reconstruction.

Format

RESTORE-PUBSET-FROM-SNAPSET                                                                                                       

PUBSET = <cat-id 1..4>

,SNAPSET = *LATEST / <name 1..1 with-low> / <integer -52..-1>

Operands

PUBSET = <cat-id 1..4>
Catalog ID of the pubset which is to be restored.

SNAPSET = 
Specifies the Snapset from which the pubset is to be restored.

SNAPSET = *LATEST
The pubset is restored on the basis of the latest Snapset.

The pubset concerned does not have to be importable for the reconstruction. The F5 label reconstruction takes place when the reconstructed pubset is imported.

SNAPSET = <name 1..1 with-low> / <integer -52..-1>
Not permitted for Symmetrix systems.
The pubset is restored on the basis of the explicitly specified Snapset (specification of the Snapset ID or of the relative age).

While the function is being executed, the pubset is implicitly imported, and it is exported when the function ends. Implicit F5 label reconstruction also takes place.

Return codes

(SC2)	SC1	Maincode	Meaning/Guaranteed messages
	0	CMD0001	Command executed without error
	32	CMD0216	Required authorization not available
	64	DMS13D5	The Snapset specified does not exist on the pubset
	64	DMS3001	Internal error
	64	DMS3002	Error in message output
	64	DMS3003	Error when requesting more space
	64	DMS3006	DMS error
	64	DMS340D	Error while reserving the disk
	64	DMS3405	Existing pubset type does not match MRSCAT entry
	64	DMS3406	No MRSCAT entry for specified catalog ID
	64	DMS3410	Pubset not in INACCESSIBLE state
	64	DMS3411	VSN not unique
	64	DMS3412	Device management reports volume inconsistency
	64	DMS3414	Pubset does not contain a Snapset catalog
	64	DMS3415	While ascertaining the volumes of the SM pubset, an error occurred when an SVL was accessed
	64	DMS3416	Pubset contains fewer volumes than the Snapset
	64	DMS3417	Error while restoring the snap unit
	64	DMS3418	Error while terminating the snap unit
	64	DMS3419	Snap device is not assigned to the device
	64	DMS341A	Device could not be attached
	64	DMS341B	No Snapset was found for a volume of the pubset
	64	DMS341C	Pubset will be processed by PVSREN
	64	DMS341F	Pubset no longer contains specific volume
	64	DMS3423	Only SNAPSET=*LATEST is permitted for the storage system available
	64	DMS3500	SHC-OSD subsystem is not available
	64	DMS3503	Error while calling the reported interface

Notes

• The pubset which is to be restored must be exported. Until the restore operation has been completed, it is protected against being placed in service by /IMPORT-PUBSET (the PVSREN indicator is set in the SVL). During this period, import attempts are  rejected with the message DMS0351 and insert 03. If the data from the snap units is already being copied back, the rejection is indicated by the messages DMS0381 and DMS038F.

• During the restore operation, a temporary copy of the Snapset catalog of the pubset which is to be restored is created on the home pubset and given the file name $TSOS.SYSWRK.SNAPSET.<catid>. This file is only required for restoration and is deleted again once the operation has been completed. During the restore operation it is protected against being deleted because it is used to restart any interrupted restore operation (the command must be called again if the operation is interrupted). If the pubset is restored in a different way, the pubset is deleted when the next pubset import takes place.

• An interrupted restore operation can only be restarted in the same runtime environment, i.e. with the same home pubset, because the copy of the Snapset catalog which is stored there is required for this purpose.