Skip to main content

vmprotect 8 Restore of Exchange 2010 mailbox fails

Thread needs solution

I've already opened a support case for this but this is unsolved since 20 days (!). Very bad support if you demand on a restore! Case-ID is 01952033.

When I start a restore of a mailbox the temporary VM is created in my vCenter. I can also see the temporary NFS datastore from the Acronis appliance and also access this datastore. But right after the temporary vm got started the connection to that temporary NFS store fails and it will be shown greyed out. The task persits for another hour at 18% and then fails.
I have to manually deregister the temporary vm in vCenter and also have to manually remove it's files from the datastore. Also any access to a SMB share from the Acronis Appliance VM fails afterwards. I have to restart the Appliance. When it got restarted I am able to access the temporary NFS share again (as it didn't got removed after cancelling the task). I can find stale files of the temporary exchange vm there.

It seems that the NFS daemon inside the Acronis Appliance crashes. But I cannot see anything in the normal logs of Acronis.

Thank you for a fast answer and workaround as this Problem persits for a long time
Dennis Koerner

0 Users found this helpful
frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Posts: 22
Comments: 3800

Hi Dennis,

Yes, looks like that NFS server service inside virtual appliance is crashing and this causes such behavior. I would first of all recommended to try vmProtect 9 Beta by subscribing for Beta program here: http://forum.acronis.com/forum/42675 where we fixed several similar issues. You can deploy a separate appliance from 9th version and use it for Exchange recovery without touching your original one (from 8th version). For deployment I'd recommended the following build of vmProtect 9 (it is newer than the one you get after subscribing for Beta program, but you still need to subscribe in order to get the serial numbers):

In case recovery still fails in 9th version with the same error then we'll need to check the NFS server logs which are located under /var/lib/Acronis/vmProtect/Logs/ folder. Please copy the entire /var/lib/Acronis/vmProtect/ folder from appliance as described in troubleshooting section of http://kb.acronis.com/content/36100 article, then pack it in .zip and send it over to me in a private message. I will check it out and will advise you further.

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

Hi Vasily,

the beta9 worked for me. Will this get fixed in a 8 release or do we have to upgrade to 9 for this essential functionality to work? I ask because I have one customer who didn't get the update subscription. So he will be stuck to a non working version 8. I don't think I can tell him: "Oh yes they sold you vmprotect8 for exchange restore but it is not working. You have to upgrade to version 9 which will cost you another $$$ and they don't care to fix their bugs for versions you already paid thousonds of $ for".

Thank you
Dennis

frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Posts: 22
Comments: 3800

Hi Dennis,

Thank you for the confirmation. In fact the issue you've got is specific to particular environment (i.e. it is not reproduced everywhere), so there are quite a lot of chances that your customer who doesn't have valid maintenance won't run into it. However if it is the case then we are still committed to provide support for 8th version and deliver the solution (which can be either 9th version or some kind of custom build for 8th version) for non-working critical functionality to particular customer. Typically such questions are resolved by support managers who take the decision, but in any case we always try to find solution which satisfies the customer in the first place (additional charge for new version is always an exception rather than a rule, but again all depends on exact circumstances).

If you are sure that your customer who doesn't have valid maintenance has the issue described in this thread, then I'd recommended to contact our support team with reference to this thread/post in order to get the final solution from Acronis support managers.

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