We've performed a couple of migrations (with assistance) to new servers.
Basically we've brought up the new instance.
exported the old server, imported to the new.
stop the scheduler on the client(s) to be migrated.
export the client.
rename the node on the old tsm server
change the dsm.opt file on the client to point to the new tsm server
restart the scheduler on the client
-or- in some cases we simply stopped old / started new
since we were starting fresh in all cases, we didn't have to merge the file
spaces.
Any help in that?
Aaron Durkee
Infrastructure Analyst
Networking and Technical Group
Catholic Health Systems, Inc.
adurkee AT chsbuffalo DOT org
phone: (716) 862-1713
fax: (716) 862-1717
>>> Patricia.Leblanc AT LIBERTYMUTUAL DOT COM 04/05/06 12:56PM >>>
Restore your tsm database to the new server.
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Dennis, Melburn W IT743
Sent: Wednesday, April 05, 2006 12:44 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Export Archive files from one TSM server to another
I recently tried exporting just the archived files of a node registered
on our old TSM server to the same node on our new TSM server that we are
migrating to. On the new server, the node has been backing up without
any problems. I executed the below command:
export node NODENAME filedata=archive toserver=SERVERNAME
mergefilespaces=yes
When I did this, it created some new filespaces that existed on the old
tsm server onto the new tsm server. Basically I now had 2 c$ filespaces
as well as 2 d$ filespaces (one unicode, one not). All of a sudden, the
client started to backup to the newly created c$ and d$ filespace that
were not unicode and acted as if the client had never backed up before,
so it did a full backup. Why is this? I just want to export all of our
archived data to the new TSM server so we can shutdown the old one. Any
suggestions?
Mel Dennis
-------------------------
CONFIDENTIALITY NOTICE: This message is confidential, intended only for the
named recipient(s) and may contain information that is privileged, or exempt
from disclosure under applicable law. If you are not the intended recipient(s),
you are notified that the dissemination, distribution or copying of this
message is strictly prohibited. If you receive this message in error, or are
not the named recipient(s), please notify the sender by reply e-mail, delete
this e-mail from your computer, and destroy any copies in any form immediately.
Receipt by anyone other than the named recipient(s) is not a waiver of any
attorney-client, work product, or other applicable privilege. This message and
all contents may be reviewed by authorized parties of the Catholic Health
System other than those named in the message header.
The contents of this message do not bind the Catholic Health System to any
contract, position, or course of action unless the sender is specifically
authorized to enter into contracts on behalf of the Catholic Health System. The
contents of this message do not necessarily constitute an official
representation of the Catholic Health System.
|
