The background copy may have a slight impact on your application because the
needs some storage resources, but the impact is minimal because the host I/O is prior to the background copy. And if you want, you can issue FlashCopy with the no background copy
option.
No background copy option
If you invoke FlashCopy with the no background copy option, the FlashCopy relationship is established without initiating a background copy. Therefore, you can minimize the impact of the background copy. When the ESS receives an update to a source track in a FlashCopy relationship, a copy of the
Benefits of FlashCopy
The
Point-in-Time Copy function authorization
FlashCopy is an optional function. To use it, you must purchase the
6.2.2 FlashCopy options
FlashCopy has many options and expanded functions to help provide data duplication. We explain these options and functions in this section.
Refresh target volume (also known as Incremental FlashCopy)
Refresh target volume provides the ability to refresh a LUN or volume involved in a FlashCopy relationship. When a subsequent FlashCopy operation is initiated, only the tracks changed on
both the source and target need to be copied from the source to the target. The direction of the refresh can also be reversed.
In many cases, at most 10 to 20 percent of your entire data is changed in a day. In such a situation, if you use this function for daily backup, you can save the time for the physical copy of FlashCopy.
Figure 6-2 on page 93 explains the architecture for Incremental FlashCopy.
92DS6000 Series: Concepts and Architecture