Troubleshooting VMDK and RDM dedupe datastore issues in VMware Data Recovery
search cancel

Troubleshooting VMDK and RDM dedupe datastore issues in VMware Data Recovery

book

Article ID: 307211

calendar_today

Updated On:

Products

VMware

Issue/Introduction

This article guides you through the process of troubleshooting issues where virtual disks (VMDK) or raw device mappings (RDM) are used for a dedupe datastore in VMware Data Recovery (VDR). This article identifies common configuration problems.


Environment

VMware Data Recovery 2.x
VMware Data Recovery 1.x

Resolution

Validate that each troubleshooting step below is true for your environment. Each step provides instructions or a link to a document, in order to eliminate possible causes and take corrective action as necessary. The steps are ordered in the most appropriate sequence to isolate the issue and identify the proper resolution. Please do not skip a step.
  1. Confirm that the VDR appliance and the plugin are updated to the current version. For more information on upgrading, see the VMware Data Recovery Documentation.

  2. Check the release notes for current releases to see if the problem has been resolved. You can view the release notes for VMware Data Recovery 1.2.1 here.

  3. Determine if the upgrade to the current version was performed as per the guidelines where the deduplication datastore is contained on a virtual disks (VMDK) or raw device mappings (RDM) directly attached to the VDR appliance. For more information, see Upgrading to VMware Data Recovery 1.2 where virtual disks (VMDKs) or raw device mappings (RDMs) are used as a dedupe datastore (1022346).

  4. Verify that the virtual disks (VMDKs) or RDMs are stored in supported storage. For more information, see the VMware Compatibility Guide.

  5. Confirm that the VMDK/RDM based deduplication store is not more than 1TB. While VDR can write to larger dedupe stores, performance and integrity is unknown. VMware recommends creating another dedupe store and another backup job to back up one set of virtual machines to the new dedupe store. When they have enough backups of those virtual machines, mark the older backups of those virtual machines from the first dedupe store for deletion. For more information, see Special Data Recovery CompatibilityConsiderations in the VMware Data Recovery 1.2 Administration Guide.

  6. Verify that the VDR appliance is using only two deduplication stores. For more information, see Deduplication Store Benefits in the VMware Data Recovery 1.2 Administration Guide.

  7. Determine if there are any storage connectivity issues. For more information, see:
  8. Unmount any NFS export directly mounted to the VMware Data Recovery Appliance. For more information, see VMware Data Recovery backup to NFS fails with error: Trouble writing to destination volume, error -102 (1037309).

Note: If your problem still exists after trying the steps in this article:


Additional Information

Troubleshooting connectivity issues to an NFS datastore on ESX and ESXi hosts
Collecting diagnostic information for VMware products