Win server 2012R2 - server backup - failed

scottjnorris
scottjnorris used Ask the Experts™
on
Not sure what to do here ...

The backup operation that started at '?2016?-?02?-?11T07:01:14.778000000Z' 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 '0x807800A1'. Please review the event details for a solution, and then rerun the backup operation once the issue is resolved.

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
  <Provider Name="Microsoft-Windows-Backup" Guid="{1DB28F2E-8F80-4027-8C5A-A11F7F10F62D}" />
  <EventID>9</EventID>
  <Version>2</Version>
  <Level>2</Level>
  <Task>0</Task>
  <Opcode>0</Opcode>
  <Keywords>0x4000000000000000</Keywords>
  <TimeCreated SystemTime="2016-02-11T07:40:24.603414500Z" />
  <EventRecordID>2329</EventRecordID>
  <Correlation />
  <Execution ProcessID="18092" ThreadID="13840" />
  <Channel>Microsoft-Windows-Backup</Channel>
  <Computer>Server.rrtna.local</Computer>
  <Security UserID="S-1-5-18" />
  </System>
- <EventData>
  <Data Name="BackupStartTime">2016-02-11T07:01:14.778000000Z</Data>
  <Data Name="BackupSetId">{1595F3BF-B196-4D0E-9007-49FCBB18424B}</Data>
  <Data Name="HRESULT">0x807800a1</Data>
  </EventData>
  </Event>

Any help appreciated.
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
From a command prompt do a vssadmin list writers and post results.

Author

Commented:
Waiting for responses.
These may be delayed if a shadow copy is being prepared.

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: 'ASR Writer'
   Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
   Writer Instance Id: {424029df-c1d2-484f-a352-abc55e5fc30f}
   State: [1] Stable
   Last error: No error

Writer name: 'System Writer'
   Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
   Writer Instance Id: {3f236810-4a37-4118-92ad-363fd025ac71}
   State: [1] Stable
   Last error: No error

Writer name: 'Microsoft Hyper-V VSS Writer'
   Writer Id: {66841cd4-6ded-4f4b-8f17-fd23f8ddc3de}
   Writer Instance Id: {23c51b96-19e1-47a6-9206-5485a9f998ad}
   State: [1] Stable
   Last error: Unexpected error

Writer name: 'Shadow Copy Optimization Writer'
   Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
   Writer Instance Id: {b792b408-b0af-458f-be2d-44cc974fc955}
   State: [1] Stable
   Last error: No error

Writer name: 'IIS Config Writer'
   Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
   Writer Instance Id: {da31fdaf-5b8c-4f9c-9b7f-8fb6d7da20ce}
   State: [1] Stable
   Last error: No error

Writer name: 'Registry Writer'
   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
   Writer Instance Id: {edbddcd6-ea9e-4b5a-ae8f-7f6c74fbc549}
   State: [1] Stable
   Last error: No error

Writer name: 'BITS Writer'
   Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
   Writer Instance Id: {f9e0790f-6c1d-4b0c-bd1b-d1c5b6b79237}
   State: [1] Stable
   Last error: No error

Writer name: 'Dhcp Jet Writer'
   Writer Id: {be9ac81e-3619-421f-920f-4c6fea9e93ad}
   Writer Instance Id: {da050ce3-4c8e-4540-8f7f-ac3836eaa9f5}
   State: [1] Stable
   Last error: No error

Writer name: 'COM+ REGDB Writer'
   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
   Writer Instance Id: {89571c0c-d22c-4849-ba33-c501f7d29ecd}
   State: [1] Stable
   Last error: No error

Writer name: 'FRS Writer'
   Writer Id: {d76f5a28-3092-4589-ba48-2958fb88ce29}
   Writer Instance Id: {2f8aaf61-f516-4971-8aef-bd1f81d2e8a7}
   State: [1] Stable
   Last error: No error

Writer name: 'WMI Writer'
   Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
   Writer Instance Id: {2f0c450e-863d-44a1-8758-dc23ffe00156}
   State: [1] Stable
   Last error: No error

Writer name: 'NTDS'
   Writer Id: {b2014c9e-8711-4c5c-a5a9-3cf384484757}
   Writer Instance Id: {fd60406c-71a3-4d06-9a6a-51972b1c7126}
   State: [1] Stable
   Last error: No error


C:\Windows\system32>
Are you running more than one backup program?
Ensure you’re charging the right price for your IT

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden using our free interactive tool and use it to determine the right price for your IT services. Start calculating Now!

Author

Commented:
This server is configured to run "LogMeIn Backup" and "windows server backup" on a schedule.
Sounds like a conflict.
Can you run a manual backup to test?

Author

Commented:
Good idea I will disable the LogMeIn Services. and run a manual backup of windows back-up over the weekend.

Author

Commented:
disabling LMI and rerunning win backup worked
thanks

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial