Replication Error Insufficient storage space on device for datastore path

Products

• VMware Live Recovery

Issue/Introduction

Symptoms

• Replications are in RPO(error) state due to insufficient storage space on the target datastore and below error will be observed.
  VM_name replication error: Insufficient storage space on device for datastore path '[datastore]  VM_name/hbrdisk.RDID--XXXXXX-3a1f-4b10-XXX-XXXX.456521.XXXXXX.vmdk'.

• In cases where the replications are configured on the VSAN datastore, the fstrim run on the virtual machines running on the production site would have released some space on the production site VSAN datastore but the incremental sync is not yet completed on the target site due to which space is not released. Also in such cases, there will be a spike in datastore usage as the replicated data is stored in one or more redo logs at the target location. Redo logs are used to preserve the integrity of the replica. Once replication is complete, a new redo log is created for the next replication cycle. The old redo log is consolidated into the base disk. This consumes additional space. 

 

Environment

VMware vSphere Replication 8.x.x
VMware vSphere Replication 9.x.x

Cause

The storage location where replicated data is being sent is running out of space, preventing the replication process from completing successfully, often resulting in a failure message due to insufficient disk capacity on the target datastore. 

The target datastore is running out of space.

Resolution

Change the Target Datastore Location of the replicated VM. 

1. On the Site Recovery home page, select a site pair and click View Details.

2. Click the Replications tab and select a VM replication from Outgoing or Incoming options.

3. Select the VM and click the Reconfigure icon.

4. Click Next till you reach the Target datastore page of the Reconfigure Replication wizard.

5. Select a new datastore or a datastore cluster.

6. Click Next until you reach the Ready to complete page and click Finish to save your settings.

The vSphere Replication moves all replicated instances and configuration files to the new target datastore.

Note:  If there is no datastore with sufficient capacity, remove few vms from replications to free up some space and wait for the incremental sync and disk consolidation to complete to reflect the space changes if fstrim was run and the target datastore is VSAN

Additional Information

Note:

To change the target datastore, the old target datastore from which you want to move the replication data must be online.

We cannot change the target datastore, while you are performing a test recovery, you must wait for the test cleanup to be complete.

To change the target datastore when the old datastore is inaccessible, you must stop the replication to the old datastore and configure another replication to the new datastore or datastore cluster.