If you are in a pure TSM environment, meaning the VTL is exclusively
used by TSM, how useful is truncating scratch tapes and returning that
space to the VTL's pool of free space? Unless you use co-location all
volumes are going to be quickly written to their define maximum native
capacity. The
John Schneider said:
I can't speak for everybody's product out there, but the EMC CDL (EDL)
releases the used pages from the virtual volume as soon as you begin to
overwrite the virtual volume from the beginning. One thing that does
this is a Label Libvolume.
This is the way they all work. And
On Mon, 11 Jun 2007 23:50:20 +0100, Neil Schofield [EMAIL PROTECTED] said:
- We still need to take into account the overhead of the reclaimable space
on a virtual tape. This can be managed by varying the reclamation
thresholds, but not eliminated.
With a pure disk VTL, you can keep
ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU wrote on 06/12/2007
09:30:58 AM:
On Mon, 11 Jun 2007 23:50:20 +0100, Neil Schofield
[EMAIL PROTECTED] said:
- Since the conversion of a pending delete volume to a scratch tape
takes
place purely in the TSM database, a virtual scratch tape will
I can't speak for everybody's product out there, but the EMC CDL (EDL)
releases the used pages from the virtual volume as soon as you begin to
overwrite the virtual volume from the beginning. One thing that does
this is a Label Libvolume.
It would be a simple script to look at all scratch tapes
VTL and over subscription as I understand it.
Definition: When (tape volume size) X (number of defined volumes)
native capacity of VTL you have over subscribed. If you try to fill-up
all your defined volumes to their defined native capacity you will fail
as you will run out of space on your
Hi there
We too are in the throes of a debate about virtual vs. physical tape
libraries.
On the VTL side, much is made of the ability to over-provision the disk
capacity - eg a 100Gb virtual tape will only occupy as much space on disk
as has been written to it. As a result, so the theory goes,
