Video Screencast Help
Symantec Appoints Michael A. Brown CEO. Learn more.

Restore a VM with Backup Exec 2010 - Final error: 0xe000957e

Created: 22 Mar 2011 | 6 comments

Hi

I have an annoying problem with restores of our VM's in a new environment.

We have a single physical Backup Exec 2010 Server on 2008 Server Standard R2 and this backs up our two ESX 4.1 servers through vCentre .

All backups of our VM's are completing successfully via SAN Transport, however all restores fail with the same error: "Final error: 0xe000957e - Unable to create the new virtual machine."

I have tried VMware redirection and restoring over the original VM, both times the VM is created in vCentre  but when data starts to restore the restore fails (around 23,700 bytes).

Here is an extract from the log:

 
Restore started on 3/21/2011 at 3:42:33 PM.
Job Log: BEX_XXXXBKP01_00094.xml
Restore Set Detail Information -
Error writing file data.
Restore completed on 3/21/2011 at 3:46:47 PM.
Restore Set Summary -
Restored 0 files in 0 directories. Processed 23,784 bytes in  4 minutes and  14 seconds. Throughput rate: 0.005 MB/min
 
 
Job Completion Status -
Job ended: Monday, March 21, 2011 at 3:46:51 PM Completed status: Failed Final error: 0xe000957e - Unable to create the new virtual machine. Final error category: Resource Errors
 
For additional information regarding this error refer to link V-79-57344-38270
 
Errors -
Click an error below to locate it in the job log
 Restore- VMVCB::\\10.131.0.19\VCGuestVm\ROA\vm\ROA_Restore\XXXXTEST VMVCB::\\10.131.0.19\VCGuestVm\ROA\vm\ROA_Restore\XXXXTEST Error writing file data.
 

I've searched for an answer but have had no luck, any help appreciated.

 

Comments 6 CommentsJump to latest comment

dw_uk2000's picture

I did a search prior to posting the query, your links are all pointing to 129931 but I double checked that I had already tried the workarounds for each tech doc.

It does look like a standard error message that isn't very helpful, I think the second part (Error writing file data.
V-79-57344-65072 -Connection to the restore target has been lost. Operation canceled.) has more meaning but can't see why as I've checked the services, rights etc.

I can do a file restore of the vmdk just not a VMware restore (which is what we need for our environment)

Cheers for trying anyway.

jdcotr's picture

I have the same setup and the same issue. Did you ever get a fix?

dw_uk2000's picture

Kind off.

Installed the latest edition 2010 R2 SP1, this fixed the problem.

WATC's picture

May not be related, but it took me a while to think about checking this so I thought I'd mention it anyway in case someone else is in a similar situation.

The account our Backup Exec 2010 setup uses is the same one our 12.5 setup used, and this was given the VCB permission set, which worked fine for backing up with VCB. The account is a domain admin and all domain admins have full administrative rights within vSphere, but it seems the more specific entry took precedence.

The backups under BE 2010 were completing fine, but every attempt to restore resulted in the 'unable to create the new virtual machine' error message. When I set the Backup Exec service account to have full administrative rights within vSphere, restores starting working.

This will probably only be an issue for people upgrading from a VCB-based setup where the Backup Exec account had only the specific permissions required for VCB to work.

jdcotr's picture

I still couldn't restore even with R2 SP1. In the end I got it working by amending the BE service account permissions within vCenter. I'd set a new role up specifically for the BE service account using the link below but it appears these permissions arn't adequate for restores: -

http://www.symantec.com/business/support/index?page=content&id=TECH129645

I'm still fine tuning exactly what is required but I've had to add additional permissions under the Virtual Machine, Network and Datastore options. After each change a restart of the BE services is required (on both the managed media server and CASO server if running CASO). Restores are now running fine.