Reprotect failed with "The object has already been deleted or has not been completely created error"
search cancel

Reprotect failed with "The object has already been deleted or has not been completely created error"

book

Article ID: 402520

calendar_today

Updated On:

Products

VMware Live Recovery

Issue/Introduction

Symptoms:

The administrator conducted a planned test failover, followed by reprotect and failback. During the subsequent reprotect, some VMs were deleted before completion.

Attempts to rerun reprotect with the force option failed.

The SRA shows volume replication has switched back to the DR site, and all options in the SRM interface are now greyed out except "Reprotect."

Environment

vSphere Live Recovery (all versions)

Cause

The reprotect failed because some virtual machines were accidentally removed from the vCenter inventory before it finished, so Site Recovery Manager can’t find them and can't continue.

Resolution

1) The protection group and recovery plan must be deleted.

If the Delete option is unavailable, the SrmDbTool.py utility should be used to delete the protection group and recovery plan directly from the SRM database. Refer to the article for SRM DB tool usage Unable to remove a VM from the protection group

2) Recreate the protection group and recovery Plan.