The backupset has ONE entry in the DB, in volumehistory. The backups of
each file are not recorded in the DB, and don't participate in versioning.
So it's like having a volume dump on the shelf, except that the backupset is
made from data that is already in server storage, without participation of
the client and without sending the data across the network again.
-----Original Message-----
From: Francisco Reyes [mailto:[EMAIL PROTECTED]]
Sent: Friday, July 27, 2001 10:01 AM
To: [EMAIL PROTECTED]
Subject: Re: Backup Scheduling
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.