D
DoJu
G'day to the Microsoft technet forums!
Despite taking several steps below to resolve, I still have no resolution to this issue.
Any hints or tips most appreciated.
Steve
SUMMARY
VMWare Guest running Windows Server 2012 R2 Fully patched
C: OS disk capacity is 40Gb, Free space 20Gb
16Gb RAM, 10Gb Free
VMWARE Tools 10.0.6.3560309
VMware Snapshot Provider
Troubleshooting steps taken:
1) vssadmin list writers returns
Writer name: 'System Writer' State: [7] Failed Last error: Timed out
Writer name: 'IIS Config Writer' State: [7] Failed Last error: Timed out
Writer name: 'WMI Writer'State: [7] Failed Last error: Timed out
Writer name: 'IIS Metabase Writer' [7] Failed Last error: Timed out
Restarted each service that corresponds to each timed-out VSS writer (which then changed state to “No Errors”)
How to Manually Restart all VSS Writers when in a Failed State without Rebooting (129774)
How to Manually Restart all VSS Writers when in a Failed State without Rebooting (129774)
VM rebooted
Result: VMWARE VSS snapshot still failed.
2) There WAS a ghosted "generic volume shadow copy" under Storage volume shadow copies" in device manager.
This ghosted object has been uninstalled.
VM rebooted
Result: VSS snapshot still failed.
3) According to Microsoft, the VSS writer timeout issue occurs "during times when there are high levels of input/output" ie. Backups. However, VSS snapshot issue occurs even during 'quite periods'
https://support.microsoft.com/en-us...volume-shadow-copy-service-writers-and-shadow
As recommended by Microsoft, I have added the DWORD MinDiffAreaFileSize registry key and specified 900Mb as the minimum size of the shadow copy storage area.
4) Changed storage area, max size shadow copy 'no limit'
5) Added NETWORK SERVICE with local access to My Computer / COM Security / Access Permissions / Edit Default in DCOMCNFG.exe
System Administrator Recipes: Event Id: 8193 Vss Error in Windows Server 2008 R2
What I haven't done:
Using Tracing Tools with VSS
Using Tracing Tools with VSS
Event ID 8193
Volume Shadow Copy Service error: Unexpected error calling routine IOCTL_DISK_SET_SNAPSHOT_INFO(\\.\PHYSICALDRIVE0) fails with winerror 1168. hr = 0x80070490, Element not found.
Operation:
Processing AbortSnapshots
Executing Asynchronous Operation
Context:
Device: \\.\PHYSICALDRIVE0
Provider Name: VMware Snapshot Provider
Provider Version: 1.0.0
Provider ID: {564d7761-7265-2056-5353-2050726f7669}
Current State: DoSnapshotSet
Event ID 8193 VSS
Volume Shadow Copy Service error: Unexpected error calling routine IOCTL_DISK_SET_SNAPSHOT_INFO(\\.\PHYSICALDRIVE0) fails with winerror 1168. hr = 0x80070490, Element not found.
.
Operation:
Processing EndPrepareSnapshots
Executing Asynchronous Operation
Context:
Provider Name: VMware Snapshot Provider
Provider Version: 1.0.0
Provider ID: {564d7761-7265-2056-5353-2050726f7669}
Current State: DoSnapshotSet
Continue reading...
Despite taking several steps below to resolve, I still have no resolution to this issue.
Any hints or tips most appreciated.
Steve
SUMMARY
VMWare Guest running Windows Server 2012 R2 Fully patched
C: OS disk capacity is 40Gb, Free space 20Gb
16Gb RAM, 10Gb Free
VMWARE Tools 10.0.6.3560309
VMware Snapshot Provider
Troubleshooting steps taken:
1) vssadmin list writers returns
Writer name: 'System Writer' State: [7] Failed Last error: Timed out
Writer name: 'IIS Config Writer' State: [7] Failed Last error: Timed out
Writer name: 'WMI Writer'State: [7] Failed Last error: Timed out
Writer name: 'IIS Metabase Writer' [7] Failed Last error: Timed out
Restarted each service that corresponds to each timed-out VSS writer (which then changed state to “No Errors”)
How to Manually Restart all VSS Writers when in a Failed State without Rebooting (129774)
How to Manually Restart all VSS Writers when in a Failed State without Rebooting (129774)
VM rebooted
Result: VMWARE VSS snapshot still failed.
2) There WAS a ghosted "generic volume shadow copy" under Storage volume shadow copies" in device manager.
This ghosted object has been uninstalled.
VM rebooted
Result: VSS snapshot still failed.
3) According to Microsoft, the VSS writer timeout issue occurs "during times when there are high levels of input/output" ie. Backups. However, VSS snapshot issue occurs even during 'quite periods'
https://support.microsoft.com/en-us...volume-shadow-copy-service-writers-and-shadow
As recommended by Microsoft, I have added the DWORD MinDiffAreaFileSize registry key and specified 900Mb as the minimum size of the shadow copy storage area.
4) Changed storage area, max size shadow copy 'no limit'
5) Added NETWORK SERVICE with local access to My Computer / COM Security / Access Permissions / Edit Default in DCOMCNFG.exe
System Administrator Recipes: Event Id: 8193 Vss Error in Windows Server 2008 R2
What I haven't done:
Using Tracing Tools with VSS
Using Tracing Tools with VSS
Event ID 8193
Volume Shadow Copy Service error: Unexpected error calling routine IOCTL_DISK_SET_SNAPSHOT_INFO(\\.\PHYSICALDRIVE0) fails with winerror 1168. hr = 0x80070490, Element not found.
Operation:
Processing AbortSnapshots
Executing Asynchronous Operation
Context:
Device: \\.\PHYSICALDRIVE0
Provider Name: VMware Snapshot Provider
Provider Version: 1.0.0
Provider ID: {564d7761-7265-2056-5353-2050726f7669}
Current State: DoSnapshotSet
Event ID 8193 VSS
Volume Shadow Copy Service error: Unexpected error calling routine IOCTL_DISK_SET_SNAPSHOT_INFO(\\.\PHYSICALDRIVE0) fails with winerror 1168. hr = 0x80070490, Element not found.
.
Operation:
Processing EndPrepareSnapshots
Executing Asynchronous Operation
Context:
Provider Name: VMware Snapshot Provider
Provider Version: 1.0.0
Provider ID: {564d7761-7265-2056-5353-2050726f7669}
Current State: DoSnapshotSet
Continue reading...