Point-in-Time Copy (FlashCopy):

When you set up a FlashCopy operation, a relationship is established between the source
and target volumes, and a bitmap of the source volume is created.
Once this relationship and bitmap are created, the target volume can be accessed as
though all the data had been physically copied.
While a relationship between the source and target volume exists, optionally, a background
process copies the tracks from the source to the target volume.
Read from the source volume
When you read some data from the source volume, it is simply read from the source
volume.
Read from the target volume
When you read some data from the target volume, FlashCopy checks the bitmap and:
If the backup data is already copied to the target volume, it is read from the target
volume.
If the backup data is not copied yet, it is read from the source volume.
Write to the source volume
When you write some data to the source volume, at frst the updated data is written to the
data cache and persistent memory (write cache). And when the updated data is destaged
to the source volume, FlashCopy checks the bitmap and:
If the backup data is already copied, it is simply updated on the source volume.
If the backup data is not copied yet, frst the backup data is copied to the target volume,
and after that it is updated on the source volume.
Write to the target volume
When you write some data to the target volume, it is written to the data cache and
persistent memory, and FlashCopy manages the bitmaps to not overwrite
Remote Mirror and Copy (Peer-to-Peer Remote Copy)
Metro Mirror (ynchronous PPRC)
Metro Mirror provides real-time mirroring of logical volumes between two DS8000s that can
be located up to 300 km from each other.
It is a synchronous copy solution where write operations are completed on both copies (local
and remote site) before they are considered to be complete.
!lo"al Copy (PPRC-#$):
Global Copy copies data non-synchronously and over longer distances than is
possible with Metro Mirror.
When operating in Global Copy mode, the source volume sends a periodic,
incremental copy of updated tracks to the target volume, instead of sending a constant
stream of updates.
This causes less impact to application writes for source volumes and less
demand for bandwidth resources, while allowing a more fexible use of the available
bandwidth.
Global Copy does not keep the sequence of write operations.
The copy is normally fuzzy, but you can make a consistent copy through synchronization.
!lo"al Mirror (%synchronous PPRC)
Global Mirror provides a long-distance remote copy feature across two sites using
asynchronous technology. This solution is based on the existing Global Copy and FlashCopy.
With Global Mirror, the data that the host writes to the storage unit at the local site is
asynchronously shadowed to the storage unit at the remote site. A consistent copy of the data
is automatically maintained on the storage unit at the remote site.
The A volumes at the local site are the production volumes and are used as Global Copy
primary volumes. The data from the A volumes is replicated to the B volumes, which are
Global Copy secondary volumes. At a certain point in time, a Consistency Group is created
using all of the A volumes.
Once the Consistency Group is created, the application writes can continue updating the A
volumes. The increment of the consistent data is sent to the B volumes using the existing
Global Copy relationship. Once the data reaches the B volumes, it is FlashCopied to the C
volumes.