Article number
000003779
Affected Versions
7.5
8.0
8.5
7.0
Source Hypervisor
All
Target Hypervisor
VMware

Error: “Failed to relocate VM [vm-xxx] volume to [datastore][vmdk_location]” when Updating VPG to Migrate Journal/Recovery Disks Between Datastores

Viewed 729 times

Summary

An administrator may notice an error when Updating a VPG in efforts to migrate journal and/or recovery disks between datastores regarding failure to relocate.

Root Cause

By default, Zerto has a 30 minute timeout for disk relocation tasks. In some environments, this timeout is too strict and needs to be increased for Zerto to allow VCenter to complete the task. Alternatively, performing the task in VCenter directly is also an option as it would avoid the timeout entirely.

Symptoms

Administrator submits an Update VPG task to change the journal/recovery datastore in use for any/all VMs in the VPG. After ~30 minutes of the task running, the below failure is seen:

Update protection group. Failed: Failed to relocate VM [vm-xxx] volume to [datastore][vmdk_location]

Solution

There are two options to workaround this issue:

  1. Perform the svmotion/migration manually via vSphere. Zerto will receive the updated location of the disk(s) as part of the reflection collection process.

  2. Alternatively, engage Zerto Support to assist with increasing the default timeout.