Terminology; Basic Concepts - IBM System storage DS6000 Series Redbook

Integration system
New application releases (for example, SAP® releases) are likely to be tested prior to
putting them onto a production server. By using FlashCopy, a copy of the production data
can be established and used for integration tests.
With the capability to reverse a FlashCopy, a previously created FlashCopy can be used
within seconds to bring production back to the level of data it had at the time when the
FlashCopy was taken.

6.2 Terminology

When discussing Metro Mirror, Global Copy and Global Mirror, the following terms are
frequently used and interchangeable:
The terms
production applications run while in normal operation. These applications create, modify,
and read the data—the application data. The meaning is extended to the disk subsystem
that holds the data as well as to its components—volumes and LSS.
The terms
data is replicated—the copy of the application data. The meaning is extended to the disk
subsystem that holds the data as well as to its components—volumes and LSSs.
When discussing FlashCopy we use the term
created by the application. We use the term
Also, the terms LUN and

6.3 Basic concepts

In a System z environment, FlashCopy can be used at volume level and at data set level.
Note: Whenever
refers to both a volume or a data set.
By doing a FlashCopy, a relationship is
considered to form a FlashCopy
As result of the FlashCopy either all physical blocks from the source volume are copied (full
copy) or—when using the
data since the FlashCopy was established. Currently, the target volume needs to be the
same size or bigger than the source volume whenever FlashCopy is used to flash a whole
volume.
Typically, large applications such as databases have their data spread across several
volumes; their volumes should all be FlashCopied at exactly the same point-in-time.
FlashCopy offers consistency groups, which allows multiple volumes to be FlashCopied at
exactly the same instance.
The following are basic characteristics of FlashCopy operation:
Establish FlashCopy relationship
When the FlashCopy is started, the relationship between source and target is established
within seconds. This is done by creating the necessary metadata such as a pointer table,
including a bitmap for the target.
local production application
, ,
remote recovery backup
, ,
volume
are used interchangeably in our discussions.
source target
or is used in this chapter without further specification, it
pair
.
nocopy
option—only those parts that are changing in the source
primary source
, , and
secondary target
, , and , denote the site to where the
source
to refer to the original data that is
target
to refer to the point-in-time backup copy.
established
between a source and a target. Both are
Chapter 6. FlashCopy overview
, denote the site where the
45