Operational Defect Database

BugZero found this defect 3958 days ago.

Veeam | kb1773

How-To: Manually Repair a VMware Replica created by Veeam

Last update date:

1/10/2024

Affected products:

Veeam Backup & Replication

Affected releases:

8.0

Fixed releases:

No fixed releases provided.

Description:

Challenge

This article explains how to manually revert a replica to its base disks, allow it to be remapped to a replication job and used as a seed when the replica's snapshot files have become corrupt.

Cause

An old or orphaned Snapshot file is linked to the VM configuration (vmx), and a new Snapshot is trying to use that file name.

Solution

Please be aware that as an alternative to performing the steps below, you may first attempt to clone the faulty replica within VMware; if it succeeds, map the Replication job to the clone of the replica.   Before Beginning Stop all replication jobs to the target location of the replica in question. Manually check each target side proxy for stuck replica hotadded disks. (Consider switching the target proxies to use Network transport mode to prevent this if it becomes a problem). See KB1775 for details. Gather Information Edit the Replica Note what disk files correlate to each SCSI ID. Example:[Datastore1] DC01_replica\DC01-00000023.vmdk on SCSI0:0 [Datastore1] DC01_replica\DC01_1-00000023.vmdk on SCSI0:1 [Datastore2] DC01_replica\DC01-00000023.vmdk on SCSI0:2 Prepare the Replica Open the Snapshot manager and starting with the oldest snapshot, delete the snapshots one at a time. The goal is to get as much new information into the base disks as possible. At some point though, there will be a snapshot that will not remove. If any snapshots are left in the snapshot manager, try using the Delete All option in the snapshot manager. Use the consolidate function to consolidate any orphaned snapshots. Note: It is expected for these steps to fail at some point. When you receive a failure, move on to the next step. Preparing Veeam Backup & Replication Within the Veeam console under Replicas, find the replica that will be repaired and right-click it. From the context menu, choose “Remove from replicas…” ("Remove from configuration")Note: After you use the “Remove from replicas…” ("Remove from configuration") function, it will remove the VM from the Replication job. You will have to add the VM back to the replication job manually. Detach Snapshot Disks and Attach Base Disks Edit the replica, and select each of the disks and click remove. It will put a strikethrough the drive and show the word (removing). After selecting all the disks for removal, press OK. Edit the replica again, reattach the base disks to the replica, choose to add an existing disk, and then navigate to the location of the base disks for the replica. Attach them to the same SCSI nodes that were noted earlier.When using the vSphere Web Client, if you run into a disk that displays “0” as the disk size, it won’t let you remove that disk from the VM. To remove this disk, you need to add a size to the disk. The number that you input here does not matter. We want to make sure the size of the disk no longer displays “0”. At this point, it will allow you to remove that disk. Datastore Cleanup Using the datastore browser, go to the folder of the replica. Most likely, there will be many files; keep in mind that the only files that are required are: VMX VMXF NVRAM VMDK for each disk. So, for example, here is a folder pre-cleanup post repair.We can remove the following files:Leaving the VMX, VMXF, NVRAM, and the VMDK for each disk. Removing the associated snapshot files that are no longer needed. Test the replica Create a snapshot on the replica. Remove the snapshot. If no error occurs, map the replica in a replication job and see if the job runs successfully.

Additional Resources / Links

Share:

BugZero® Risk Score

What's this?

Coming soon

Status

Solved

cost-cta-background

Do you know how much operational outages are costing you?

Understand the cost to your business and how BugZero can help you reduce those costs.

Have you ever...

had your data corrupted from a

VMware

bug?

Search:

...