Your Browser is not longer supported

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

{{viewport.spaceProperty.prod}}

Working with clones

SHC-OSD provides information services and commands for controlling the QuickOPC, EC and TimeFinder/Clone functions.

When the SHC-OSD commands for pubsets, MN or VSN of BS2000 are called, SHC-OSD automatically discovers the type of storage system and maps the call to the corresponding function.

The copy process for QuickOPC and EC is always started with the /START-CLONE command. The EC clone pair must already have been copied fully and be consistent when activation takes place with the /ACTIVATE-CLONE command. In the case of TimeFinder/Clone, on the other hand, starting the copy process with /START-CLONE is only an option. It can also be started only when /ACTIVATE-CLONE-SESSION is issued, or not at all. (See also the difference in the statuses in section "Status of the clone session and of the devices".)

The devices which are controlled using these commands must be attached on the server.
/MODIFY-SHC-PROCESSING also permits (not-defined) devices which are detached or are not connected directly to the server to be controlled.

Clone pairs are managed in clone sessions. Clone sessions, on the other hand, are managed on the storage system.