What exactly are you looking to control about the replication? There's no parameter to say "perform replication", because that happens automatically with HA cell pairs. There are the CellDuplicate* parameters that setup cells into being in HA & control failover, auto-switchback, etc. There are also the following parameters which control timeouts and intervals in the communication (#1 and #2 below are reserved for indicating primary / secondary nodes in an HA cell pair);
I also communicated the same to my customer ,
He was keen on asking that in a DR scenario if the primary cell is offline for 5 days , will it resync to secondary ,
If yes till what level
What is maximum number of days /message primary site will sync to secondary or vice versa ?
How and which parameters control the sync b/w the primary and secondry cells ?
Can we customize any paramters if yes which paramters are suitable for longer duration of DR and what is the bmc recommended value
Environment : one node of cell in PROD site and second node in DR
Can you share the configuration? I am curious for the DR scenario too
Hi charles, Can you explain the details for that 3 parameters for HA cells and how to implement them in both primary and standby cell, tsk #DestinationBufferReconnectInterval=#1=10,#2=10,=2m #DestinationBufferKeepWait=#1=1d,#2=1d,=1h #DestinationBufferKeepSent=#1=3,#2=3,=2m
The mentioned DestinationBuffer* parameters can control the duration for which they'd try to keep in sync. If one side is down for an extended period, it may be too long to reasonable expect them to get back into sync in a timely manner, and in those cases, a manual sync is suggested - https://docs.bmc.com/docs/display/tsim107/Cells+troubleshooting