Re: Strategy question for 24X7, how to do cold backups?

Galen,

You don't need to keep all of the archived redo logs from day one. Database changes are flushed from memory to disk regularly and you only need to keep archived logs containing changes that that have not yet been applied to the data files on your latest backup.

If you want to have a secondary backup, have you considered running a regular export dump? This might not be practical though if your database is very large.

Standby database is very useful but I believe the standby instance can't normally be used so the standby machine is idle during normal operation. Have you considered other options such as replication or parallel server to maintain a duplicate database running on a separate server? These are more complicated than standby database but they allow all of your server resources to be used at the same time and your database is still available if one of the servers fails.

Regards,

Richard

"Galen Boyer" <galenboyer_at_hotpop.com> wrote in message news:usndbt1n1.fsf_at_verizon.net...
> All web clients want a 24X7 solution. Immediately, hot backups
> are needed. But, then, for a true 24X7, one must keep a copy of
> all of the redo logs from day one and a recovery would take quite
> awhile (Maybe I'm wrong here and the question is moot). On
> google, I am reading that one strategy is to configure a standby
> database where the current database's redo logs are applied
> against the standby. Then, if done correctly, a cold backup is
> never needed? Even if it is, the standby can be used to produce
> the cold backup?
>
> Am I on the correct path to the #1 solution for this and are
> there other options as well for actually achieving 24X7?
>
> Thanks.
> --
> Galen Boyer
> Everyone in town, now, they probably all agree,
> I'm _lying_ in the bed I made.
Received on Tue Sep 25 2001 - 19:00:23 CDT