• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1837
  • Last Modified:

VM won't boot after failed VEEAM backup attaemt

Was attempting to backup a VM guest using VEEAM 5 yesterday.  For some reason, it didn't work, and now when I try to boot the VM up, I get a "Disk error, press Ctrl. Alt. Del to reboot" error.  I do have vCenter and can browse the files for this VM.  Can I manually go in and delete files to put it in the state it was before the attempted backup so I can get it up and running again?  If so, which files can I delete? Which are needed?  And do I have to modify any CID's or anything so I can boot it up again?  Thanks in advance.
0
tenover
Asked:
tenover
  • 3
  • 3
1 Solution
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
If there are any snapshots present, that Veeam Backup has left, remove these from the Snapshot Manager.

Was the VM working before Veeam Backup?
0
 
tenoverAuthor Commented:
Yes, VM was working fine before the attempted backup.  There's nothin listed in Snapshot Manager, however there are snapshot files and other files that don't look like they should be there when I browse that VM in the data store.
0
 
tenoverAuthor Commented:
Yes, VM was working fine before the attempted backup.  There's nothin listed in Snapshot Manager, however there are snapshot files and other files that don't look like they should be there when I browse that VM in the data store.
0
Restore individual SQL databases with ease

Veeam Explorer for Microsoft SQL Server delivers an easy-to-use, wizard-driven interface for restoring your databases from a backup. No expert SQL background required. Web interface provides a complete view of all available SQL databases to simplify the recovery of lost database

 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
What failed with the Veeam Backup, was the VM on, when you tried to backup?

Any Veeam Backup error, any VM error?

What other attempts have you made to cure this issue?

Did the VM go off?

What events have happened, to cause the VM to reboot with this disk fault, which seems like a disk failure or corruption issue, that's why it's not booting.

Disk/Data Corruption?
0
 
tenoverAuthor Commented:
Not sure what failed, that's the problem.  The VEEAM backup had a red exclamation mark next to it and the VM was powered on when I started the backup and then when I came in this morning, it was powered off and threw the error when rebooted.  I just recreated the VM and pointed to an older set of files that I happened to have on hand....So I got the machine up and running.  Just backed up 2 other VMs on the same host using VEEAM without any issues.  I do the VEEAM backups with the VM's powered ON, that should be the way to do it, correct?
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
I just recreated the VM and pointed to an older set of files that I happened to have on hand...

If this is correct, you will need to make sure, you correct the CIDS if they mismatch, and update the snapshots in the VMX file.

or update the CIDs, and then Merge the Snapshot file at the command line.

See here to fix the snapshot CID mismatch

Resolving the CID mismatch error: The parent virtual disk has been modified since the child was created
http://kb.vmware.com/kb/1007969

http://edgylogic.com/driveactivated/recovering-vmware-snapshot-after-parent-changed/

But you will also need to regenerate the VMX file, to ensure that when you fix the above CIDs in the files, that you include the correct items in the VMX file.

or Merge Snapshots at the command line.

(but do not do this until you have fixed the CIDs)

See here

Merge Snapshots at command line
http://kb.vmware.com/kb/1002310
http://kb.vmware.com/kb/1006847

If Veeam Backup caused the issue, it's possible you could exclude the last Snapshot file. But I would proceed as above.
0
 
RickEpnetCommented:
It may just be a coincidence and have nothing to do with the backup software. For example that happened to me one time I was having an issue with a UPS and it would restart the server and it normally did it in the middle of the backup leading me to believe it was the backup but once I replace the UPS everything worked fine.
0

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 3
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now