ADSM-L

Re: Server partitioning using TSM library sharing

2002-07-23 10:11:37
Subject: Re: Server partitioning using TSM library sharing
From: "William F. Colwell" <bcolwell AT DRAPER DOT COM>
Date: Tue, 23 Jul 2002 10:09:44 -0400
Scott, I haven't done this but I have thought about it before.
I suggest some additional steps for safety.

1. empty out the diskpool and delete the volumes.  Make sure
the copypool is a complete image.  Than take the dbbackup and restore
to server b.  Add  1/2 of the disk volumes to the diskpool in a, the other half
to the diskpool in b.
2. Assume the single server had a tape pool called POOL.  Mark it
read only in both servers and create new tapepools - poola & poolb.
Update POOL in both servers to set reusedelay to 9999.
3. Now do the cross deletes.  Then reclaim POOL to poola in server a
and to poolb in server b.
4. When POOL is empty in both servers, delete the volumes from server a
in a way that returns them to scratch, and from server b in a way that doesn't.

You will need to invest in some extra media to do this, but it will be the
safest way.

If you go ahead, let us know how it works out.

Good luck!

Bill

At 04:26 PM 7/19/2002, you wrote:
>Hello fellow TSMers,
>
>We have a fairly large TSM server that we are planning to partition into 2
>servers. In other words, add a second server and split the client nodes
>across the two.
>
>The hardware environment is two AIX TSM servers, both fibre attached to a
>10 drive 3494 ATL.
>
>What I am proposing to do (and looking for input) is as follows:
>
>1) Restore a copy of TSM server-A's database to the new TSM server-B
>2) Reconfigure the library and drive configuration on TSM server-B to be a
>library client to the shared library manager server-A.
>3) Identify the nodes that are to be associated with each server.
>4) Identify the volumes associated with the nodes for each server (Storage
>pools are currently fully collocated by node).
>5) Run update libvol to change the owner on the appropriate tapes to be
>owned by server-B.
>6) Delete the filespace and node definitions for the nodes NOT associated
>with each server.
>7) Reconfigure half the nodes to point to the new server-B.
>8) Pat myself on the back and take the rest of the day off :-)
>
>It seems too simple....  Has anyone done this before? (hard to type with my
>fingers crossed)
>
>The big question of course is: what happens to volume ABC123 on server-A
>when the filespaces are deleted and the volume empties, gets deleted from
>the storage pool, and returned to scratch? Server-B still thinks there is
>data on that tape and this proposed solution would only work if he was
>allowed to request a mount and read that volume.
>
>Any and all feedback is appreciated!
>
>Scott
>Scott McCambly
>AIX/NetView/ADSM Specialist - Unopsys Inc.  Ottawa, Ontario, Canada
>(613)799-9269

----------
Bill Colwell
Bill Colwell
C. S. Draper Lab
Cambridge Ma.