|
midrange.com
My first guess was like yours Rob, but I just talked to support and they
gave me some more info. Because the cluster replication is 'event driven',
the initial replication to the cluster mates is a push type replication
that is driven by the initial DB change. Once that even occurs, it
wouldn't necessarily be driven to occur again to another replica that shows
up there later (like in our guess).
Lotus support said that all that is necessary to cause the replicas to get
the offline server back in synch is a simple replicate command, THEN the
DBs will hash it out.
So:
Users to backup server
Main server shutdown
Test server up
DB activity on backup server
DB activity replicates to test server
Tests done
Test server shutdown
Main server back up
Main server still missing DB activity
Replicate command issued for server (ex. REPLICATE MAIN)
Replicas bring Main server DBs to current state
Users back to Main server
I wanted to make sure I posted what I found out... so there it is!
For this upgrade, I think my testing is going to be more complex than the
actual migration...
rob@xxxxxxxxx
Sent by:
domino400-bounces To
+chadb=wheeling-n Lotus Domino on the iSeries / AS400
isshin.com@midran <domino400@xxxxxxxxxxxx>
ge.com cc
Subject
07/26/2006 01:49 Re: New Machine Domino Testing
PM (involving cluster)
Please respond to
Lotus Domino on
the iSeries /
AS400
<domino400@midran
ge.com>
I believe so. Perform a simple test
Create a new database
Replicate this database on to a different server.
Backup the database on the new server.
Make some changes to the database on the primary.
Replicate it over to the backup server
DBCACHE FLUSH on the backup server
delete the database on the backup server
restore from backup
replicate again and see if your changes appear. I bet they will.
I am trying to guess how they do replication. I am betting there isn't
some huge server file that keeps track of which field in which file has
been replicated.
Nor do I wish to believe that there is a id in the "primary" field that
says "this field has been replicated to servers A,C,F"
I am taking a big WAG that there is a replica hash much like the table
replica id. And if the replica hash isn't identical then somehow Domino
quickly finds the changes.
Rob Berendt
--
Group Dekko Services, LLC
Dept 01.073
PO Box 2000
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com
ChadB@xxxxxxxxxxxxxxxxxxxx
Sent by: domino400-bounces+rob=dekko.com@xxxxxxxxxxxx
07/26/2006 10:18 AM
Please respond to
Lotus Domino on the iSeries / AS400 <domino400@xxxxxxxxxxxx>
To
Lotus Domino on the iSeries / AS400 <domino400@xxxxxxxxxxxx>
cc
Subject
New Machine Domino Testing (involving cluster)
Next month we will be installing and bringing live a new model 520+ that
runs our 'main' Domino server and Websphere setup. We are clustered with
another iSeries based Domino server that we consider the 'backup' Domino
server (we keep users off it normally with SERVER_RESTRICTED=2 unless we
specifically want users on this server instead). We can easily control
which server our apps and email are currently flowing to via DNS and
firewall changes.
Since we've gone to the clustered setup, it's been easy to test Domino
releases and such, because we can switch the users over to the 'backup'
Domino server and test things on the other server while it's not actively
serving apps or receiving live email. This new box brings a slightly
different challenge to my testing plans... I want to try and test as much
as possible on the new box before doing a final save/restore migration,
but
don't want to get in any trouble with cluster replication, etc.
With that long-winded intro having been said, my main question is this:
If we are running on the backup server and have our current main server
shut down, and then plug the new server into the network for testing the
cluster will replicate items from the currently live backup server into
the
new test server's databases (it will be a restore of the main server and
identical in IP address, etc.). Once we are finished testing, we will
disconnect the new test server and then bring up the current main server
again. Will the transactions that occurred on the backup server while the
main server was down all replicate back to the main server even if some of
them also replicated to the test server when it was connected?
Any thoughts are appreciated...
_______________________________________________
This is the Lotus Domino on the iSeries / AS400 (Domino400) mailing list
To post a message email: Domino400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/domino400
or email: Domino400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/domino400.
_______________________________________________
This is the Lotus Domino on the iSeries / AS400 (Domino400) mailing list
To post a message email: Domino400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/domino400
or email: Domino400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/domino400.
_____________________________________________________________________________
Scanned by IBM Email Security Management Services powered by MessageLabs.
For more information please visit http://www.ers.ibm.com
_____________________________________________________________________________
ForwardSourceID:NT0004D452
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
