Symantec System Recovery 2013 r2 sp4 & Server 2008 r2 BSOD

That stop code usually indicates a driver issue. I assume you are restoring to different hardware?

Are you following this restore procedure? https://www.veritas.com/support/en_US/article.000006864

Yes we are following the restore procedure and the backup procedue.  I have been on the phone with Veritas for a week now.

Have you restore a Server 2008 r2 machine with only the c:\boot and no reserve partition?

Thank you for responding.

Oh sorry we are working on a vSphere restore right now.  Same setup on the Hardware settings.  We are having issues with our physical also.  When we restore then it is to the same hardware.

So for this issue, are you restoring to same or different hardware? Is this physical to physical, or physical to virtual etc?

virtual to virtual

So I assume (please confirm) that restore anyware is NOT enabled? Are the source and destination virtual machines on the same vSphere host?

Any difference between the 2 virtual machines?

So I assume (please confirm) that restore anyware is NOT enabled?

The Veritas technicians had me 2 times run restore without restore anyware, and the last one had me run it with it enable with only check mark for delete drivers. 

Are the source and destination virtual machines on the same vSphere host?

No.  We are in a critical environment, so we have a vSphere setup in a lab that we are testing with Veritas.  I performed a manual (not schedule) backup of the virtual machine I want to test with Veritas with to see if we are doing something wrong or if there is a bug in the software.  The backup image is then stored on our Data Storage.

I am testing with the Veritas technican on a vSphere Lab.  So the source of the backup image is not on the same vSphere as the restore of the same backup Image.

We lost a blade with six virtual machines on it and could not restore ANY of them.  All of them running Server 2008 r2 operating system, 4 running SSR 2013 sp2 and 2 running SSR 2013 sp4.  I was testing the software on the machines to see if it conficted with our 3rd party software we run which is critical.  We had to rebuild from scratch all 6 machines.

Any difference between the 2 virtual machines?

Sorry if I am confusing you.  There is only 1 virtual machine I am testing with right now with the Veritas Technician.  I backed up the source virtual machine on a different vSphere; then I am trying to restore it to another vSphere using the backup image from the data storage.

If the source and destination virtual machines are configured in the same way (i.e. same storage controllers), then restore anyware should be disabled.

Which volume(s) were backed up? Just volume C?

Another option is to do a P2V (physical to virtual conversion). I know the source machine was virtual but SSR actually 'sees' it as physical (it does not care). A P2V would convert the image (v2i) to VMDK format (upload directly to ESXi). May be something worth trying here.

For your current testing, is the source server still available?

Yes the source and destination configured the same way and same storage controllers.  We tried to restore with restore anyware disabled.  We are trying to get Veritas to help figure out why they will not restore. 

We do not want to P2V to get this work.  We want the backup images to work with the restore.  We have over 400 machines at this location and we pay for SSR 2013 on all of them.  We need the backup software to work.

That is why I am working with Veritas to find out what is wrong whether it is our procedure or bug in the software.

We do not want to P2V to get this work.  We want the backup images to work with the restore. 

Yes, I understand that. I was not sure how critical this was - I was just offering you a potential workaround.

Is ths source machine still available?