Hi John,
We did this about 3 years ago to one of our ADSM servers. The approach that we took
was to duplicate the entire ADSM database onto the new machine and then remove about
half of the client from each machine. Once the database was duplicated we locked every
node defintion where the node should be backing up to the other server. Then we
deleted the filespaces and node defintions.
Of course this will only work if you use collocation for your tape storage pools and
you do have to be careful as to which tapes get checked into each machine but it was
relatively painless and a lot less work than having to do exports.
An additional advantage is that to a certain degree, one all of the nodes are backing
up to their respective servers you have as long as you want to remove the redundant
data from the database.
regards,
Trevor
-----Original Message-----
From: John Haight [mailto:[EMAIL PROTECTED]]
Sent: Wednesday,27 September 2000 7:46
To: [EMAIL PROTECTED]
Subject: Upgrading from ADSM 3.1.2.50 to TSM 3.7.x
I would like to migrate my ADSM 3.1.2.50 data to TSM 3.7.x.
I have out grown my existing hardware and would like to divide up the ADSM data
to 2 new TSM servers. All my ADSM/TSM servers are connected to the same 3494
tape library (8 3590E drives).
In theory, I should be able to export the meta data of which tapes hold which
data and check out those tape and check them back into the new TSM servers.
What are the export and import commands to issue? Any additional thoughts?
Thanks...
John Haight
Dynegy, Inc
[EMAIL PROTECTED]
------------------------------------------------------------------------------
This message and any attachment is confidential and may be privileged or otherwise
protected from disclosure. If you have received it by mistake please let us know by
reply and then delete it from your system; you should not copy the message or disclose
its contents to anyone.
