We also have many systems running Oracle.  We were shutting down all of our
databases each night and running full backups.
Recently we installed SQL Backtrack, now each night we keep our Oracle
databases up and running, run hot backups using SQL Backtrack, then
use ADSM excluding all Oracle mount points except for the location where
all the SQL backtrack files are located.
Then every saturday I have a schedule that change the Client option file to
include all Oracle mount points.  When that backup
kicks in, we shut down the Oracle databases, and do full backups.

In the event of us loosing our database's, we would just lay down the full
backup, and use SQL Backtrack to get to our most current data.

Our databases are about 8 gig each, SQL backtrack takes about 45 minutes to
run, and our nightly ADSM backups run in about 20 minutes
compared to almost 1 hr and 15 minutes (before installing SQL Backtrack)





robin_sharpe AT HOTMAIL DOT COM on 11/25/98 03:30:25 PM

Please respond to ADSM-L AT VM.MARIST DOT EDU

To:   ADSM-L AT VM.MARIST DOT EDU
cc:    (bcc: Joe Schilling/BOMC/TIME_INC/US)
Subject:  Re: ADSM-L Digest - 23 Nov 1998 to 24 Nov 1998




Tina,
We have several Oracle instances, and also SAP R/3.  We do not use the
Oracle or SAP utilities for backup; instead we shutdown the databases
and do a weekly full.
I understand ADSM = "Incremental Forever" (In fact, I'm thinking of
getting a license plate that reads "INCR FRVR"  :))
However, since our databases get updated every day, a daily incremental
would back up the entire database.  Our solution is to exclude the
Oracle database files from the daily backup... in a recovery situation,
a PIT restore would be done, then we would apply the archived redo logs
to bring the database back up to date.
We have a possible work-around.... we will create a second node
definition in ADSM for each client with a database, and the weekly
backup will be done from this node.  Another possibility is to archive
the database files rather than backup.
I was wondering how others handle database backups...
Thanks,
Robin
___________________________________
Date:    Tue, 24 Nov 1998 13:31:31 -0500
From:    Hilton Tina <HiltonT AT TCE DOT COM>
Subject: Re: Exclude causes expire on HP-Unix clients!
This has always been the case for all ADSM clients.  You either want the
file backed up or you don't.  Without a lot of trickery, ADSM can't do
daily/weekly logic.  It's intended to be used for "incremental forever"
backup.  What are you trying to accomplish with having different daily
and
weekly backups?
Tina
______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com