Unable to start vmProtect appliance

Thread needs solution
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Posts: 2
Comments: 1

Hi

I am getting the following error when attempting to start the vmProtect appliance:

An unexpected error was received from the ESX host while powering on VM vm-798.
Reason: The parent virtual disk has been modified since the child was created. The content ID of the parent virtual disk does not match the corresponding parent content ID in the child.
Cannot open the disk '/vmfs/volumes/3231739b-f5955f10/APP/APP-000002.vmdk' or one of the snapshot disks it depends on.

Background:

A backup failed, and the VM in question was left in a state where snapshot consolidation was required. First attempt at this failed with an error that a disk was locked. I assumed this was because vmProtect has the disk locked, so shut down vmProtect appliance and performed the snapshot consolidation on the VM which was successful.

Now when starting the vmProtect appliance it is obviously looking for the snapshot on the VM which no longer exists and fails to start.

Any ideas on how to resolve this short of blowing away the appliance and reinstalling would be appreciated.

thanks

Russell.

Fri, 03/02/2012 - 03:35
0 Users found this helpful
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Posts: 7
Comments: 15

I thought about this some more... The VMDK for the backup machine in question is probably still attached to the Appliance. Now that you have removed the old snapshots they may still be linked here. Edit the appliance and see if the disk is still attached to the Acronis appliance. If you verify it is you should be able to safely remove it from the Acronis appliance.

(USE WITH CAUTION: MAKE SURE YOU KNOW WHAT YOUR DOING.)

Go to hardware \ view the hard disks attached \ select remove \ Select REMOVE FROM VIRTUAL MACHINE.

MAKE SURE NOT TO REMOVE AND DELETE AS THIS WOULD DELETE YOUR GUEST VIRTUAL MACHINE DISK.

Fri, 03/02/2012 - 14:46
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Posts: 2
Comments: 1

This worked perfectly, thanks for your help vwemil. I think it took us several months to get comfortable with other Acronis products like Echo Server when we were dealing mainly with physical servers. Looks like we're going to go through a similar process with this one...

Tue, 03/06/2012 - 04:00
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Forum Member
Posts: 6
Comments: 25

Thanks this fixed the issue. It didn't like one of my data stores for some reason. Once I removed those hard drives it booted back up.

Mon, 12/31/2012 - 17:12