Author: Suad Musovich <suad AT CCU1.AUCKLAND.AC DOT NZ>
Date: Fri, 1 Jun 2001 00:58:38 +1200
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 eithe
Author: Robin Sharpe <Robin_Sharpe AT BERLEX DOT COM>
Date: Thu, 31 May 2001 09:08:54 -0400
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 inten
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 no
Author: David Longo <David.Longo AT HEALTH-FIRST DOT ORG>
Date: Thu, 31 May 2001 09:17:23 -0400
One question pops up to consider in the planning. Do the files they put in the staging area have a unique filename each day or will it be the same filename each day? David B. Longo System Administrat
Well, there is also the TSM API where, if you program in C, and your database system itself provides an API, you could potentially create your own client. It's not for everyone, but it's there. Rich
Author: James Thompson <mezron AT HOTMAIL DOT COM>
Date: Thu, 31 May 2001 07:12:56 -0700
I also vote for archives. Archives are designed to keep a set of related files together. You do not want any type of versioning to occur when doing a file level / os level backup of your database fil
Author: "Richard L. Rhodes" <rhodesr AT FIRSTENERGYCORP DOT COM>
Date: Thu, 31 May 2001 11:55:14 -0500
This is exactly how we backup our more than 200 Oracle databases. We have a script (actually, a rather large suite of scripts) that create the backup in a a staging area on the db server. The backup