Oracle redo logs

Only if you want to ever recover anything.

You should also be backing up the database every day as well.

---
W. Curtis Preston
Author of O'Reilly's Backup & Recovery and Using SANs and NAS
VP Data Protection
GlassHouse Technologies

-----Original Message-----
From:
] On Behalf Of

Sent: Tuesday, December 19, 2006 5:55 PM
To:
Subject: [C.A.S.] Oracle redo logs

Hi.. I recently ran into a company that archives (daily) their Oracle
redo logs... each log is around 100MB... they have heavy transactions
and run 3 rotational logs. So thats about 300MB per day.

My question is, do they need to do this? Do they need to archive onto
secondary every day's redo log files?

I am not a DBA, so I cannot advise them on this topic, but trying to
get a feel for standard practices here

Jon.

_______________________________________________
Subscribe or Unsubscribe to this mailing list he
http://backupcentral.com/mailman/lis...e_backupcentra
l.com

Curtis Preston wrote:
Only if you want to ever recover anything.

You should also be backing up the database every day as well.

---
W. Curtis Preston
Author of O'Reilly's Backup & Recovery and Using SANs and NAS
VP Data Protection
GlassHouse Technologies

-----Original Message-----
From:
] On Behalf Of

Sent: Tuesday, December 19, 2006 5:55 PM
To:
Subject: [C.A.S.] Oracle redo logs

Hi.. I recently ran into a company that archives (daily) their Oracle
redo logs... each log is around 100MB... they have heavy transactions
and run 3 rotational logs. So thats about 300MB per day.

My question is, do they need to do this? Do they need to archive onto
secondary every day's redo log files?

I am not a DBA, so I cannot advise them on this topic, but trying to
get a feel for standard practices here

Jon.

_______________________________________________
Subscribe or Unsubscribe to this mailing list he
http://backupcentral.com/mailman/lis...e_backupcentra
l.com

This is adding 300MB daily to their storage requirements... isnt there
any way to curb this?

Jon

wrote:

....

This is adding 300MB daily to their storage requirements... isnt there
any way to curb this?

Probably no way that wouldn't cost far more than they're paying for the
required storage (well under $1 per day if it's mirrored, unless they're
using high-end enterprise-level storage for backup).

- bill

wrote:
This is adding 300MB daily to their storage requirements... isnt there
any way to curb this?


While this needs to be carefully coordinated with the DB admins, the
usual (easy) approach is to have a scheduled hard shutdown and backup
of the database at some regular interval (weekly, monthly), and then
rotate through several generations of complete database backup plus an
interval's worth of logs. Then you eventually throw away old logs.

The number of intervals has to do with your recovery requirements, and,
perhaps, with data retention requirements.

This, of course, does add a regular outage to your application.

More complicated is doing a snapshot backup of the live database.
Oracle certainly can do that, although I think you may need some
optional components.

Although I agree with Bill, the volumes you're talking about are
probably cheaper to just ignore.

usual (easy) approach is to have a scheduled hard shutdown and backup
of the database at some regular interval (weekly, monthly),

Why shutdown? MSSQLServer and Oracle can do hot database backups.

More complicated is doing a snapshot backup of the live database.
Oracle certainly can do that

All database backups in MSSQLServer are such, since version 4.2 of early 90ies.
I think Oracle can do this too.

--
Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation

http://www.storagecraft.com