464 Implementing the IBM Storwize V7000 with IBM Spectrum Virtualize V8.2.1
Path Offline for the source Volume
If a FlashCopy mapping is in the copying state and the source volume goes path offline, this 
path offline state is propagated to all target volumes up to, but not including, the target volume 
for the newest mapping that is 100% copied but remains in the copying state. If no mappings 
are 100% copied, all of the target volumes are taken offline. Path offline is a state that 
exists on a per-node basis. Other nodes might not be affected. If the source volume comes 
online, the target and source volumes are brought back online.
Path Offline for the target Volume
If a target volume goes path offline but the source volume is still online, and if any dependent 
mappings exist, those target volumes also go path offline. The source volume remains online.
11.1.18  Asynchronous notifications
FlashCopy raises informational event log entries for certain mapping and Consistency Group 
state transitions. These state transitions occur as a result of configuration events that 
complete asynchronously. The informational events can be used to generate Simple Network 
Management Protocol (SNMP) traps to notify the user. 
Other configuration events complete synchronously, and no informational events are logged 
as a result of the following events:
/SM590000PREPARE_COMPLETED
This state transition is logged when the FlashCopy mapping or Consistency Group enters 
the prepared state as a result of a user request to prepare. The user can now start (or 
stop) the mapping or Consistency Group. 
/SM590000COPY_COMPLETED
This state transition is logged when the FlashCopy mapping or Consistency Group enters 
the idle_or_copied state when it was in the copying or stopping state. This state 
transition indicates that the target disk now contains a complete copy and no longer 
depends on the source. 
/SM590000STOP_COMPLETED
This state transition is logged when the FlashCopy mapping or Consistency Group enters 
the stopped state as a result of a user request to stop. It is logged after the automatic copy 
process completes. This state transition includes mappings where no copying needed to 
be performed. This state transition differs from the event that is logged when a mapping or 
group enters the stopped state as a result of an I/O error.
11.1.19  Interoperation with Metro Mirror and Global Mirror
A volume can be part of any copy relationship (FlashCopy, Metro Mirror, or Remote Mirror). 
Therefore, FlashCopy can work with MM/GM to provide better protection of the data.
For example, you can perform a Metro Mirror copy to duplicate data from Site_A to Site_B, 
and then perform a daily FlashCopy to back up the data to another location.
Table 11-7 on page 465 lists the supported combinations of FlashCopy and remote copy. In 
the table, remote copy refers to Metro Mirror and Global Mirror.
Note: A volume cannot be part of FlashCopy, Metro Mirror, or Remote Mirror if it is set to 
Transparent Cloud Tiering function.