A backup agent is not in sync with a running (and live) main agent.
How can we force a sync so the backup is OK again?
The midnight sync does not solve it. And using the System Center > Tools > Sync > "this dms" does not seem to do anything (no info events are generated)
Which components of the DMA aren't in sync? Is it the DB or something else within the DMA (elements, views, protocols)? What DM version is it?
Hi Mieke,
You will need to use SLNetClientTest tool and do “Forcing file synchronization between DMAs” with the selected flag “Fix inconsistency problems”. You can find the details in the DataMiner help: Reference -> Tools -> SLNetClientTest tool -> SLNetClientTest tool advanced procedures: Forcing file synchronization between DMAs.
Thanks Alexander.
I could use the force sync dma, but this not sync the missing Elements + Protocols.
I found that we can set all files from a folder as changed via the same tool, but how can I make sure that all the sub folders are also “forced” to sync?
Hi Mieke,
When you say the backup agent is not in sync, does this mean that when you perform a 'nodetool status' on the offline agent the effective ownership of that node is less then 100% or what exactly makes you say the agents are not in sync i.e. are files not in sync or is the database not in sync?
If the database would be out of sync, performing a 'nodetool repair' should make sure all data gets synced again between the two nodes.
It can also make sense to do the compaction after the repair process finished. Run the ‘nodetool compact -s’ on both agents to start the compaction manually (in case if the database is more than 10 GB compact the tables separately)
The element and protocol files are missing.
When a switch is done none of the elements are shown.
When we check the Status page via system center on the running main the failover is indicated OK.