Re: Creating a backup database

Hi,
The best solution for backup would be STANDBY database. But, IMHO you have to had O7.3.4 both for this, because stand by mode needs homogeneous environment.
Also, you can't use standby database as report machine.

So. You need Replication. You can use Replication Option, if you need support of distribued transactions. If no - use simple customized replication
on snapshots with snapshot logs.

Simple example:

MasterDB:

create snapshot log on TableA;

ReportDB:

create snapshot TableA
refresh fast next sysdate+1
as select * from TableA_at_MasterDB;

This should work more smooth and faster.

For users, roles, procedures replication use full export/import without table data ROWS=N.

Also you can try to write data into regular files and then to load this via direct path.

Mark Malakanov
DBA
Sapience, Toronto

Richard Platt <rick.platt_at_btinternet.com> wrote in message news:7t7f5e$bck$1_at_plutonium.btinternet.com...
> Hi
>
> I have 2 databases on seperate machines. A live one, and a backup one.
> They are both running 7.3 (one is 7.3.2 and the other 7.3.4). How can I
> ensure that the backup database is an exact backup of the live one.
>
> I wrote some scripts which dropped all the users (except) sys in the
backup
> database, then loaded a full export from the live machine. The major
> problem is the time taken. The import takes a good 14 hours at the
moment,
> never mind the export as well 2-3hrs.
>
> The backup machine is used for reporting, and hence I need to complete the
> job of an evening. I also want it to be self maintaining, i.e users
created
> on the live machine are duplicated, as are roles.
>
> I had thought of snapshots but there are load of users and tables, as well
> as server side code.
>
> Any thoughts ?
>
> --
> Regards Richard Platt
> rick.platt_at_btinternet.com
>
>
Received on Sun Oct 03 1999 - 09:00:20 CDT