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

> 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
Not a big fan of hot backups... so, no comment here.

> 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?
>

As for a standby database, if the luxury of having duplicate (or more) resources exists, I feel it is an elegant solution for high availablity... and, there is no third-party software involved! Obviously, there are the additional administrative tasks one has to perform - I feel they are worth it.

To cold backup, take the standby database out of managed recovery mode, shut it down, back it up, startup and perform manual recovery (using any archive logs created by the primary database while the standby was down), and place the standby database in managed recovery mode.

Alternatively, standby database can be backed up while it is placed in read-only mode, thus avoiding the need to perform manual recovery.

Also, while all this is going on, might as well set up hot backups of the primary database... for peace of mind, I suppose. -Lute. Received on Tue Sep 25 2001 - 14:45:13 CDT