Data migration, Appendix, Legacy – IBM TIVOLI SC32-0129-00 User Manual
Page 69: Acsls, Data, Migration, Coexistence
Appendix
B.
Legacy
ACSLS
Data
Migration
and
Coexistence
Note:
For
the
latest
information
concerning
migration
and
coexistence,
see
the
Tivoli
Storage
Manager
README.
If
your
environment
consists
of
Tivoli
Storage
Manager
storage
pools
associated
with
an
ACSLS
library
type
and
an
ECARTRIDGE
device
type,
the
library
can
be
updated
with
the
SHARED=YES
option
to
enable
LAN-free
data
movement.
If
your
environment
consists
of
Tivoli
Storage
Manager
storage
pools
associated
with
an
ACSLS
library
type
and
a
GENERICTAPE
device
type,
data
migration
is
required
rather
than
coexistence
because
Tivoli
Storage
Manager
ACSLS
shared
library
support
cannot
co-exist
with
external
library
support.
See
the
″Configuring
Storage
Devices
″
chapter
in
the
Administrator’s
Guide
for
detailed
information
on
how
to
migrate
from
an
external
library
environment
to
a
shared
ACSLS
library
environment.
Data
Migration
Data
migration
of
ACSLS
to
external
library
support
is
necessary
only
when
Tivoli
Storage
Manager
ACSLS
shared
library
support
is
not
possible
in
your
configuration.
The
only
situation
where
ACSLS
shared
library
support
is
not
possible
is
when
your
environment
does
not
contain
a
Tivoli
Storage
Manager
server
installed
on
AIX,
Solaris,
or
Windows
to
serve
as
the
library
manager.
Migrate
the
existing
data
from
existing
(old)
storage
pools
to
new
storage
pools
associated
with
the
appropriate
policy,
device
class,
and
library
definitions.
Migration
of
data
also
allows
the
entire
environment
to
be
LAN-free,
providing
better
performance
and
better
utilization
of
tape
drives
and
media.
displays
the
normal
migration
path
from
an
old
storage
pool
containing
the
data
associated
with
the
ACSLS
library
type
to
a
new
storage
pool
associated
with
an
EXTERNAL
library
type
and
an
ECARTRIDGE
device
class.
©
Copyright
IBM
Corp.
2000,
2007
51