RE: backup up archivelogs

Paula,

If you are really worried about this, then take the simplest approach possible.

If you know that you normally generate 10 archivelog files a day, then simply back them up to tape, say, every 3 hours. Or 2 hours. Pick a time frame that you are comfortable with.

At one place I worked at, we ran a job every 15 minutes that looked at the archivelog directory. If, say, 5 files were there, we would back them up and remove them.

With either approach, you can at least tell management that you are doing *something* about it.

Tom

-----Original Message-----
From: oracle-l-bounce_at_freelists.org
[mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Ron Rogers Sent: Tuesday, May 17, 2005 9:42 AM
To: Paula_Stankus_at_doh.state.fl.us; oracle-l_at_freelists.org; onkarnath.tiwary_at_gmail.com; rgramolini_at_tax.state.vt.us Subject: RE: backup up archivelogs

Paula,
 That is a valid concern if you loose the archive log destination. How = =3D
about setting up another destination on a different server or nfs mounted =3D
point.=3D20
Ron

>>> <Paula_Stankus_at_doh.state.fl.us> 05/17/05 9:01 AM >>>
We have redo members mirrored on multiple file systems. We write the redos to an archive log. We backup the database in full along with archivelogs each night.

The problem is that if the entire box goes down or we loose the RAID for archives we would only be able to restore/recover to the previous night.

I am considering backing up archivelogs to tape immediately as they are filled up. =3D3D20

Anyone doing this and their thoughts on gotchas/caveats/best practices?

Thanks,
Paula

--
http://www.freelists.org/webpage/oracle-l

--
http://www.freelists.org/webpage/oracle-l
--
http://www.freelists.org/webpage/oracle-l