- Newest
- Most votes
- Most comments
This issue with MGN replication becoming stalled and snapshots being out of date could be caused by a number of factors. Some possible causes include network connectivity issues between the source and destination environments, insufficient resources on the destination server, or problems with the MGN agent on the source server.
To troubleshoot this issue, you may want to start by checking the logs on the MGN agent on the source server to see if there are any error messages or warnings that could provide insight into the problem. You can also check the resource utilization on the destination server to ensure that it has enough CPU, memory, and storage to handle the replication workload.
Another step could be to check the network connectivity between the source and destination environments, to ensure that there are no issues that are preventing the replication process from completing. If possible you can try testing connectivity and bandwidth between the two environments.
You may also want to consider increasing the frequency of your snapshots to ensure that they are more up-to-date in case of issues with replication.
You can also try to test replication with a single server and monitor its behavior to check if the issue is consistent or it is only happening with a specific server.
Relevant content
- asked 2 years ago
- asked a year ago
- asked 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago