It looks like adding an ID vault and vault replica on 2 servers has broken the scheduled replication between them.
One of the servers has a connection document to perform a push pull replication every 30 minutes. This worked perfectly until I added an ID vault to the servers. Now it looks like the ID vault is replicated between the servers every 10 minutes (and sometimes more often). This is all well and good as I understand the replicas need to be as up to date as possible.
However the problem is everytime the ID vault replicates the next replication time (from show schedule) is pushed 30 minutes on so never gets the chance to run.
Is any one else seeing this or have I missed something?
Subject: Seems So
Thank you for reporting this. I investigated this in the code and found that the vault replica creation code was correctly performing a replication with another server, but incorrectly recorded this as a replication in the replication schedule database.
I have written an SPR to get this corrected.
From what I can tell, this problem will not occur often, since the IDVault code only performs a replication when a new replica is created.
Thanks again
Pete Mierswa - IBM
Subject: ID Vault and replication
Thanks Pete,
From my experience the ID vault is replicating at least every 10 minutes so my 2 servers have never carried out a scheduled replication since I set up the ID vault replica.
I have worked around the problem for now by adding a program document to run replica every 30 minutes so it is not causing major problems.
Thanks again,
Colin