RE: Off Topic: SQL-Backtrack

Don't know if your question was to everyone or not but I'll add my 2 cents. We always delete the archive logs after backing them up. We also changed our batch SQL Backtrack scripts to first backup the archivelogs in one step, then do the hot backup, then backup the archive logs again. We were having trouble with SQL Backtrack for a while using Netbackup. The archivelogs would get backed up, deleted, and then SQL Backtrack would start doing the hot backup. Netbackup would abend for various reasons and scratch the tape that had the archivelogs on it. The three part backup prevents this. A hot backup has always worked for us.

-----Original Message-----
From: Suzy Vordos [mailto:lvordos_at_uswest.com] Sent: Wednesday, July 05, 2000 4:06 PM
To: Multiple recipients of list ORACLE-L Subject: Off Topic: SQL-Backtrack

Just started using SQL-Backtrack, and have a few questions....

Is there any benefit to having SQL-Backtrack keep (rename) the archive logs after backup instead of deleting them?

After switching to archivelog mode, is a full online backup sufficient, or for safety should I do a full cold backup?

For some databases, there isn't a regular window that can be used for cold backups, so only full on-line daily backups will be done. Any problem with this strategy?

Thanks much,
Suzy

-- 
Author: Suzy Vordos
  INET: lvordos_at_uswest.com

Fat City Network Services    -- (858) 538-5051  FAX: (858) 538-5051
San Diego, California        -- Public Internet access / Mailing Lists
--------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from).  You may
also send the HELP command for other information (like subscribing).