FlashCopy mapping events details the events that modify the state of a
FlashCopy mapping.
- Create
- A new FlashCopy mapping is created between the specified source virtual
disk and the specified target virtual disk. The various supported parameters
are also described there. The operation fails if either the source or target
virtual disks are already a member of a FlashCopy mapping. The operation fails
if the SAN Volume Controller has insufficient bitmap memory. The operation also fails if the
source and target virtual disks are different sizes.
- Prepare
- The prepare command is directed to either a consistency group for FlashCopy
mappings which are members of a normal consistency group or to the mapping
name for FlashCopy mappings which are members of the special consistency group
0. The prepare command places the FlashCopy mapping in the preparing state.
It is important to note that the act of preparing for start may corrupt any
data which previously resided on the target virtual disk since cached writes
are discarded. Even if the FlashCopy mapping is never started, the data from
the target may have been logically changed by the act of preparing for start.
- Flush done
- The FlashCopy relationship moves from the preparing state to the prepared
state automatically once all cached data for the source has been flushed and
all cached data for the target has been invalidated.
- Start
- When all the FlashCopy mappings in a consistency group are in the prepared
state, the FlashCopy relationships can be started. Some other FlashCopy products
refer to this event as starting the FlashCopy.
The start of all of the
FlashCopy mappings in the consistency group must be synchronized correctly
with respect to I/Os directed at the virtual disks to preserve the cross volume
consistency group. This is achieved as follows:
During the start command:
- New reads and writes to all source virtual disks in the consistency group
are paused in the cache layer until all ongoing reads and writes below the
cache layer have been completed.
- Once all FlashCopy mappings in the consistency group have been paused,
internal cluster state is set to allow FlashCopy operations.
- Once all FlashCopy mappings in the consistency group have had their cluster
state set, read and write operations are unpaused on the source virtual disks.
- The target virtual disks are brought online.
As part of the start command, read and
write caching is enabled for both the source and target virtual disks.
- Modify
- A FlashCopy mapping has two properties which can be modified. These are the
background copy rate and the consistency group. The
background copy rate can be modified in any state but attempting to modify
the consistency group in any state other than idling, copied, or stopped will
fail.
- Stop
- There are two
mechanisms by which a FlashCopy mapping can be stopped:
- Either you have issued a command; or
- An input/output (I/O) error has occurred.
- Delete
- This command requests that the specified FlashCopy mapping be deleted.
If the FlashCopy mapping is in the stopped state, the force flag must be used.
Deleting a FlashCopy mapping in the stopped state may allow unflushed write
data from the cache to be destaged to what was the target virtual disk. This
does not affect the data integrity of the system because following a forced
delete, nothing can be certain about the contents of the target virtual disk.
The data contained in the target virtual disk could be anything.
The
destaging of old data to what was the target virtual disk does not affect
the future use of the virtual disk because any new data will be written over
this old data, in the cache or on disk.
- Flush failed
- If the flush of data from the cache cannot be completed then FlashCopy
mapping will enter the stopped state.
- Copy complete
- Once every grain of the source and target has been copied, the source
and target are independent and the state machine enters the copied state.
The FlashCopy mapping is not automatically deleted at this time and can be
re-activated by preparing and starting again.
- Bitmap Online/Offline
- The node has failed.