Go Premium for a chance to win a PS4. Enter to Win

x
?
Solved

Barracuda Yosemite Backup failing on a Windows SBS2008 server.

Posted on 2013-10-29
4
Medium Priority
?
1,700 Views
Last Modified: 2013-12-06
We have a single windows sbs2008 server running Barracuda Yosemite Backup software. The backup is not taking place. The log shows 0 files processed.

On investigating the backup job shows Error 5087 - "Snapshot failed with critical timeout"

Yosemite support tell me that we have a problem with our VSS writer, and on checking I notice several errors when detailing the writer status, as follows :-

vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2005 Microsoft Corp.

Writer name: 'FRS Writer'
   Writer Id: {d76f5a28-3092-4589-ba48-2958fb88ce29}
   Writer Instance Id: {adc2ecb9-7d77-46e4-a618-f9c876b2ece1}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'SqlServerWriter'
   Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
   Writer Instance Id: {ddd280f1-637f-4b77-a502-7246ec81aebc}
   State: [1] Stable
   Last error: No error

Writer name: 'System Writer'
   Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
   Writer Instance Id: {4fb47292-3a81-4239-baf3-4e31a9b8de0d}
   State: [1] Stable
   Last error: No error

Writer name: 'ASR Writer'
   Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
   Writer Instance Id: {a44b5182-7869-44a3-b0c5-0a498ee65fd9}
   State: [9] Failed
   Last error: Timed out

Writer name: 'FSRM Writer'
   Writer Id: {12ce4370-5bb7-4c58-a76a-e5d5097e3674}
   Writer Instance Id: {6a4b148e-5890-42b9-b245-5258ffcb8a4e}
   State: [9] Failed
   Last error: Timed out

Writer name: 'Certificate Authority'
   Writer Id: {6f5b15b5-da24-4d88-b737-63063e3a1f86}
   Writer Instance Id: {7320fbbe-eae0-48e1-95b4-9843abc36d17}
   State: [1] Stable
   Last error: No error

Writer name: 'IIS Config Writer'
   Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
   Writer Instance Id: {d0ae6d73-7c8b-42ad-b8d9-279a177e8497}
   State: [1] Stable
   Last error: No error

Writer name: 'Microsoft Exchange Writer'
   Writer Id: {76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}
   Writer Instance Id: {b0bd335e-d7da-4099-9e6a-e3d96cd907fc}
   State: [1] Stable
   Last error: No error

Writer name: 'WMI Writer'
   Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
   Writer Instance Id: {aa726ec4-2188-4065-bb7d-bacbb02e9e3a}
   State: [1] Stable
   Last error: No error

Writer name: 'Shadow Copy Optimization Writer'
   Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
   Writer Instance Id: {b62e3681-4596-43b3-a741-9e050c4edaf4}
   State: [9] Failed
   Last error: Timed out

Writer name: 'BITS Writer'
   Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
   Writer Instance Id: {b1d5c282-38c2-4536-82ae-ef740d0a1634}
   State: [1] Stable
   Last error: No error

Writer name: 'COM+ REGDB Writer'
   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
   Writer Instance Id: {1d1c3e08-c560-42aa-81f4-ebd46643eda5}
   State: [9] Failed
   Last error: Timed out

Writer name: 'Registry Writer'
   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
   Writer Instance Id: {9671be87-6ae8-4b01-a676-422e506d0c1b}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'IIS Metabase Writer'
   Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
   Writer Instance Id: {87f5ac48-65d7-47f3-bc04-616475331034}
   State: [1] Stable
   Last error: No error

Writer name: 'Dhcp Jet Writer'
   Writer Id: {be9ac81e-3619-421f-920f-4c6fea9e93ad}
   Writer Instance Id: {0da2b0c8-ad2a-42cd-8674-4637f5c1dd65}
   State: [1] Stable
   Last error: No error

Writer name: 'NPS VSS Writer'
   Writer Id: {35e81631-13e1-48db-97fc-d5bc721bb18a}
   Writer Instance Id: {aa293b5c-2294-4128-9436-3875747b1949}
   State: [1] Stable
   Last error: No error

Writer name: 'NTDS'
   Writer Id: {b2014c9e-8711-4c5c-a5a9-3cf384484757}
   Writer Instance Id: {3b88fec4-07df-40bb-9400-d0ef273f3c46}
   State: [1] Stable
   Last error: No error

When I reset the server, it seems to clear the writer errors, but our backup again fails, and on checking the writer status the errors have returned.

The thing I am unsure about is --- is it the yosemite software causing this problem, or the problem with our writers that causes the backup to fail, as Yosemite seem to be advising me is the case.

Either way, I am still having problems.

Any ideas??

Many thanks.
0
Comment
Question by:nigelbeatson
  • 2
4 Comments
 
LVL 17

Accepted Solution

by:
WORKS2011 earned 2000 total points
ID: 39609483
When I used Acronis VSS writers constantly failed, the only way I could get it to work was remove the product, in your case Barracuda, clean all traces of it from the registry, restart the system, and reinstall for it to work.
0
 

Expert Comment

by:snake454
ID: 39661579
Hello!

I have been battling this exact same issue for almost two years.  I have to constantly "massage" the failed backups by restarting the server, (SBS 2011 Standard).  

While I have had very favorable experience with Yosemite Server Backup on other servers, this particular install was turning me in to a hater.

Same 5087 errors...same line from Yosemite Support, that the VSS Writers were jacked up and that I needed to call Microsoft.

Never thought about a complete\clean uninstall.  Thank you, I'll give it a go and report back in the next several days.  Thank you!!

Here is my log:

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Windows\system32>vssadmin list writers
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2005 Microsoft Corp.

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: 'System Writer'
   Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
   Writer Instance Id: {31b240f7-9afe-434c-848c-b064e181d864}
   State: [1] Stable
   Last error: No error

Writer name: 'ASR Writer'
   Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
   Writer Instance Id: {5f66dcb8-84c9-416e-83fd-ac9f7bf4cb72}
   State: [9] Failed
   Last error: Timed out

Writer name: 'FRS Writer'
   Writer Id: {d76f5a28-3092-4589-ba48-2958fb88ce29}
   Writer Instance Id: {5170d9c2-101a-4c8a-95ff-900631f3c5f5}
   State: [9] Failed
   Last error: Timed out

Writer name: 'SqlServerWriter'
   Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
   Writer Instance Id: {d6385efe-1b23-4a82-826a-67b209fc855c}
   State: [1] Stable
   Last error: No error

Writer name: 'SharePoint Services Writer'
   Writer Id: {da452614-4858-5e53-a512-38aab25c61ad}
   Writer Instance Id: {c23431d6-51d5-41a1-976a-d05d62ebdceb}
   State: [1] Stable
   Last error: No error

Writer name: 'TS Gateway Writer'
   Writer Id: {368753ec-572e-4fc7-b4b9-ccd9bdc624cb}
   Writer Instance Id: {3891852a-b040-42d3-9c4b-30415c299173}
   State: [1] Stable
   Last error: No error

Writer name: 'FSRM Writer'
   Writer Id: {12ce4370-5bb7-4c58-a76a-e5d5097e3674}
   Writer Instance Id: {74fee2da-0c2f-409d-9fd7-2723082b4724}
   State: [9] Failed
   Last error: Timed out

Writer name: 'COM+ REGDB Writer'
   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
   Writer Instance Id: {94dcc5cf-d4c1-4958-b88e-8f92c7a45e44}
   State: [9] Failed
   Last error: Timed out

Writer name: 'Microsoft Exchange Writer'
   Writer Id: {76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}
   Writer Instance Id: {c4ade82c-05bd-4fdd-8882-b31e70446655}
   State: [9] Failed
  Last error: Timed out

Writer name: 'Registry Writer'
   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
   Writer Instance Id: {d5272b6b-c26e-4d04-8dc5-50487e7b7bc0}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'IIS Config Writer'
   Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
   Writer Instance Id: {b9d4b0af-1a27-4b40-a42c-14d3ad10b1c2}
   State: [1] Stable
   Last error: No error

Writer name: 'Certificate Authority'
   Writer Id: {6f5b15b5-da24-4d88-b737-63063e3a1f86}
   Writer Instance Id: {96fdfa00-8303-44c8-9271-0cdf7152e08a}
   State: [1] Stable
   Last error: No error

Writer name: 'MSSearch Service Writer'
   Writer Id: {cd3f2362-8bef-46c7-9181-d62844cdc0b2}
   Writer Instance Id: {9d7acd28-7387-4411-a116-f0025d94acd3}
   State: [1] Stable
   Last error: No error

Writer name: 'NPS VSS Writer'
   Writer Id: {35e81631-13e1-48db-97fc-d5bc721bb18a}
   Writer Instance Id: {71e0aa63-1201-4c00-a84b-0ff1abac3fe6}
   State: [1] Stable
   Last error: No error

Writer name: 'SPSearch4 VSS Writer'
   Writer Id: {35500004-0201-0000-0000-000000000000}
   Writer Instance Id: {e856e9e3-1bfb-43ea-aeeb-4d6ede174415}
   State: [1] Stable
   Last error: No error

Writer name: 'Dhcp Jet Writer'
   Writer Id: {be9ac81e-3619-421f-920f-4c6fea9e93ad}
   Writer Instance Id: {f21753d2-b1c0-4117-9554-2e19ef407667}
   State: [1] Stable
   Last error: No error

Writer name: 'WMI Writer'
   Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
   Writer Instance Id: {732826c7-9e7a-4a31-9c00-b9b6bc6184b8}
   State: [1] Stable
   Last error: No error

Writer name: 'BITS Writer'
   Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
   Writer Instance Id: {24a3b14c-4a58-4dd0-bf63-9f9ab6ea6bee}
   State: [1] Stable
   Last error: No error

Writer name: 'IIS Metabase Writer'
   Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
   Writer Instance Id: {cb5bff35-7210-4795-838e-f7508d165074}
   State: [1] Stable
   Last error: No error

Writer name: 'NTDS'
   Writer Id: {b2014c9e-8711-4c5c-a5a9-3cf384484757}
   Writer Instance Id: {609dafe5-a2ca-4250-809a-52bbb760d2ab}
   State: [1] Stable
   Last error: No error

Writer name: 'Shadow Copy Optimization Writer'
   Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
   Writer Instance Id: {bddb9716-d9f8-491d-9454-a04f4ccb3a0c}
   State: [9] Failed
   Last error: Timed out


C:\Windows\system32>
0
 

Author Closing Comment

by:nigelbeatson
ID: 39677369
This resolved it - Thanks.
0
 

Expert Comment

by:snake454
ID: 39702054
For the record, a complete uninstall\reinstall of Yosemite Server BU did not fix my issue.  5087 errors still occur.  Not on every BU job, but I would estimate that 40-50 % of my jobs still fail with the 5087 error.
0

Featured Post

Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Question has a verified solution.

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

The problem of the system drive in SBS 2003 getting full continues to be an issue, even though SBS 2008 and SBS 2011 are both in the market place.  There are several solutions to this, including adding additional drive space or using third party uti…
You may have discovered the 'Compatibility View Settings' workaround for making your SBS 2008 Remote Web Workplace 'connect to a computer' section stops 'working around' after a Windows 10 client upgrade.  That can be fixed so it 'works around' agai…
Integration Management Part 2
Exchange organizations may use the Journaling Agent of the Transport Service to archive messages going through Exchange. However, if the Transport Service is integrated with some email content management application (such as an anti-spam), the admin…
Suggested Courses

885 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