If you do not need to replicate a virtual machine, you can stop the replication of that virtual machine.

Take a note of the target datastore and the name of the replication that you are about to stop. You need this information to clean up your environment after you stop the replication.


Verify that you are logged in the vSphere Web Client or vSphere Client as a VRM virtual machine replication user or a VRM administrator user.


  1. Log in to the vSphere Client or vSphere Web Client.
  2. On the home page click Site Recovery and click Open Site Recovery.
  3. On the Site Recovery home page, select a site pair and click View Details.
  4. Click the Replications tab and select a replication from Outgoing or Incoming.
  5. Click the Remove icon.
    vSphere Replication asks you if you want to stop permanently the replication for the selected virtual machine.
    Note: The connection between the vSphere Replication sites must be working to stop a replication on both sites. Alternatively, you can force stop the replication on the local site by selecting Force stop replication. If the remote site is available, you must also use the Site Recovery user interface to force stop the corresponding replication on the remote site. If you force stop a forward replication, the replication can still be recovered by using the Site Recovery user interface on the remote site.
  6. Click Remove to confirm that you want to stop replicating this virtual machine.
    If you want to retain your replica disks, select the Retain replica disks check box.
  7. Inspect the target datastore for any leftover replica disks and files. Delete them if you do not plan to use them as seeds in the future.


The virtual machine does not replicate to the target site.

When you stop a replication, the following operations are performed at the replication target site.
  • If the VMDK files were created when the replication was first configured, the VMDK files are deleted from the target site datastore.
  • If you configured the replication to use existing disks at the target site as seeds, the VMDK files are not deleted and remain on the target datastore.