-
Hi, DBA,
I need all your input.
Environment:
3 machines: 1 master site, 2 copies of master site read-only mode. one DB on each machine.
user only update on master site, all query done on the copies of master site.
Requirement:
1. all update transactions will be reflected on 2 "copy" sites instantly.
2. copy site does not need backup, but need to be able to rebuilt as needed
3. little network traffic
question:
I should use snapshot or multi-master replication?
I did some test:
if snapshot refresh interval set to be 5 sec, it create 3Gb arch log files on master site each day without any activity/transaction.
to rebuild snapshot site is much easer and faster than multi-master site.
so any suggestion?
thanks in advance
-
I never work with Multi-master, but I had work with Master and snapshot. And yes, the master site will create a lot of archive file due to the replication. And there is no way to shrink the creation of the archive log.
In my opinion, it's more simple to reconfigure a snapshot site than a multi-master environnement. So my advise was, keep going with the snapshot envirronement.
(this is my 2 cent suggestion)
Fugazi...
-
thanks, I agree snapshot is much much simpler than multi-master. but the size of arch log file plus "instance" update make my boss perfer to multi-master or:
in snapshot environment
create a trigger which can be fired to active the refreshment
either by # of transaction or as needed.
I see the possibility and complexity. e.g. what if regular time_based refresh job and this new "trigger" fired at same time ...
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|