You CAN delete an off-line storage pool volume; you will need to specify
'discard=yes' to do it (I do it all the time at D/R).
My approach, as a semi-paranoid admin, would be to start by marking all the
disk storage pools read-only. Then migrate them to the next pool. And then
update them to 'unavailable', disable client sessions (probably about the time
I made the pools read-only), and do the database backup.
Restore on the new system, and then delete the old disk pools from the new
system configuration. Build the new disk pools.
I missed the original post - is this a different tape technology, or just a new
tape library? If the technology is different, I'd take a shot at marking one
drive unavailable on the old TSM server and attach it to the new server -
define it as a manual library with one drive. Then do the export on the old
server to tape, check out the tape, and fire up the import on the new server.
Mount the tape(s) by hand. Gotta be faster than ethernet.
But it will require physical access to an old drive on the new system.
Hope this helps -
Tom Kauffman
NIBCO, Inc.
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Lee, Gary D.
Sent: Thursday, August 28, 2008 8:49 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Trouble doing tsm db restore
Howard Colse was correct. Did a db backup type=full, and restored from it ok.
Now to get around the next difficulty. Totally different hardware config.
My plan was to restore the db to the new server. However, the disk pools will
be completely different, and it looks like you can't delete a storage pool
volume that is off line.
One thought is to delete the disk pool from the old server, then do the db
backup.
Does anyone have a better way of moving 80 nodes and their data between servers
without doing the export / import thing?
Roughly 8 tB of data over a gigabit ethernet.
I would appreciate any solutions you may have.
Gary Lee
Senior System Programmer
Ball State University
phone: 765-285-1310
|
