Simple,Clear and Superb explanation.
Thanks Arup.
-Original Message-
Nanda
Sent: Wednesday, November 19, 2003 1:10 AM
To: Multiple recipients of list ORACLE-L
VirVit,
You haven't specified Oracle version and your tolerance for data loss. If
you can afford to lose the data in the most
Verification was easy. We just powered down the primary machine, changed the
db name in the external table, drop the replication on the backup server and
restart the application. Everything worked fine. After 2-3 days, over the
weekend, we rebuilt the replication again.
Yechiel Adar
Mehish
-
We are doing exactly that. We use multi master synchronous replication. In
case the regular server dies, we drop replication from the backup machine.
Change one parameter in the application ini file (what db name to use in
connections), start the application again. About 5 minutes turn around
Yechiel - So how do you verify your backup environment? My gut feeling is
that simpler systems are less prone to catastrophe, and multimaster
replication definitely adds a lot of pieces compared to conventional
backups.
Dennis Williams
DBA
Lifetouch, Inc.
[EMAIL PROTECTED]
-Original
VirVit,
You haven't specified Oracle version and your tolerance for data loss. If
you can afford to lose the data in the most current redo log file, then I
would suggest 9i Data Guard in maximum performance mode (or Standby in 8i)
solution over the MM replication. The DG solution does not affect
