One idea that you can try is to use the "GENERATE BACKUPSET" command and
store this media for as long as you want.
That way you can tell him that you have a saved copy of his data then
move him to the new server and it should run a full backup of all his
data anyway onto the new media. My two cents! :)
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Martha McConaghy
Sent: Tuesday, July 08, 2008 11:09 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] Tricky conversion problem
We are moving to a new TSM server on a Pseries box with an IBM 3592 tape
system from a very old mainframe based TSM server. We had not planned
on moving any of the old data over to the new server as there was no
requirement for it. However, we run into a single user who wants to
have all of his previous backups moved to the new server, even though
most are no longer usable (we are talking about old OS2 systems,
etc....every PC he has ever used in the last 20 years). Since this user
is our 2nd line manager, we have no choice to try and figure something
out.
The main problem is that the two servers are not compatible. The old
server can only talk to 3590 tape drives, whose tapes are not usable in
the new 3592s. So, I can't just export the data to tape and then import
into the new server. (Ah if only life were that easy!).
On a hunch, I've tried creating a server connection between old and new
TSM server. Then, I exported a filespace to a virtual volume
(devclass=server) on the new server. It sits on a 3592 tape right now.
However, the new server will not allow me to import this tape, as it
belongs to a pool and it thinks it is in use.
Is there any way to make this work? I'm at a loss for ideas at this
point.
I could create a virtual volume on disk and move the old filespaces to
it, but then I'll have to keep the old server running "forever" or at
least until it will run no longer.
Anyone have any ideas?
Martha McConaghy
Strategic Planner/Project Manager
Marist College IT
|
