Article number
000003003
Affected Versions
All
Source Hypervisor
All
Protection group failover before commit. Failed: Failed to create disk 3 times
Viewed 348 times
Root Cause
A recovery VRA used by the VPG that failed is configured to use a datastore that is inaccessible for at least one journal or recovery disk.
Other VPGs that are not configured to use the inaccessible datastore my also fail if they use any recovery VRA that has at least one journal or recovery disk stored on the inaccessible datastore.
The inaccessible datastore will prevent changes to the VRA VM VMX file as long as a disk on the inaccessible datastore is attached to the VRA VM.
Other VPGs that are not configured to use the inaccessible datastore my also fail if they use any recovery VRA that has at least one journal or recovery disk stored on the inaccessible datastore.
The inaccessible datastore will prevent changes to the VRA VM VMX file as long as a disk on the inaccessible datastore is attached to the VRA VM.
Symptoms
After starting a test failover, live failover, or move task, the task fails with the error:
Protection group failover before commit. Failed: Failed to create disk 3 times
The following Zerto alert is active before or during the task:
Storage [datastore name] is not accessible
Protection group failover before commit. Failed: Failed to create disk 3 times
The following Zerto alert is active before or during the task:
Storage [datastore name] is not accessible
Solution
Once the storage is accessible again, retry the test failover, live failover, or move task.
The health of the datastore can be tested by attempting to create a VMDK on this datastore via the vSphere client.
If datastore maintenance or other activity is planned, then edit any VPGs using this datastore for journal or recovery disk storage, and change the VPG settings to use an active datastore until the datastore is available again.
The health of the datastore can be tested by attempting to create a VMDK on this datastore via the vSphere client.
If datastore maintenance or other activity is planned, then edit any VPGs using this datastore for journal or recovery disk storage, and change the VPG settings to use an active datastore until the datastore is available again.