Knowledge Base

The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides
 
Search the VMware Knowledge Base (KB)   View by Article ID
 

Troubleshooting VMware Data Recovery backup issues (1038927)

Purpose

This article provides information on the process troubleshooting VMware Data Recovery (VDR) backup issues, and identifies some common reasons for backup failures.

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. Verify that the VDR appliance and the plug-in 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 issue has been resolved. You can view the release notes for VDR 1.2.1 here.

  3. Verify that the VDR appliance is connected. For more information, see Troubleshooting VMware Data Recovery connectivity (1037995)

  4. Restart the VMware data recovery service. For more information, see Restarting the datarecovery service on a VMware Data Recovery appliance (1036768).

  5. Verify that there are no destination related issues. For more information, see:
  6. Verify that the IP address of the ESX host and vCenter Server can be resolved from the VDR appliance. For more information, see VMware Data Recovery backup operations fail with error: -3948 (vcbapi exception) (1011678).

  7. Determine whether there are errors related to the filesystem in the var/log/messages reported on the VDR appliance. For more information see, Booting VMware Data Recovery fails with the error: ext3-fs warning: maximal mount count reached reported on boot (1020974).

  8. Verify that the VDR appliance has free space on the disk that holds the dedupe store. For more information, see VMware Data Recovery (VDR) fails to run backups even after a reclaim (1027607).

  9. If the backup job fails to start on time, see VMware Data Recovery backups do not start on time (1019139).

  10. If VDR performs a full backup instead of an incremental backup on some virtual machines, see VMware Data Recovery performs a full backup instead of an incremental backup on some virtual machines (1026142).

  11. If editing an existing backup job fails, see Editing an existing backup job in VMware Data Recovery 1.x fails with the error: More than 0 virtual machines were selected (1033813).

  12. Verify that VDR is not using the network for backing up larger virtual machines. For more information, see When does VMware Data Recovery use network based copy instead of SCSI Hot-Add (1012862).

  13. Determine whether the backup job fails due to the deduplication store being locked. For more information, see Automatic and manual VMware Data Recovery backups fail (1014860).

  14. Determine whether the virtual machine being backed up has RDMs attached. For more information, see VMware Data Recovery backup job fails when backing up a virtual machine with RDMs (1015488).

  15. If the reclaim job fails to run, see VMware Data Recovery reclaim job fails to run (1031220).

  16. Determine whether the configuration of the appliance has been modified. For more information, see VMware Data Recovery performs only a single backup at a time (1024552).

  17. To understand the reclaim operation of VMware Data Recovery, refer to article Understanding reclaim operations in VMware Data Recovery (1039075).
Note: If your problem still exists after trying the steps in this article:
 
 

Tags

vdr-backup-fails

See Also

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

  • 9 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.
What can we do to improve this information? (4000 or fewer characters)
  • 9 Ratings
Actions
KB: