This website uses cookies to ensure you get the best experience.
Learn more.
Replication lag grows faster than it can be reduced during business hours. What should be evaluated?
Published
- Treat successful inventory discovery as proof replication is current.
- Delete recent source changes to improve the graph.
- Change rate, available transfer throughput, replication configuration, and the cutover outage requirement.
- Assume lag automatically becomes zero when DNS changes.
Comments — 0
Sign in to comment