Keith,
the difference is that you are using pre-defined volumes - which the doc
says will be used in alphabetical order - see the worked example at the
bottom of the technote (steps 1 - 8 ). The true round-robin across
directories only works when using scratch volumes (that are auto-created
Ian,
The Technote says, When predefining volumes, the Tivoli Storage Manager server
will use all of the volumes in one directory before using the volumes in
another directory.
Here is the example:
7) Sort list of empty volumes alphabetically: List appears as
c:\.BFS
Rick,
I am just getting started with FILE deviceclass storage pools, so take the
following with ample grains of salt. However, my experience contradicts
swg21497567. Or, I might misunderstand that Technote.
This is a TSM 6.2 RHEL5 server. The file deviceclass has fourteen 2 TB
filesystems on
If you have a dev class of type FILE with multiple directories, how does
TSM determine which dir to create a new volumes in?
I've checked everywhere I can think of and the most I can find is comments
that TSM is free to pick any dir to create a new scratch vol in. Assuming
lots of free space
@VM.MARIST.EDU
11/11/2011 03:00 PM
Please respond to
ADSM-L@VM.MARIST.EDU
To
ADSM-L
cc
Subject
[ADSM-L] Dev Class type FILE with multiple directories
If you have a dev class of type FILE with multiple directories, how does
TSM determine which dir to create a new volumes in?
I've checked everywhere I
@VM.MARIST.EDU] On Behalf Of
Richard Rhodes
Sent: Friday, November 11, 2011 3:00 PM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] Dev Class type FILE with multiple directories
If you have a dev class of type FILE with multiple directories, how does
TSM determine which dir to create a new volumes