Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Windows Server 2012 VSS Snapshot issue

Created: 03 Sep 2013 • Updated: 19 Nov 2013 | 10 comments
This issue has been solved. See solution.

Hello,

We recently added a Windows 2012 Server to our backup and it contain serveral SQL 2012 databases. To make things short I have about three Jobs for this particular server, one job with just the SQL databases with AOFO disable, second I had the OS and the system state, and lastly the third job has the other drives that is on that server which is the D and E drive.

The issue that I am having involves just the third job. The following error message is what I am receiving: 

- Snapshot Technology: Initialization failure on: "Server\E:". Snapshot technology used: Microsoft Volume Shadow Copy Service (VSS).
V-79-10000-11217 - VSS Snapshot error. The Microsoft Volume Shadow Copy Service (VSS) snapshot failed. Make sure that all provider services and tasks are running. Check the Windows Event Viewer for details.
 

Backup
- Snapshot Technology: Initialization failure on: "\Server\D:". Snapshot technology used: Microsoft Volume Shadow Copy Service (VSS).
V-79-10000-11217 - VSS Snapshot error. The Microsoft Volume Shadow Copy Service (VSS) snapshot failed. Make sure that all provider services and tasks are running. Check the Windows Event Viewer for details.

I have checked the forum, but have not found anything remotely close to my issue. I do have AOFO enable for the third job in cause your curious.

Therefore any assistance would be greatly appreicated.

Operating Systems:

Comments 10 CommentsJump to latest comment

marcusolini's picture

Hi.  If you are still experiencing the snapshot failure, when able, please collect the following diagnostic information using the native Windows command line tools and post the information for review.  This diagnostic information is executed on the server that experiencing the snapshot failure.  Thank you.

(1)    C:\>VSSADMIN LIST VOLUMES
(2)    C:\>VSSADMIN LIST WRITERS
(3)    C:\>VSSADMIN LIST PROVIDERS
(4)    C:\>VSSADMIN LIST SHADOWS
(5)    C:\>VSSADMIN LIST SHADOWSTORAGE
(6)    C:\>REG QUERY "HKLM\SYSTEM\CurrentControlSet\Services\VSS"
(7)    C:\>REG QUERY "HKLM\SYSTEM\CurrentControlSet\Services\VSS\Providers" /s
(8)    C:\>REG QUERY "HKLM\SYSTEM\CurrentControlSet\Services\VSS\VssAccessControl" /s
(9)   C:\>REG QUERY "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\SPP" /s
(10)  C:\>REG QUERY "HKLM\SYSTEM\CurrentControlSet\Services\MountMgr" /s
(11)  C:\>REG QUERY "HKLM\SYSTEM\CurrentControlSet\Services\TrueCrypt" /s
(12)  C:\>REG QUERY "HKLM\SYSTEM\CurrentControlSet\control\hivelist" /s
(13)  C:\>VER
(14)  C:\>BCDEDIT /ENUM
(15)  C:\>MOUNTVOL
(16)(a)  C:\>DISKPART
(16)(b)   DISKPART> LIST DISK
(16)(c)   DISKPART> LIST VOLUME
(16)(d)   DISKPART> LIST VDISK
(16)(e)   DISKPART> EXIT
(17) Question: Physical Machine or Virtual Machine?

CraigV's picture

...I'll jump on here although it is a couple of days old. But do you have BE 2012 SP2 installed on the media server, and have these updates been push-installed to your remote servers?

Without SP2 installed, Windows Server 2012 is not supported at all.

Thanks!

Alternative ways to access Backup Exec Technical Support:

https://www-secure.symantec.com/connect/blogs/alte...

Vdang's picture

To my knowledge our BE 2012 has been updated to the latest services verison pack since about 2 weeks ago.

Vdang's picture

Hello Marcusolini,

What are the implications of running the following commands. I just want to make sure I would not affect our production server in a negative way.

(6) C:\>REG QUERY "HKLM\SYSTEM\CurrentControlSet\Services\VSS"
(7) C:\>REG QUERY "HKLM\SYSTEM\CurrentControlSet\Services\VSS\Providers" /s
(8) C:\>REG QUERY "HKLM\SYSTEM\CurrentControlSet\Services\VSS\VssAccessControl" /s
(9) C:\>REG QUERY "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\SPP" /s
(10) C:\>REG QUERY "HKLM\SYSTEM\CurrentControlSet\Services\MountMgr" /s
(11) C:\>REG QUERY "HKLM\SYSTEM\CurrentControlSet\Services\TrueCrypt" /s
(12) C:\>REG QUERY "HKLM\SYSTEM\CurrentControlSet\control\hivelist" /s

marcusolini's picture

Hi.  They are Registry query commands that read the specific registry key and output the results to the command line.  These commands are less intrusive and simpiler than using the Registry application Regedit.exe.  I would not expect any ill effects to the production server.  Hope this helps clarify.

Vdang's picture

Hello Marcusolini,

I have attached the result of what I was able to capture of the following: 1-8, 10,12-15, and 16a-16e which can be seen from the following screen shot.

Capture2.JPG

AttachmentSize
Result.txt 13.22 KB
marcusolini's picture

Hi.  Thank you for collecting all of the diagnostic information.  Based on this information, I suspect that the 'Nimble Storage VSS Provider' VSS Hardware Provider is most likely the cause of your VSS snapshot difficulties.  To work around the possible VSS Hardware Provider difficulty, there are a few solutions listed below.  Please review, evaluate, and perform one of these possible solutions and let me know the outcome.  Hope this proves helpful. Thank you.

(A) From Backup Exec 2012,   Configure the Advanced Open File to use the Microsoft VSS System Provider and disable Checkpoint Restart.  SELECT Advanced Open File – Snapshot Configuration – Microsoft Volume Shadow Copy Server (Windows 2003 and later) – Snapshot provider: -  ‘System – Use Microsoft Software Shadow Copy Provider’.  Also, UNSELECT  ‘Enable checkpoint restart’ (for the  Backup Options and\or Job Defaults).

OR

(B) From the Registry, Configure VSS to always use the Microsoft VSS System Provider.  Create and Set the following Registry value to DWORD 1: ‘HKLM\SYSTEM\CurrentControlSet\Control\BackupRestore\useMicrosoftProvider’.  Note, a reboot is required.

OR

(C) Investigate and correct any issues with the 'Nimble Storage VSS Provider' VSS Hardware Provider.

OR

(D) Disable or Uninstall the 'Nimble Storage VSS Provider' VSS Hardware Provider.

SOLUTION
Vdang's picture

Hello Marcusolini,

I will get back to you as soon as possible with regards to the possible solution you have provided.

Vdang's picture

After I had made the changes using the first option it appears that the jobs are completing successfully without any issues or exeception.. However, what would I like to know is that by making this change, how would it affects future restore jobs for this particular server if any.

marcusolini's picture

Hi.  Great news!  Restore jobs would not be affected because, for Backup Exec, VSS Providers are not involved in restore operations.  Please consider marking this post as solved, so others with a similar issue can perform some self-help diagnostics.  Thank you for all of your assistance!  Glad this proved helpful.