If memory servers, a standby database is kept in a mount state, and is not
available for reporting.
Tapan Trivedi <tapan.trivedi_at_abbnm.com> wrote in message
news:37F8B71C.553AA77D_at_abbnm.com...
> Richard,
> HI. As far as I know you can go for either stand by database or the
> replication option both of which come with their own headaches. Since
> you need the backup database only for reporting you can use async
> replication . In any case both of these options also provide the option
> that you can have the stand by act as the primary if you lose the
> priamry database
> Tapan
>
> Richard Platt wrote:
> >
> > 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 Sat Oct 09 1999 - 09:16:05 CDT
