> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]
> Sent: Freitag, 14. Februar 2003 12:04
> To: Brunzema, Martin
> Cc: [EMAIL PROTECTED];
> [EMAIL PROTECTED]
> Subject: Antwort: RE: Backup and Recovery
>
>
> Hi Martin,
> could you please explain it once again, using more single steps?
> I tried several ways with no working result. I talked to
> others who tried
> your solution,
> unfortunately nobody made it work. :-(
Hi,
this is no real "standby"-sloution, but a cheap version
of it using the log-backup to keep the standy-db up to
date.
Here are the steps to perform it (i also didn't implement
this solution, but it should work)
master-db: start database
master-db: create a complete databackup
standby-db: install the standby-db from the databackup
now you have two identical databases. If you change data
on the master-db, you want to do this changes also auto-
matically on the standby-db. You can perform this by
using the logsaves of the master-db, which contains all
the change-operations. You only have to do periodically
a save-log on the master-db and to restore them into
the standby-db.
For a delay of one hour, you should establish save/restore
log every hour as follows:
master-db: save-log into file.xxx (xxx is the automatically
appended number)
copy file.xxx to the standby-db
standby-db: restore log from file.xxx-1
(do not restore file.xxx, but the predecessor in
order to maintain your delay of one hour)
In case of a crash of the master-db you can either
- restore the rest of the logsave
- additionally do a save log on the master in cold-mode
and restore it also
- or just doing a restart by using recover_ignore
The delay will not be exactly one hour, but in the intervall
1 to 2 hours. You can adjust it by changing interval of
your logsave.
HTH, Martin
_______________________________________________
sapdb.general mailing list
[EMAIL PROTECTED]
http://listserv.sap.com/mailman/listinfo/sapdb.general
