The .dsm files (disk storage pool volumes) you mention under 2. Below,
can either be migrated to tape, and deleted, then copy all the files you
list under 1., or you can copy them just like the files under 1. Below.
I like the migrate to tape and delete option, that creates fewer things
to go wrong
See IBM Technote 1114874 for the basic approach.
2. How about archive.dsm, backup.dsm, log.dsm
A production system should not have those: they are the "training
wheels", starter pools and Recovery Log spaces established by the TSM
server installation, which one would replace with the subst
For example:
1. You mean copy these files:
dsmserv.dsk
/tsmdata/TSM01/db/db0
/tsmdata/TSM01/db/db1
/tsmdata/TSM01/db/db2
/tsmdata/TSM01/db/db3
/tsmdata/TSM01/db/db4
/tsmdata/TSM01/db/db5
/tsmdata/TSM01/db/db6
/tsmdata/TSM01/db/db7
/tsmdata/TSM01/db/db8
Log1.dsm, log2.dsm
Right?
2. How about arc
Make sure you empty and remove the disk storage pools if you have any
(easiest, then you can just create new ones on the new server), or copy
the volumes for them to the same location on the new server.
See Ya'
Howard
> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:ads...@vm.
Hi
just copy your dsmserv.dsk file, DB&LOG files ( or mirror them if possible
) to your new linux box
install the same TSM release on your new linux box
fire up TSM
it should work :)
Regards
Julien
From:
"ANURADHA.K"
To:
ADSM-L@VM.MARIST.EDU
Date:
30/12/2009 14:01
Subject:
[ADSM-L] sug
