Forum Discussion

Lavee383's avatar
Lavee383
Level 4
11 years ago

Snapshot technology Initiation failure on 2012R2 VM

Just started getting this error recently on a new VM I created in my Server 2012 Standard Hyper-V.  The VM is Server 2012R2 Standard.  I have another VM that is 2012R2 and I don't have any issues with it.  I have updated the integration services.  Here's the error:

Job ended: Sunday, March 16, 2014 at 10:37:35 PM Completed status: Failed Final error: 0xe000fed1 - A failure occurred querying the Writer status. See the job log for details about the error. Final error category: Resource Errors For additional information regarding this error refer to link V-79-57344-65233

Backup- HYPR-03.domain.local
V-79-57344-65233 - Snapshot Technology: Initialization failure on: "VRTSRV::\\HYPR-03.domain.local\Hyper-V?Virtual?Machine\OME-01".  Snapshot technology used: Microsoft Volume Shadow Copy Service (VSS).

Snapshot technology error (0xE000FED1): A failure occurred querying the Writer status. See the job log for details about the error.

Check the Windows Event Viewer for details.

Writer Name: Microsoft Hyper-V, Writer ID: {66841CD4-6DED-4F4B-8F17-FD23F8DDC3DE}, Last error: The VSS Writer failed, but the operation can be retried (0x800423f3), State: Failed during prepare snapshot operation (8).

Any help on why this is happening is greatly appreciated.

Thanks!

  • Never mind I actually found my answer via Spiceworks...this is CRAZY!!!  SBE 2012 R2 won't be released until 3rd Q?!?!  That's a FULL YEAR after the OS is released!  Terrible...just absolutely terrible.

    https://www-secure.symantec.com/connect/blogs/backup-exec-2012-r2-update-news-about-windows-server-2012-r2-support-and-target-ga

    Windows Server 2012 R2 support: Backup Exec 2012 R2 will include agent and media server support for Windows Server 2012 R2. This is a significant undertaking by our engineering team, but we are committed to delivering timely support. I know that many of you are asking for this support now, and we are doing everything we can to get to where you want us to be. I know many of you are frustrated and I apologize, please know that our #1 priority is to deliver timely platform support. We have put a structure in place to solve this issue so that we can return to being the first to offer support for new platforms.

    Backup Exec 2012 R2 timing: We are targeting general availability (GA) between late in the 2nd quarter or early in the 3rd quarter of 2014 (calendar year).  We have achieved our feature code complete milestone and are quickly approaching our Beta 1 milestone.

  • I was under the impression that the latest service pack was supposed to include support for 2012R2.  If that's not the case, what's the date for the next release that DOES support R2?!?!  I'm in the process of upgrading all my 2012 servers to 2012R2 and this is a major issue if there isn't support for R2.

  • Never mind I actually found my answer via Spiceworks...this is CRAZY!!!  SBE 2012 R2 won't be released until 3rd Q?!?!  That's a FULL YEAR after the OS is released!  Terrible...just absolutely terrible.

    https://www-secure.symantec.com/connect/blogs/backup-exec-2012-r2-update-news-about-windows-server-2012-r2-support-and-target-ga

    Windows Server 2012 R2 support: Backup Exec 2012 R2 will include agent and media server support for Windows Server 2012 R2. This is a significant undertaking by our engineering team, but we are committed to delivering timely support. I know that many of you are asking for this support now, and we are doing everything we can to get to where you want us to be. I know many of you are frustrated and I apologize, please know that our #1 priority is to deliver timely platform support. We have put a structure in place to solve this issue so that we can return to being the first to offer support for new platforms.

    Backup Exec 2012 R2 timing: We are targeting general availability (GA) between late in the 2nd quarter or early in the 3rd quarter of 2014 (calendar year).  We have achieved our feature code complete milestone and are quickly approaching our Beta 1 milestone.