Solved

Hyper-V VM running SQL

Posted on 2011-03-24
11
528 Views
Last Modified: 2012-08-13
We have a VM running SQL2008. Backups are handled by Backup Exec 12.5 with Hyper-V Agent.

We are cannot backup the SQL VM unless the SQL and Agent services are shut down.

Running a backup with these services running generates VSS errors.

Basically, the backup fails during the initial snapshop process.

Thanks
0
Comment
Question by:Gig-A-Dee
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 7
  • 4
11 Comments
 
LVL 10

Expert Comment

by:rscottvan
ID: 35215460
Unless you use the SQL Agent for Backup Exec, you need to backup SQL with a SQL Maintenance Plan to a location that will be backed up later by the Hyper-V agent jobs.  In the Hyper-V agent job, exclude the folder where the live databases are located.
0
 
LVL 1

Author Comment

by:Gig-A-Dee
ID: 35219850
SHouldn't the Hyper-V Agent copy/backup the entire VHD file of the VM?
0
 
LVL 1

Author Comment

by:Gig-A-Dee
ID: 35278114
We do in fact have the Backup Exec agent installed on this VM. This should also support GRT but it still fails and kills the VSS processes on the server.

Thanks
0
NFR key for Veeam Backup for Microsoft Office 365

Veeam is happy to provide a free NFR license (for 1 year, up to 10 users). This license allows for the non‑production use of Veeam Backup for Microsoft Office 365 in your home lab without any feature limitations.

 
LVL 10

Expert Comment

by:rscottvan
ID: 35281169
Can you post the Event Log entries for the VSS errors?
0
 
LVL 1

Author Comment

by:Gig-A-Dee
ID: 35295096
Backup- VRTSRV::\\EDGE-VM1.EDGE.LOCAL\Hyper-V?Store\Initial Store V-79-57344-65233 - AOFO: Initialization failure on: "VRTSRV::\\EDGE-VM1.EDGE.LOCAL\Hyper-V?Virtual?Machine\Edge-SQL". Advanced Open File Option used: Microsoft Volume Shadow Copy Service (VSS).

Snapshot provider error (0xE000FED1): A failure occurred querying the Writer status.

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).

Here's the backup exec log. I will post the app log shortly.

Thanks
0
 
LVL 1

Author Comment

by:Gig-A-Dee
ID: 35295324
There are zero errors in the Windows App log with the exception of the backup failing. No mention of VSS, etc.

Thanks
0
 
LVL 10

Accepted Solution

by:
rscottvan earned 500 total points
ID: 35298621
Have a look at this Symantec article:
http://www.symantec.com/business/support/index?page=content&id=TECH74769

1. Stop the Microsoft Shadow Copy Provider &Volume Shadow Copy Service.

2. Export the contents of the HKLM\Software\Microsoft\EventSystem key to a .regfile.
Warning:Incorrect use of the Windows registry editor may prevent the operating system from functioning properly. Great care should be taken when making changes to a Windows registry. Registry modifications should only be carried-out by persons experienced in the use of the registry editor application. It is recommended that a complete backup of the registry and workstation be made prior to making any registry changes.

3. Delete the HKLM\Software\Microsoft\EventSystem\{26c409cc-ae86-11d1-b616-00805fc79216}\Subscriptions key. (Do not delete the EventClasses key).

4. Restart the server.

5. Run the"VSSADMIN LIST WRITERS" command. (from an elevated command prompt)


This causes the VSS entries in the HKLM\Software\Microsoft\EventSystem\{26c409cc-ae86-11d1-b616-00805fc79216}\Subscriptions key to be rebuilt when the writers initialize.
0
 
LVL 1

Author Comment

by:Gig-A-Dee
ID: 35361888
Performed the above procedure.

Please see attached screenshot.

Rescue--87667036-2011-04-10-10h5.jpg
0
 
LVL 10

Expert Comment

by:rscottvan
ID: 35366712
I'll have to check the service history for our system when I get to the office in a couple hours - we had exactly the same issue...  it may have simply been upgrading to R2 and upgrading the agent on the SQL server that ultimately fixed this for us.
0
 
LVL 1

Author Comment

by:Gig-A-Dee
ID: 35368151
Fingers crossed!!!!!!!

Thanks
0
 
LVL 1

Author Closing Comment

by:Gig-A-Dee
ID: 36410991
Thanks
0

Featured Post

Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Scenario:  You do full backups to a internal hard drive in either product (SBS or Server 2008).  All goes well for a very long time.  One day, backups begin to fail with a message that the disk is full.  Your disk contains many, many more backups th…
Nowadays, Virtual Machines are used equally by small and large scale organizations. However the issue is that VMDK files are also prone to corruption. So, in this article we are looking at how to recover VMDK files from hard disk of host operating s…
This tutorial will walk an individual through the steps necessary to join and promote the first Windows Server 2012 domain controller into an Active Directory environment running on Windows Server 2008. Determine the location of the FSMO roles by lo…
This Micro Tutorial hows how you can integrate  Mac OSX to a Windows Active Directory Domain. Apple has made it easy to allow users to bind their macs to a windows domain with relative ease. The following video show how to bind OSX Mavericks to …

733 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question