DO IT WITH AN ARCHIVE ! ! !
A big reason is to keep "sets" of backups/archives complete...
If you do things with backups (versions) say something goes wrong half way
through your processing...
you now have not one but two incomplete sets of the data base
one is the set that only got half processed
the other is the set that had half its data rolled off because of the bad
backup
Dwight
-----Original Message-----
From: Suad Musovich [mailto:[EMAIL PROTECTED]]
Sent: Thursday, May 31, 2001 7:59 AM
To: [EMAIL PROTECTED]
Subject: backing up DBs from filesystems
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
--
