Solve VM replication issue related to vSphere replication

From Notes_Wiki
Revision as of 08:25, 10 May 2021 by Saurabh (talk | contribs) (Created page with "<yambe:breadcrumb self="Solve VM replication issue related to vSphere replication">VSphere replication or Site Recovery Manager|VSphere replication or Site Recovery Manager</y...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

<yambe:breadcrumb self="Solve VM replication issue related to vSphere replication">VSphere replication or Site Recovery Manager|VSphere replication or Site Recovery Manager</yambe:breadcrumb>

Solve VM replication issue related to vSphere replication

To solve VM replication issue for any VM due to vSphere replication, please check the following:

  1. There is enough space on destination datastore and destination datastore is not read-only due to some storage issue
  2. VM is powered on. Powered off VMs do not get replicated
  3. Proper replication is configured for the VM and it is not in paused state
  4. Rebooting vSphere replication Management Server (VRMS) and its additional vSphere Replication Managers (VRMS) on both sites helps in establishing connection, if it was lost due to network issues
  5. Validate connectivity from ESXi host of one site to VRMS of same site to VRMS of second side to ESXi host of second site. All four should be able to communicate with each other.
  6. If still there is issue then try the following
    1. Pause ongoing replication
    2. Rename replication folder at destination side
    3. Stop or force stop replication at both sides
    4. Rename replication folder at destination side same as before
    5. Reconfigure replication with seeds by selecting the replication folder
    6. Wait for initial sync to finish




<yambe:breadcrumb self="Solve VM replication issue related to vSphere replication">VSphere replication or Site Recovery Manager|VSphere replication or Site Recovery Manager</yambe:breadcrumb>