Migrating
data
using
the
direct
copy
method
Use
the
following
information
as
a
guide
for
determining
when
to
use
the
direct
copy
method
to
migrate
data
for
a
UNIX
operating
system.
This
method
suffers
from
the
same
drawback
as
using
the
cplv
and
splitlvcopy
commands
on
logical
volumes.
You
can
use
this
method
on
active
file
systems,
but
data
consistency
between
the
original
and
new
copies
cannot
be
guaranteed.
Use
the
cpio
-p
command
only
on
file
systems
that
are
in
a
quiescent
state
to
guarantee
consistency
between
the
copy
and
the
original.
This
will
cause
some
disruption
of
service
to
users
to
occur.
Migrating
data
using
backup
and
restore
methods
Use
the
following
information
as
a
guide
for
determining
when
to
use
backup
and
restore
methods
to
migrate
data.
All
backup
and
restore
methods
require
that
the
file
systems
or
logical
volumes
that
you
are
backing
up
be
in
a
quiescent
state.
Typically,
you
run
backups
after
hours
when
there
is
minimal
use
of
the
system
and
you
can
shut
down
databases.
Some
databases
require
that
you
export
the
data
before
you
move
it
between
file
systems
or
logical
volumes.
You
must
then
import
the
data
on
to
the
new
file
system
or
logical
volume.
You
might
have
to
reconfigure
the
database
so
that
it
points
to
the
new
data
locations.
Migrating
data
from
a
Windows
host
system
Use
the
following
information
as
a
guide
for
how
to
migrate
data
from
a
Windows
Server
2000,
2003,
or
2008
You
can
migrate
data
from
a
Windows
host
system
into
an
storage
unit
by
mirroring
the
data
and
splitting
the
mirrors
(similar
to
the
method
described
for
UNIX
systems).
Create
a
full
backup
of
the
data
before
attempting
any
data
migration.
Migrating
data
maintains
file
ownership,
permissions,
and
the
date
and
time
while
the
copy
is
made.
The
drag-and-drop
function
and
the
xcopy
command
might
cause
ownership
problems
to
date-related
information
in
the
copy
of
the
new
data.
Mirroring
the
data
and
splitting
the
mirrors
requires
some
outage
to
rename
drive
letters
at
the
end
of
the
migration.
If
the
mirroring
tool
that
the
operating
system
supplies
cannot
be
used
(for
example,
if
drive
sizes
in
the
old
and
new
systems
are
not
the
same),
you
might
be
able
to
use
a
third-party
mirroring
tool
to
accomplish
the
same
goal.
If
an
outage
occurs,
you
can
copy
Windows
2000
data
to
the
new
disk
using
the
scopy
command.
Migrating
data
between
storage
units
Migrating
data
between
storage
units
requires
the
use
of
Global
Copy
or
IBM
System
Storage
Metro
Mirror.
Perform
this
process
to
migrate
data
between
storage
units.
1.
Establish
paths
between
all
Site
A
LSSs
and
Site
B
LSSs.
2.
Establish
all
necessary
volume
pairs
between
the
Site
A
storage
units
and
the
Site
B
storage
units.
You
can
use
either
the
Global
Copy
or
the
IBM
System
Storage
Metro
Mirror
feature.
Chapter
9.
Migrating
data
to
a
storage
unit
151
|
|
Содержание DS8000 - ADDITIONAL INFORMATION
Страница 1: ...IBM System Storage DS8000 User s Guide V ersion 1 Release 4 SC26 7915 02 ...
Страница 2: ......
Страница 3: ...IBM System Storage DS8000 User s Guide V ersion 1 Release 4 SC26 7915 02 ...
Страница 8: ...vi DS8000 User s Guide ...
Страница 10: ...viii DS8000 User s Guide ...
Страница 12: ...x DS8000 User s Guide ...
Страница 14: ...xii DS8000 User s Guide ...
Страница 26: ...xxiv DS8000 User s Guide ...
Страница 106: ...78 DS8000 User s Guide ...
Страница 168: ...140 DS8000 User s Guide ...
Страница 202: ...174 DS8000 User s Guide ...
Страница 204: ...176 DS8000 User s Guide ...
Страница 212: ...184 DS8000 User s Guide ...
Страница 242: ...214 DS8000 User s Guide ...
Страница 246: ...218 DS8000 User s Guide ...
Страница 249: ......
Страница 250: ... Printed in USA SC26 7915 02 ...