User`s guide

Although the operations involved in most data snapshot processes are
commonplace, the reaction in response to failures during the operation is heavily
influenced by each installation’s operational needs. For this reason, CLONE does
not attempt to automate the error recovery process. If you encounter an error
during a CLONE operation, you will need to resolve the situation by manually
issuing the appropriate CLI commands.
The following circumstance will cause CLONE to cease operation:
1. If the controller is reset or there is a power loss.
2. If the host moves the unit being copied from one controller to the other.
3. If you change the configuration of the unit while CLONE is running.
4. If a disk device being used by CLONE fails.
5. If the CLONE utility is aborted via ^Y or ^C.
6. If the controller fails.
In most cases, CLONE can automate the operation entirely, and will complete
successfully without intervention. In those cases where it cannot complete, it
stops at the point the error occured. The CLI operations performed so far have
been output and are displayed on your terminal screen.
Recovering partially completed CLONE operations requires you to be familiar
with the data snapshot process as described in Section 6.10.1. The recovery
strategy is to decide what follow-on operations will best meet your operational
needs. You can continue the data snapshot operation to completion by manually
issuing the remaining commands in the sequence. You can undo the actions
CLONE has taken by issuing appropriate CLI commands to reverse them.
Alternatively, you can decide that some entirely different course of action
is appropriate, and issue the appropriate CLI commands to proceed in that
direction.
Each of the four CLONE examples that follow contain a detailed discussion
of the typical sequence of operations that CLONE will perform for each of the
legal target configurations. If a CLONE operation does not complete, use these
template sequences and your knowledge of data snapshot operations in general to
guide a manual recovery session.
Any unit created by CLONE has a mirrorset level in the configuration heirarchy,
even if the original unit did not have mirroring. The CLONE utility uses
mirrorsets during copying and must maintain that structure when it adds the
cloned disk as a newly-created unit. The steps below illustrate this concept:
1. CLONE is run on a single-disk unit.
2. CLONE creates a mirrorset from the single disk and adds the target disk to
the mirrorset. The target disk is initialized as a member of a mirrorset when
it is added.
3. The data on the first member of the mirrorset is copied to the new (target)
member.
4. When the copy is complete, CLONE removes the target drive from the
mirrorset, and then sets the original disk so that it is no longer a mirrorset.
5. Because the target disk was initialized as a mirrorset member, CLONE makes
it into a single-member mirrorset to preserve the metadata before adding it
as a unit.
7–86 Diagnostics and Utilities