with a vtl, does we still need a diskpool?
we have 279 clients nodes set up on tsm. backups start at 6pm and are suppsoed to end at 6am.
Currently with the diskpool that we have, 5TB in size, everything gets dumped to the random access disk diskpool "usually" within the 12 hours, well not really, then migrated to a physical tape library.
if we bring in a vtl, management wants to get that 5tb diskpool back for other projects or systms
I have seen 50 sessions running on tsm at the max (i think i have max sessions set to 75 on the tsm server)... does this mean with the diskpool gone, the VTL will need to have 50 virtual tape drives created, or 75 to correspond with the max sessions (am i right in saying each backup session for each node requires its own tapedrive??)
We do not have any lanfree agents anywhere, everything moves over the lan to the TSM server, then out the fiber..
So, do we need to keep our diskpool? or will the VTL and TSM work it out?
we have 279 clients nodes set up on tsm. backups start at 6pm and are suppsoed to end at 6am.
Currently with the diskpool that we have, 5TB in size, everything gets dumped to the random access disk diskpool "usually" within the 12 hours, well not really, then migrated to a physical tape library.
if we bring in a vtl, management wants to get that 5tb diskpool back for other projects or systms
I have seen 50 sessions running on tsm at the max (i think i have max sessions set to 75 on the tsm server)... does this mean with the diskpool gone, the VTL will need to have 50 virtual tape drives created, or 75 to correspond with the max sessions (am i right in saying each backup session for each node requires its own tapedrive??)
We do not have any lanfree agents anywhere, everything moves over the lan to the TSM server, then out the fiber..
So, do we need to keep our diskpool? or will the VTL and TSM work it out?