Re: [ADSM-L] TSM multi libraries in a single stgpool

2011-07-06 14:06:51
Subject: Re: [ADSM-L] TSM multi libraries in a single stgpool
From: Bob Levad <blevad AT WINNEBAGOIND DOT COM>
Date: Wed, 6 Jul 2011 18:04:20 +0000
There is no reason a single library can't have multiple device classes.

If I thought I would ever need to run multiple libraries, I'd be tempted to 
create multiple device classes, one per tape storage pool.

Then if it ever became necessary to move a pool to another library, it would be 
a simple matter to update the device class to point to the new library and move 
the corresponding tapes.


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
Remco Post
Sent: Wednesday, July 06, 2011 12:26 PM
Subject: Re: [ADSM-L] TSM multi libraries in a single stgpool

On 6 jul 2011, at 14:09, Steven Langdale wrote:

>> Can TSM support having two libraries in a single stgpool?  Looking to add
>> another library but would to make sure it is used in tandem with our current
>> library and not just sit there.
>> Thank you,
>> Vince
> Vince
> No you can't, it's one devclass in a stgpool and a devclass can only point
> to one library.
> Theres obviously nothing stopping you creating a new devclass and stgpool
> for this new library and pointing some servers at it to spread the workload.

or, use one library for the primary pools and another for the copy pools, or 
define one stgpool in the new library as the next for an existing pool in the 
existing lib.....

> Steven

Met vriendelijke groeten/Kind Regards,

Remco Post AT plcs DOT nl
+31 6 248 21 622
This electronic transmission and any documents accompanying this electronic 
transmission contain confidential information belonging to the sender. This 
information may be legally privileged. The information is intended only for the 
use of the individual or entity named above. If you are not the intended 
recipient, you are hereby notified that any disclosure, copying, distribution, 
or the taking of any action in reliance on or regarding the contents of this 
electronically transmitted information is strictly prohibited.

<Prev in Thread] Current Thread [Next in Thread>