Moving optical disk to another library after having migrated tsm server to another box

Resolving The Problem

The easiest way to "move" the ITSM server DB from "old" to "new" machine
would be as follows:
(1) assumption is that the ITSM server DB structure (filenames,
directory paths) can remain the same and that the mass storage
devices (tape library) attached to the "old" machine can be easily
attached to the "new" machine by just moving the hardware
(2) do a FULL backup db on the "old" machine to have it available
in case it's should be necessary
(3) halt the ITSM server on the "old" machine
(4) halt the ITSM server on the "new" machine
It is not necessary to have any configuration, db and log file available
on the "new" machine.
(5) copy, ftp (binary) or just let's say transfer the ITSM server DB and
LOG files from the "old" machine to the "new" machine.
Be sure to use same directory structure and filenames on the "new"
machine! Do NOT resize files! It does NOT help to modify the
dsmserv.dsk file!
Example:
"old" machine... P
database files: /tsmdb/db01.dsm /tsmdb/db02.dsm
log files: /tsmlog/log01.dsm /tsmlog/log02.dsm
must be the same on the "new" machine:
database files: /tsmdb/db01.dsm /tsmdb/db02.dsm
log files: /tsmlog/log01.dsm /tsmlog/log02.dsm
(6) copy the ITSM server configuration files from the "old" to the
"new" machine:
volume.history
device.config
dsmserv.opt
dsmserv.dsk
...and ensure the environment variables DSMSERV_* are set correctly
(also customize the rc.adsmserv startup script if
necessary)
(7) Attach the tape library to the "new" box and run the cfgmgr /
define the devices using smitty:devices:tsm devices...depends on the
tape library hardware used.
If the device special files are not the same on the "new" box as they
were on the "old" box it is necessary to update the ITSM server device
configuration on the "new" box after library initialization failed.
Maybe necessary to update the dsmserv.opt with
"nomigrrecl" option too, in order
to prevent the ITSM server from starting reclamation / migration.
Remove the option and restart the ITSM server after configuration
has been updated.
(8) start the dsmserv process on the "new" box as follows (always
assuming that the environment variables are set correctly)
I) dsmserv upgradedb
II) dsmserv runfile /usr/tivoli/tsm/server/webimages/dsmserv.idl
(9) restart the server as usual...done.
.
It's easily to test this before going into production on the "new"
machine. Test it without moving tape/library hardware first as it is
not needed to upgradedb etc.
.
It is possible to change the ITSM server db / log file structure and
re-arrange them on the new box keeping in mind that this can be
done online later on by adding / removing db / log volumes.
.
If these actions don't work correctly or a fail occurs during test phase,
it is strongly suggested to follow the official procedure which is

(a) update the ITSM server on the old box using following ITSM server
levels:
- latest 4.1 level
- 4.2.0.0 up to latest 4.2 level
- 5.1.0.0 or 5.1.5.0 to latest 5.1 level because 5.1 is the last
ITSM server version supported on AIX 4.3.3
(b) do a full backup db on the "old" box at latest 5.1 server level
(c) install ITSM server 5.1 up to latest level on the "new" box.
This is required as the ITSM server 5.2 is NOT able to restore and
handle ITSM server 5.1 db backups correctly.
Now it is possible to restructure the db / log filenames etc because it's a
new server install.
(d) attach the library / tape hardware to the new box
(e) copy the ITSM server config files from the "old" to the "new" box
as already described above.
Do NOT copy and use the dsmserv.dsk file from the "old" box!!!
(f) recreate the device special files on the "new" box
(g) customize the device config file to match the new device special
filenames if applicable
(h) run 'dsmserv restore db todate=today' with devconfig and volume
history file available
(i) update the ITSM server on the "new" box to 5.2 as usual

If the physical library changes the library within ITSM needs to be
deleted and redefined.
When doing this all library inventory is lost.
Question may be when to delete the library?
Choosing to do backup db / restore db it must be deleted AFTER the restore db has been done and the server's up and running on the new box.
On the "new" server wait until library initialization failed completely
before trying to delete the library definitions within ITSM server.
"Transferring" the database / log files from the "old"
box to the "new" box could be necessary to delete the library definitions
before the transfer of files to the new box and bringing up the "new" server.
This will be faster.
After the library is redefined into ITSM server the actions to get back library volumes are:
1. checkin libvolume 3995_lib search=yes status=scratch
2. checkin libvolume 3995_lib search=yes status=private


It is possible to move the platters from the old 3995 to the new one,keeping the volumes one by one using the export/import slots of the libraries but that may take several time.
It should be better to open the library covers and move them all at a time.
Be sure to physically re-inventory the "new" 3995 after all platters
are physically located in the library.
.
Doing RESTORE DB as described above
the handling of the platters containing the dbb is a little bit more
difficult.
This is because the device config file, the volume history file and the
physical location of the platter in the "new" library does not match
the "old" environment.
It is possible manually loading the platters into one drive and defining a manual
library with one drive only to ITSM for restore db.
This needs to be done by putting the correct entries into the device
config file.
Anyway...the device config file needs to be created manually before
the db can be restored.
Or...another tricky way is to install a "blank" server on the "new"
box, bring it up and define the devices to it as usual.
It could be installed using minimum db / log sizes. It is necessary to have
a server up and running and the device special files to be available.
This will create a device config file to use for restoring the db
later on.
.