1 Answer
- Newest
- Most votes
- Most comments
0
Hi,
This behavior can sometimes happen if server "B" and server "E" share the same "identity" that the Agent picks up. For example, for VMware machines the VM UUID is picked up by the agent and can be seen in the "Server info" tab[1]. If your two VM's share the same VM UUID (typical scenarios which cause this can be cloning/copying a VM), this can cause the behavior you noticed.
I hope this information is helpful.
Resources: [1] Server info - https://docs.aws.amazon.com/mgn/latest/ug/source-server-info.html
answered a year ago
Relevant content
- asked 6 months ago
- Accepted Answerasked 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
Ideally, this shouldn't happen. Is the source server name the same for the two servers? Please open a ticket with the support team.