>> On Thu, 13 Aug 2009 11:51:32 -0400, Shawn Drew
>> said:
> We started using Virtual Volumes earlier this year for some new
> branch locations with no local, long-term storage. As it works,
> multiple virtual volumes will get stacked into one "real" sequential
> volume.
> The problem is tha
-Shawn Drew wrote: -
>TSM 5.5.3
>
>For some reason, it seems to ignore the maxsize setting. I've set
>the devclass to 50G, but the volumes seem to randomly choose when
>they are full. Collocation is disabled. Here is an excerpt from
>a q vol. Strange.
>
>[Excerpt deleted]
If I remember
awn Drew
Internet
nbstr...@lmus.leggmason.com
Sent by: ADSM-L@VM.MARIST.EDU
08/13/2009 12:55 PM
Please respond to
ADSM-L@VM.MARIST.EDU
To
ADSM-L
cc
Subject
Re: [ADSM-L] Virtual Volume assistance
Shawn,
In your virtual volume devclass definition you might try to set a
maxsize equal to
genius, power and magic.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
Shawn Drew
Sent: Thursday, August 13, 2009 11:52 AM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] Virtual Volume assistance
We started using Virtual Volumes earlier this year
We started using Virtual Volumes earlier this year for some new branch
locations with no local, long-term storage.
As it works, multiple virtual volumes will get stacked into one "real"
sequential volume.
The problem is that periodically, a reclamation process will require two
volumes that happen
