Re: 24x7 with full backup

There are several ways to do this ranging from cheap to expensive and relatively easy to really hard. Which one works best depends on your exact requirements.

The cheapest way is probably to do a cold backup, copy the files to a reasonably close backup machine, bring that instance up to a mounted state. Then start up the primary copy and routinely copy over the log files and apply them to the backup database. I think the command is something like 'alter database backup database ...'. This gives you a 'warm' backup that can be restarted as necessary. The process is just to copy over the latest active log file, do a point in time recovery and the start the backup database. There are also some ancillary issues that need to be dealt with, like swapping the IP numbers so clients can find the new database server, etc. I've been out of the game for a while so the specifics are a bit hazy, but it is definitely doable.

You could also look at running parallel server in a fall-over configuration so that a single machine failure is handled transparently. Much more expensive to build and I would expect harder to maintain, tune, etc. but worth it if your downtime requirements are tight.

--rick

 ga wrote in message <371B2E50.9E08A90D_at_alerts.co.il>...
>My company just made a decision to go 24x7 with oracle 8.0.5.
>
>I am stuck with finding out if there is an easy way (i know that within
>oracle nothing is every easy) to get an oracle server up with 24 hours -
>7 days a week access. And if the server dies, be back up - with minimum
>data loss within 1/2 hour.
>
>I have heard about oracle 8 with enterprise server and replication.
>
>Does that sound like the right path?
>
>I have no experiance with replication and do not know what its
>performance is or how complicated it is to:
> set up
> manage
> cut over to backup if the primary is down
> go back to primary when it is up to date
>
>I know this is a long question - sorry.
>
>thanks ahead for any info
>GA
Received on Tue May 04 1999 - 12:06:17 CDT