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 as a VRM virtual machine replication user or a VRM administration user. See vSphere Replication Roles Reference.


  1. In the vSphere Client or the vSphere Web Client, click Site Recovery > Open Site Recovery.
  2. On the Site Recovery home tab, select a site pair and click View Details.
  3. In the Replications tab, click Forward Replications or Reverse Replications.
  4. Right-click a replication and select Remove.

    vSphere Replication asks you if you want to permanently stop the replication for the selected virtual machine.


    The hosts and vSphere Replication server used by the replication must be accessible to stop a replication on both sites. If a host or the server is not accessible, you can force stop the replication on the accessible site by selecting Force stop replication. If you force stop the replication from Forward Replications, you must also force stop the corresponding replication from Outgoing Replications if the source site is available. If you force stop the replication from Reverse Replications, you can only force stop the corresponding replication from Incoming Replications.

  5. Click Remove to confirm that you want to stop replicating this virtual machine.


The virtual machine does not replicate to the target site.

When you stop a replication, the following operation is performed at the replication target site.

  • VMDK files are deleted from the target site datastore if the VMDK files were created when the replication was first configured.


When you stop a replication, vSphere Replication does not delete the replica directory at the target datastore. As a result, stale directories remain on VMFS and NFS target datastores, and unused namespaces remain on Virtual SAN and Virtual Volume target datastores. Because the maximum number of directories and namespaces on a datastore is limited, you must manually clean them up to free resources on the datastore. See Clean Up the Target Datastore After You Stop a Replication.