Manually Launch Integrity Check in vDR September 22, 2010Posted by General Zod in Backup, Tech, VMware.
Yesterday, just before leaving the office, I added a couple of new VMs into one of my regular backup jobs via the VMware Data Recovery appliance in my environment. At the time, I noted that it was in the midst of a Integrity Check. No big deal as the backups would (should have) run after the check was completed.
So this morning, I set to checking the status of my VM backups when I discovered the following Warning in my vDR Reports.
** Integrity check failed for the restore point created on 9/20/2010 3:17:15 PM for ServerA
** Integrity check failed for the restore point created on 9/21/2010 12:50:00 AM for ServerB
** Backup Set "<path to VM backups>" will be locked until the restore point with errors are deleted and integrity check succeeds.
So my backups have some corruption in them… well… best to purge them ASAP. So I head over to the Restore tab, and locate the backups identified in the Warning report. As you click your way through the expandable tree of backups, these can be easily identified by their bold, red font…
+ 9/20/2010 3:17:15 PM (damaged)
+ 9/21/2010 12:50:00 AM (damaged)
Right-click each damaged backup, and select “Mark for Delete”… and you’ll see a little red X appear on each. Only problem is… these backups won’t actually be purged until the next Integrity Check is run. So what you need to do is kick is off manually to process this change ASAP.
Go to the Configuration tab, and click “Destinations”. Right-click the Destination where the backups were originally stored and select “Integrity Check”.
With that done, the Integrity Check will run, the corrupt backups will be purged, and the backup set destination will be unlocked (assuming no other issues exist).
I just wish VMware would make an option in vDR to automate the purge of corrupt backups during the Integrity Check in which the problem is discovered.