text: **11.1.9 Incremental FlashCopy**
  
  When a FlashCopy mapping is stopped, either because the entire source volume was copied 
  onto the target volume or because a user manually stopped it, the bitmap table is reset. 
  Therefore, when the same FlashCopy is started again, the copy process is restarted from the 
  beginning. 
  
  Using the**-incremental**option when creating the FlashCopy mapping allows the system to 
  keep the bitmap as it is when the mapping is stopped. Therefore, when the mapping is started 
  again (at another point-in-time), the bitmap is reused and only changes between the two 
  copies are applied to the target. 
  
  A system that provides Incremental FlashCopy capability allows the system administrator to 
  refresh a target volume without having to wait for a full copy of the source volume to be 
  complete. At the point of refreshing the target volume, for a particular grain, if the data 
  changed on the source or target volumes, the grain from the source volume is copied to the 
  target. 
  
  The advantages of Incremental FlashCopy are only useful if a previous full copy of the source 
  volume was obtained. Incremental FlashCopy only helps with further recovery time objectives 
  (RTOs, time needed to recover data from a previous state), it does not help with the initial 
  RTO. 