Suad,

You can just set the VEREXIST and VERDELETED to "NOLIMIT".  This removes
version count from the algorithm, and retention is solely controlled by
date.  This is what Tivoli recommends if you intend to do Point In Time
Restores.  As long as you can control how many backups get done, it
shouldn't be an issue...

Robin Sharpe
Berlex Labs



                    Suad Musovich
                    <[email protected]
                    AND.AC.NZ>       To:    ADSM-L AT VM.MARIST DOT EDU
                                     cc:    (bcc: Robin Sharpe/WA/USR/SHG)
                    05/31/01 08:58   Subject:
                    AM                      backing up DBs from filesystems
                    Please respond
                    to "ADSM: Dist
                    Stor Manager"







We are about to start backing up our enterprise databases.
They are comprised of about 15 Oracle instances ranging from 7GB to 25GB.
About a third are being backed up nightly and the others are either 1 or 2
times
weekly.

On the server side, we will set up a seperate stgpool hierarchy as they
there
will be expectations for QOS etc. (I will seperate them out onto a 2nd
server
later this year)

There are no TDPs available (Dynix) so we have to use the command line
client
to backup. The DBAs run the database in backup mode and cpio the files to
a staging area, then the TSM client will scoop them up.

They want a 30day retention period with one backup a month kept for a year
(acheived
by a management class flag on dsmc)

Question:
Should we run incrementals or archive the files considering we have a date,
as
opposed to frequency, retention requirement?

Suad
--
=========================================================================