The backup set IS exactly a snapshot. It makes a bundle of file copies and
does not track the separate files (the DB tracks them as parts of stgpools)
but tracks the entire bundle/backupset as a single object.
The backupset written to a media (tapes, CDs, etc.) can be used for "bare
metal/LAN-free" restore. So tracking of backupset gives you an idea when
you created that image. If it is recent enough you can restore the system
from media containing the backupset and later just restore newer files.
So this functions also as something similar to archive.





On Fri, 27 Jul 2001, Len Boyle wrote:

> In article <[EMAIL PROTECTED]>, Steve Harris
> <[EMAIL PROTECTED]> says:
> 2) If you need to keep a snap shot of data for a long time  without the
>    need to keep the data in the tsm data look at the backupset
>    function to snap a copy of the active fileset on a tape set that
>    can be removed from the tsm server.


I just read the description for the backupset and I don't see how it can
be used as a snap shot. I didn't really understand from reading that what
is that the backupset is or does. In particular I don't see how it would
do what Len wrote above .. "keep a snap shot of data for a long time
without the need to keep the data in the tsm data". Does that mean that
the backupset is not tracked by the DB? It seems TSM remembers or tracks
the existance of the backupset since there is a parameter for that, but
what does that keep track of?

Thanks.

Reply via email to