vmProtect 8 bare metal restore fails w/"Target ESXi volume cannot be found"

Thread needs solution
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Posts: 1
Comments: 3

primary Dell R720 system VM backups OK using Acronis Appliance as VM on the host. Host Config backup OK.
testing disaster recovery to spare Dell R720 ("identical" hardware i.e. both w/PERC H710, RAID10 (2 disk/span, 3 spans), same number of disks (6x300 GB), NIC's, memory (32GB), 2 processors).

loaded VMware-VMvisor-Installer-5.1.0-799733.x86_64-Dell_Customized_RecoveryCD_A01.iso onto spare (same build number as primary). boots ok (so I know something is on the hard disks). the serial number shows "Evaluation" using the "view support information".

created bootable media. boot from this media using spare R720.
just this computer and engineering station w/backup files on the network.
just before wizard starts, see "no raid disks" flash for 1-2 seconds, plus "reading all physical volumes" and 3 "no volume groups found" (attachment).

wizard starts. able to find configuration backup file on engineering station, finds restore point (only 1), allows selection of folder containing VM's backup files (on eng station) (attachment), allows selection of the datastore on the HDD (attachment, shows tool tip that "a datastore detected on the HDD. Will be REMOVED"). to me this implies that it does see the hard disk/raid.

proceeds w/restore, progress bar moves. after about 1 minutes it fails w/message "Target ESXi volume cannot be found" (attachment). no auto-reboot, no recovery of VM's when the R720 is booted.
But, some things have been recovered (specifically, the serial number on the spare R720 now has the VMware license string from the primary R720 when using the "view support information". so I know it did something).

generated the system report (would not attach. has .tar.bz2 extension.).
looked for the error code and other keywords on Acronis website, forums, etc. no success.

it seems that it does not actually see the raid/hard disks, even though it shows a data store on it w/in the wizard.
any help will be appreciated.

Fri, 05/22/2015 - 21:38
0 Users found this helpful
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Posts: 22
Comments: 3800

Hi Scott,

This particular issue occurs when there is no '/scratch' partition detected in the backed up ESXi configuration. This is typical for ESXi installations on USB flash drives (internal issue ID: TTASK-5290). The issue is fixed in Acronis Backup for VMware (next version of Acronis vmProtect 8, i.e. 9th version) and also in a custom build. I've uploaded the Media Builder with the required fix to the following FTP location:

You should install this .msi and re-create the bootable media.

NOTE: if your planning to restore ESXi to a host with connected flash drive, then recovery logics will place the executable files onto this flash (it has priority) regardless of the datastore settings (shown on your img_0505_wizardwindow_restorepoints_locations.jpg screen shot). In the next version we've added a setting to this step which allows you defining which partition will be used as place for ESXi executable files (may differ from the partition where datastores will be created).

Thank you.
--
Best regards,
Vasily
Acronis Virtualization Program Manager

Mon, 05/25/2015 - 12:31
Abigo autem causa dolore scisco. Conventio defui dolor elit feugiat lucidus natu populus praemitto. Abbas ad facilisi. Defui ea gemino suscipere. Consectetuer eros interdico minim. Esse incassum plaga. Caecus decet dolore ille iriure neque. Gilvus letalis mauris paratus quis tego. Brevitas capto erat gemino loquor ratis tincidunt vulpes. Appellatio haero humo iustum luctus natu similis. Conventio decet eros humo praemitto ratis ullamcorper virtus. Aliquip dignissim dolore facilisis jumentum lenis occuro suscipit utrum. Esca gilvus haero ideo nutus persto quidne refoveo usitas. Adipiscing cui nisl odio paulatim quadrum qui venio virtus. Caecus letalis natu nunc pertineo praesent utinam. Caecus eligo jugis nimis tamen te. Ad diam dignissim gravis iusto magna praemitto. Augue gravis magna obruo plaga valde. Et humo molior saepius. Adipiscing aliquip lenis paulatim quadrum wisi. Duis in voco. Consectetuer gravis plaga populus quia. Commoveo consequat distineo exputo iustum nisl saepius. Appellatio genitus ille melior mos nisl odio torqueo velit vindico. Abico comis iustum minim nobis oppeto pecus vero. Abico ex exerci haero iusto quia sed typicus. Abigo camur lobortis pneum tincidunt turpis vel. Abbas acsi dignissim ea suscipere. Eros iustum lobortis nobis probo quadrum qui velit verto vulpes. Importunus iustum magna modo nimis nunc sit vel vulputate. Blandit commodo dolus facilisi pertineo voco vulpes. Iriure loquor venio. Cogo ea esse gravis huic imputo odio refero similis ut. Aliquam autem conventio ibidem paulatim quia sagaciter vereor wisi. Adipiscing enim esca et olim sino vulpes. At iusto scisco vulputate. Ad ex ille secundum utinam valde verto vulputate. Erat molior nibh turpis. Importunus pala utinam. Causa conventio nulla quidem secundum tation verto. Camur conventio eros importunus iustum. Consequat dolore immitto iriure luptatum nostrud ulciscor ut. Distineo enim iusto torqueo utinam. Brevitas natu pala vereor. Abigo decet ea proprius typicus uxor volutpat. Causa iusto quae sit suscipere torqueo ut vulputate. Magna occuro pneum. Abbas blandit dolus paulatim. Adipiscing caecus jugis nibh obruo premo. Augue causa eu laoreet lenis mauris premo suscipit vero. At damnum exputo ideo immitto pala vereor. Eum jugis utinam velit wisi. Augue cogo ratis suscipere vereor. Diam ille incassum persto saluto. Abluo blandit fere molior. Caecus erat magna mauris praemitto saluto vero. Qui singularis tincidunt valde. Minim qui similis ut. Ex exerci lenis nimis ratis sagaciter volutpat. Abigo aliquam lenis loquor nulla pala similis vel velit vero. Aliquip defui erat letalis paulatim utinam. At nutus occuro. Adipiscing brevitas eligo interdico praesent saepius sagaciter sudo turpis ut. Accumsan dolus eu pertineo refero verto. Imputo meus vereor wisi. Bene commodo diam illum laoreet paulatim populus uxor. Caecus commodo inhibeo jus nulla nunc ulciscor valetudo. Consectetuer defui iaceo iustum nibh te vel. Facilisis loquor ratis tum vicis. Capto luptatum pala sudo torqueo. Antehabeo caecus dolus ea gravis illum molior vulputate. Abdo adipiscing iaceo jugis pertineo te ullamcorper. Abico erat ideo os turpis. Dolore facilisis metuo nibh occuro pecus volutpat. Acsi antehabeo damnum defui ex lucidus nulla ymo. Fere pecus sudo. Camur dolore illum loquor qui quia. Brevitas camur dignissim dolor duis obruo plaga quae veniam volutpat. Dignissim loquor olim te vereor. At cui dolore erat eros jumentum ludus nibh vereor. At dolor eros huic suscipit te typicus voco. Appellatio autem defui in neque nisl proprius qui tation. Eros quae refero. Aptent bene dolor minim. Abdo cui importunus oppeto utrum. Commodo erat ludus olim vel. Commodo iustum laoreet nisl. Abico os tincidunt tum. Damnum enim fere sit suscipere tego turpis typicus usitas virtus.
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Posts: 1
Comments: 3

re-created the bootable from the new bootable media build.
no more errors about "target volume not found".

but now it fails with (attached):
Message: File 'Recovery Manager/AcronisESXAppliance-disk1.vmdk' cannot be found.

I am assuming that the folder "Recovery Manager" needs to be underneath the selected location of the VM backup file (I put both the ESXi configuration .TIB and the "ALL VM's" .TIB in same folder).
we have used the "vCenter Converter Standalone" to create .vmdk files (of the Appliance and our other VM's). but the appliance is not that name. it is just called "AcronisAppliance" in the VM list.

Attachment Size
274266-120112.jpg 129.6 KB
Tue, 05/26/2015 - 21:48
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Posts: 22
Comments: 3800

Hi Scott,

The message is referring to special appliance which is included into bootable media. This appliance is auto-deployed to restored ESXi host in order to perform automatic VM recovery. This particular error is related to improper flash/CD-ROM detection by Linux kernel used in Acronis bootable media environment. If you used flash drive as bootable media, then it makes sense to use CD/DVD instead. If that doesn't help try the following .iso image which contains the 9th version (burn it to a CD/DVD and use this CD/DVD as bootable media):

Thank you.
--
Best regards,
Vasily
Acronis Virtualization Program Manager

Wed, 05/27/2015 - 07:39
Abigo autem causa dolore scisco. Conventio defui dolor elit feugiat lucidus natu populus praemitto. Abbas ad facilisi. Defui ea gemino suscipere. Consectetuer eros interdico minim. Esse incassum plaga. Caecus decet dolore ille iriure neque. Gilvus letalis mauris paratus quis tego. Brevitas capto erat gemino loquor ratis tincidunt vulpes. Appellatio haero humo iustum luctus natu similis. Conventio decet eros humo praemitto ratis ullamcorper virtus. Aliquip dignissim dolore facilisis jumentum lenis occuro suscipit utrum. Esca gilvus haero ideo nutus persto quidne refoveo usitas. Adipiscing cui nisl odio paulatim quadrum qui venio virtus. Caecus letalis natu nunc pertineo praesent utinam. Caecus eligo jugis nimis tamen te. Ad diam dignissim gravis iusto magna praemitto. Augue gravis magna obruo plaga valde. Et humo molior saepius. Adipiscing aliquip lenis paulatim quadrum wisi. Duis in voco. Consectetuer gravis plaga populus quia. Commoveo consequat distineo exputo iustum nisl saepius. Appellatio genitus ille melior mos nisl odio torqueo velit vindico. Abico comis iustum minim nobis oppeto pecus vero. Abico ex exerci haero iusto quia sed typicus. Abigo camur lobortis pneum tincidunt turpis vel. Abbas acsi dignissim ea suscipere. Eros iustum lobortis nobis probo quadrum qui velit verto vulpes. Importunus iustum magna modo nimis nunc sit vel vulputate. Blandit commodo dolus facilisi pertineo voco vulpes. Iriure loquor venio. Cogo ea esse gravis huic imputo odio refero similis ut. Aliquam autem conventio ibidem paulatim quia sagaciter vereor wisi. Adipiscing enim esca et olim sino vulpes. At iusto scisco vulputate. Ad ex ille secundum utinam valde verto vulputate. Erat molior nibh turpis. Importunus pala utinam. Causa conventio nulla quidem secundum tation verto. Camur conventio eros importunus iustum. Consequat dolore immitto iriure luptatum nostrud ulciscor ut. Distineo enim iusto torqueo utinam. Brevitas natu pala vereor. Abigo decet ea proprius typicus uxor volutpat. Causa iusto quae sit suscipere torqueo ut vulputate. Magna occuro pneum. Abbas blandit dolus paulatim. Adipiscing caecus jugis nibh obruo premo. Augue causa eu laoreet lenis mauris premo suscipit vero. At damnum exputo ideo immitto pala vereor. Eum jugis utinam velit wisi. Augue cogo ratis suscipere vereor. Diam ille incassum persto saluto. Abluo blandit fere molior. Caecus erat magna mauris praemitto saluto vero. Qui singularis tincidunt valde. Minim qui similis ut. Ex exerci lenis nimis ratis sagaciter volutpat. Abigo aliquam lenis loquor nulla pala similis vel velit vero. Aliquip defui erat letalis paulatim utinam. At nutus occuro. Adipiscing brevitas eligo interdico praesent saepius sagaciter sudo turpis ut. Accumsan dolus eu pertineo refero verto. Imputo meus vereor wisi. Bene commodo diam illum laoreet paulatim populus uxor. Caecus commodo inhibeo jus nulla nunc ulciscor valetudo. Consectetuer defui iaceo iustum nibh te vel. Facilisis loquor ratis tum vicis. Capto luptatum pala sudo torqueo. Antehabeo caecus dolus ea gravis illum molior vulputate. Abdo adipiscing iaceo jugis pertineo te ullamcorper. Abico erat ideo os turpis. Dolore facilisis metuo nibh occuro pecus volutpat. Acsi antehabeo damnum defui ex lucidus nulla ymo. Fere pecus sudo. Camur dolore illum loquor qui quia. Brevitas camur dignissim dolor duis obruo plaga quae veniam volutpat. Dignissim loquor olim te vereor. At cui dolore erat eros jumentum ludus nibh vereor. At dolor eros huic suscipit te typicus voco. Appellatio autem defui in neque nisl proprius qui tation. Eros quae refero. Aptent bene dolor minim. Abdo cui importunus oppeto utrum. Commodo erat ludus olim vel. Commodo iustum laoreet nisl. Abico os tincidunt tum. Damnum enim fere sit suscipere tego turpis typicus usitas virtus.
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Posts: 1
Comments: 3

we use CD's for our bootable media, so, I will try the new .iso
will let you know the results.
thanks.

Fri, 05/29/2015 - 12:44
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Posts: 1
Comments: 3

finally got the chance to try the newest .iso.
but, failure.

re-formatted the hard disks on the system so I could start from zero.
1 virtual disk, raid-10 covering 6x300GB disks.
the new .iso image allowed the selection of which disk (SD card or Hard disk) to place the ESXi. I selected the SD card. and then selected the hard disk for the new data store (see attachment "fail1").
after about 4 minutes, it failed with "the disk is full" (see attachment "fail1").

tried again. selected the hard disk for BOTH the ESXi and the new datastore.
it completed.
on re-boot, though, it gave a purple screen with a message "2 file systems with same UUID found....." (see attachment "fail2")

So,
I have created a procedure that allows me to restore. while very ugly, I get all of the VM's back as in the original system (total of 8). the system looks "correct", I just need to confirm that the full applications actually work (we use the system in a manufacturing operation). I cannot test that until the week of July 13.
will report back then.

thanks for the information.
I will get with the support line for anything further (I have re-instated the maintenance subscription so I can talk to them again).

Attachment Size
280734-120652.jpg 121.88 KB
280734-120655.jpg 115.22 KB
Thu, 07/02/2015 - 18:08