Not sure how you would mirror disks located in two separate datacenters :-)
We need a share nothing type of solution like what is shown in those diagrams I showed in the MS SQL examples.
Here is the previous post on what I'm looking for (I posted it under the wrong subject, doh!):
If either one of the systems go down, they both go down. I'm not looking for a high availability solution. I'm looking for:
1. User issues INSERT statement on SERVER A, it gets replicated to SERVER B.
2. If user issues INSERT on SERVER B, it gets replicated to SERVER A.
1. An INSERT is not committed to either system until it has replicated to the remote system.
I'd also settle for a topology where if rule #1 can't be obtained out of the box then whichever system was the first one to INSERT wins, and the last one to UPDATE wins.
As I understanding it journaling does most of this, but I have found no documentation that states how to do bi-directional and also shows you the topology diagrams along with the control panels/GUI tools that aide in conflict resolution, as well as how to define conflict resolution rules within IBM i DB2.
Again, documentation seems scarce on this subject. Very plentiful in LUW and other DB platforms. Just point me to the redbook please :-)
From: Nathan Andelin [mailto:nandelin@xxxxxxxxx]
Sent: Monday, March 11, 2013 3:46 PM
To: Midrange Systems Technical Discussion
Subject: Re: Bi-directional transactional replication on IBM i
I'm looking for something akin to this type of replication in SQL 2012
The web page you referenced sites a couple use cases:
1. Improved read performance, because reads are spread out over two servers.
2. Higher availability if maintenance is required or in case of failure at one node.
For improved read performance we chose to go with mirrored disks under IBM i. Since the files exist on 2 disks - more jobs, processors, etc. have simultaneous access. Wouldn't mirrored disk be easier to manage than mirrored DB servers?
Mirrored disks also support higher availability. If one disk fails, the other picks up the load.
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l