## 5.2.1 The FlashCopy background copy 

By default, standard FlashCopy (also called FULL copy ) starts a background copy process that copies all point-in-time data to the target volume. After the completion of this process, the FlashCopy relationship ends and the target volume becomes independent of the source. 

The background copy can slightly affect application performance because the physical copy needs storage resources. The impact is minimal because host I/O always has higher priority than the background copy. 

## 5.2.2 No background copy option 

A standard FlashCopy relationship can also be established by using the NOCOPY option. With this option, FlashCopy does not start a background copy. Point-in-time data is copied only when a copy is required due to an update to the source or target. This option eliminates the impact of the background copy. 

## 5.2.3 Benefits and use 

The NOCOPY option is useful in the following situations: 

GLYPH<SM590000> When the target is not needed as an independent volume 

GLYPH<SM590000> When repeated FlashCopy operations to the same target are expected 

The point-in-time copy that is created by FlashCopy often is used when you need to produce a copy of the production data with little or no application downtime. Use cases for the point-in-time copy that is created by FlashCopy include online backup, testing new applications, or creating a copy of transactional data for data mining purposes. To the host or application, the target looks exactly like the original source. It is an instantly available binary copy. 

## 5.2.4 FlashCopy options 

FlashCopy provides many more options and functions. These options and capabilities are described in this section: 

GLYPH<SM590000> Persistent FlashCopy 

GLYPH<SM590000> Incremental FlashCopy (refresh target volume) 

GLYPH<SM590000> Multiple relationship FlashCopy 

GLYPH<SM590000> Data Set FlashCopy 

GLYPH<SM590000> Consistency Group FlashCopy 

GLYPH<SM590000> FlashCopy on existing Metro Mirror or Global Copy primary 

GLYPH<SM590000> Inband commands over remote mirror link 

## Persistent FlashCopy 

Persistent FlashCopy allows the FlashCopy relationship to remain even after the (FULL) copy operation completes. You must explicitly delete the relationship to end it. 

## Incremental FlashCopy (refresh target volume) 

Incremental FlashCopy requires that the background copy and the Persistent FlashCopy options are enabled. The first full copy must be complete. 

