
A
three-site
Metro/Global
Mirror
configuration
provides
the
following
recovery
options
at
the
alternate
sites
if
a
failure
occurs:
v
If
an
outage
occurs
at
the
local
site,
recovery
operations
can
begin
at
the
intermediate
site.
Global
Mirror
continues
to
mirror
updates
between
the
intermediate
and
remote
sites,
maintaining
the
recovery
capability
at
the
remote
site.
v
If
an
outage
occurs
at
the
local
site,
recovery
operations
can
begin
at
the
remote
site
and
preparations
can
be
made
to
resynchronize
the
local
site
when
it
recovers
from
its
disaster.
Once
in
recovery
mode
at
the
remote
site,
another
Global
Mirror
session
can
be
set
up
and
put
into
operation
using
the
former
intermediate
as
its
new
remote
site.
This
new
Global
Mirror
session
provides
additional
disaster
recovery
while
operating
at
the
remote
site.
v
If
an
outage
occurs
at
the
intermediate
site,
data
at
the
local
storage
unit
is
not
affected.
Applications
continue
to
run
normally.
v
If
an
outage
occurs
at
the
remote
site,
data
at
the
local
and
intermediate
sites
is
not
affected.
Applications
continue
to
run
normally.
The
intermediate
storage
unit
maintains
a
consistent
up-to-date
copy.
v
If
both
the
local
and
intermediate
sites
are
lost,
the
scenario
is
similar
to
a
two-site
scenario
when
access
to
the
local
storage
unit
is
lost.
Recovery
must
be
achieved
using
the
last
consistent
point-in-time
copy
at
the
remote
site.
Consistency
group
formation
in
a
Metro/Global
Mirror
environment
Consistency
groups
in
a
Metro/Global
Mirror
environment
create
a
consistent
point-in-time
copy
of
multiple
volumes,
with
negligible
host
impact.
If
there
is
a
disaster
at
the
local
site,
data
consistency
must
be
maintained
across
multiple
volumes.
This
requires
ensuring
that
consistency
groups
form
successfully
at
the
remote
site
and
are
valid
to
use.
(A
consistency
group
keeps
data
consistent
across
multiple
volumes
in
multiple
storage
units.)
There
are
two
methods
of
maintaining
consistent
data
in
a
Metro/Global
Mirror
configuration:
Metro
Mirror
The
freeze
function
that
is
part
of
Metro
Mirror
operations
provides
data
consistency
for
a
Metro
Mirror
environment.
The
freeze
function
can
be
used
by
external
automation
software
to
ensure
data
consistency
to
multiple
Metro
Mirror
volume
pairs
in
a
specified
LSS.
External
automation
software
can
detect
messages
that
are
generated
by
Metro
Mirror
processing
errors.
You
can
temporarily
suspend
write
operations
to
the
volume
pairs
that
are
associated
with
the
specified
LSS.
This
ensures
a
point
of
consistency
at
the
remote
site,
across
all
necessary
volumes
in
the
specified
LSSs.
Afterwards,
you
can
resume
host
I/O
on
the
volumes
pairs.
Global
Mirror
The
integrated
consistency
capabilities
of
Global
Mirror,
which
uses
a
master
storage
unit
(along
with
optional
subordinate
storage
units)
internally
manage
data
consistency
using
consistency
groups
in
a
Global
Mirror
environment.
Note:
The
consistency
of
the
Global
Mirror
replication
depends
on
the
consistency
of
the
Metro
Mirror
target
volumes.
Otherwise,
even
though
the
Global
Mirror
target
volumes
will
be
a
valid
copy
of
the
Global
Mirror
source
volumes
during
the
mirroring
process,
they
might
not
necessarily
be
a
valid
copy
of
the
production
volumes.
122
DS8000
User’s
Guide
Summary of Contents for DS8000 - ADDITIONAL INFORMATION
Page 1: ...IBM System Storage DS8000 User s Guide V ersion 1 Release 4 SC26 7915 02 ...
Page 2: ......
Page 3: ...IBM System Storage DS8000 User s Guide V ersion 1 Release 4 SC26 7915 02 ...
Page 8: ...vi DS8000 User s Guide ...
Page 10: ...viii DS8000 User s Guide ...
Page 12: ...x DS8000 User s Guide ...
Page 14: ...xii DS8000 User s Guide ...
Page 26: ...xxiv DS8000 User s Guide ...
Page 106: ...78 DS8000 User s Guide ...
Page 168: ...140 DS8000 User s Guide ...
Page 202: ...174 DS8000 User s Guide ...
Page 204: ...176 DS8000 User s Guide ...
Page 212: ...184 DS8000 User s Guide ...
Page 242: ...214 DS8000 User s Guide ...
Page 246: ...218 DS8000 User s Guide ...
Page 249: ......
Page 250: ... Printed in USA SC26 7915 02 ...