App Volumes replication jobs fail due to metadata errors
search cancel

App Volumes replication jobs fail due to metadata errors

book

Article ID: 324567

calendar_today

Updated On:

Products

VMware

Issue/Introduction

Symptoms:
  • App Volumes replication jobs do not succeed
  • The following error or similar is observed in the logs:
[2022-01-01 23:59:59 UTC] P5368DJ4339689 INFO    Cvo: Duplicate token found while acquiring token "Cvo::VolumeModificationExecutor-[AppVolumes_NFS] appvolumes/packages/appstackname.vmdk.metadata": Validation failed: Unique name has already been taken


Cause

This issue occurs due to orphaned metadata on the target storage. When App Volumes performs replication it checks the target storage to see if the appstack has already been copied and if the metadata file already exists, for instance due to a previous underlying storage issue that caused incomplete copy operations to perform, the appstack copy operation will fail.

Resolution

App Volumes 4.6 (2203) contains a permanent fix for this issue.

Workaround:
If the target storage has only the metadata file and not the appstack vmdk it can be manually removed so that the copy operation of the appstack can complete.