Gents/Ladies,
I couldn't find a "server" area for support, so here goes:
Server 2012 R2, Fresh install, fully updated.
MS server backup fails - Event log:
The backup operation that started at '2014-06-03T17:22:37.387000000Z' has failed because the Volume Shadow Copy Service operation to create a shadow copy of the volumes being backed up failed with following error code '0x8078006B'. Please review the event details for a solution, and then rerun the backup operation once the issue is resolved.
Other VSS related events
XXXXXXXXXXXXXXXXXXXXX
Volume Shadow Copy Service error: Unexpected error DeviceIoControl(\\?\Volume{643142df-1a81-416b-aaf8-732f062f4764} - 0000000000000258,0x0053c008,0000000233EA10E0,0,0000000233EA3100,4096,[0]). hr = 0x80070001, Incorrect function.
.
Operation:
Processing EndPrepareSnapshots
Context:
Execution Context: System Provider
XXXXXXXXXXXXXXXXXXXXXX
Volume Shadow Copy Service error: Unexpected error DeviceIoControl(\\?\Volume{fdb18256-e7bf-11e3-80b1-806e6f6e6963} - 000000000000013C,0x0053c008,0000000233EA10E0,0,0000000233EA5120,4096,[0]). hr = 0x80070001, Incorrect function.
.
Operation:
Processing EndPrepareSnapshots
Context:
Execution Context: System Provider
XXXXXXXXXXXXXXXXXXXXXXX\
C:\Users\Administrator>vssadmin list writers
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line too
(C) Copyright 2001-2013 Microsoft Corp.
Writer name: 'Task Scheduler Writer'
Writer Id: {d61d61c8-d73a-4eee-8cdd-f6f9786b7124}
Writer Instance Id: {1bddd48e-5052-49db-9b07-b96f96727e6b}
State: [1] Stable
Last error: No error
Writer name: 'VSS Metadata Store Writer'
Writer Id: {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06}
Writer Instance Id: {088e7a7d-09a8-4cc6-a609-ad90e75ddc93}
State: [1] Stable
Last error: No error
Writer name: 'Performance Counters Writer'
Writer Id: {0bada1de-01a9-4625-8278-69e735f39dd2}
Writer Instance Id: {f0086dda-9efc-47c5-8eb6-a944c3d09381}
State: [1] Stable
Last error: No error
Writer name: 'System Writer'
Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
Writer Instance Id: {9fb3a4c8-8cd7-45ce-bbe9-6ce7f8330ab6}
State: [7] Failed
Last error: Timed out
Writer name: 'ASR Writer'
Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
Writer Instance Id: {18697d2b-e1f7-461e-ba87-96aa71ba3d6d}
State: [1] Stable
Last error: No error
Writer name: 'Shadow Copy Optimization Writer'
Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
Writer Instance Id: {279f6402-df98-446a-babf-de4d1c6ef6db}
State: [1] Stable
Last error: No error
Writer name: 'Registry Writer'
Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
Writer Instance Id: {bf6ddbc8-ddee-4173-91d2-cf2c4f44df77}
State: [1] Stable
Last error: No error
Writer name: 'COM+ REGDB Writer'
Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
Writer Instance Id: {f75aefc7-4e14-48c5-88ec-7483f5fcff36}
State: [1] Stable
Last error: No error
Writer name: 'WMI Writer'
Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
Writer Instance Id: {81022bab-4671-47d4-8b49-c981a18a6116}
State: [7] Failed
Last error: Timed out
Writer name: 'IIS Config Writer'
Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
Writer Instance Id: {a50d614b-a032-452d-9e02-111139567f9b}
State: [7] Failed
Last error: Timed out
Writer name: 'DFS Replication service writer'
Writer Id: {2707761b-2324-473d-88eb-eb007a359533}
Writer Instance Id: {a3ca1bf2-d65e-4439-8233-b67261cf6cc2}
State: [7] Failed
Last error: Timed out
Writer name: 'Dhcp Jet Writer'
Writer Id: {be9ac81e-3619-421f-920f-4c6fea9e93ad}
Writer Instance Id: {578befe2-31ed-4bbe-a6e1-cca193c0ceab}
State: [7] Failed
Last error: Timed out
Writer name: 'WINS Jet Writer'
Writer Id: {f08c1483-8407-4a26-8c26-6c267a629741}
Writer Instance Id: {4c4d2183-af48-4783-84bd-e75edfcd0de4}
State: [7] Failed
Last error: Timed out
Writer name: 'NTDS'
Writer Id: {b2014c9e-8711-4c5c-a5a9-3cf384484757}
Writer Instance Id: {02840c13-062c-4031-89cf-9a02f6d8889f}
State: [7] Failed
Last error: Timed out
My research on this so far indicates that this issue may be due to the c: drive not being the active partition (server 2012 sets up a 350mb boot manager partition on the first drive that is the active partition) Making the C drive the active partition (from experience), renders the system non-bootable.
Any ideas how to resolve this would be greatly appreciated!!!!!
Thanks, Deek
