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

V-79-57344-34086

Created: 04 Nov 2013 • Updated: 15 Nov 2013 | 5 comments
This issue has been solved. See solution.

Hi, we're having a problem with our Volume Shadow Copy Service and backup exec is failing every night.  Below are the errors from the latest job, event log doesn't seem to give much more info, any ideas what I need to look at here?

 

V-79-57344-34086 - Snapshot Technology: Initialization failure on: "System?State". Snapshot technology used: Microsoft Volume Shadow Copy Service (VSS).
Snapshot technology error (0xE0008526): Backup Exec could not locate a Microsoft Volume Shadow Copy Services (VSS) software or hardware snapshot technology for this job. Select a valid VSS snapshot technology for the target computer.

Check the Windows Event Viewer for details.

 

 

Backup- [servername].[domain].localV-79-57344-34086 - Snapshot Technology: Initialization failure on: "Microsoft Information Store". Snapshot technology used: Microsoft Volume Shadow Copy Service (VSS).

Snapshot technology error (0xE0008526): Backup Exec could not locate a Microsoft Volume Shadow Copy Services (VSS) software or hardware snapshot technology for this job. Select a valid VSS snapshot technology for the target computer.

Check the Windows Event Viewer for details.

V-79-57344-34086 - Snapshot Technology: Initialization failure on: "Microsoft Information Store". Snapshot technology used: Microsoft Volume Shadow Copy Service (VSS).

Snapshot technology error (0xE0008526): Backup Exec could not locate a Microsoft Volume Shadow Copy Services (VSS) software or hardware snapshot technology for this job. Select a valid VSS snapshot technology for the target computer.

Check the Windows Event Viewer for details.

BackupV-79-57344-34086 - Snapshot Technology: Initialization failure on: "System?State". Snapshot technology used: Microsoft Volume Shadow Copy Service (VSS).

Snapshot technology error (0xE0008526): Backup Exec could not locate a Microsoft Volume Shadow Copy Services (VSS) software or hardware snapshot technology for this job. Select a valid VSS snapshot technology for the target computer.

Check the Windows Event Viewer for details.

V-79-57344-34086 - Snapshot Technology: Initialization failure on: "Search instance\Index files 1 ([servername]\e6bbaecc-8490-44eb-ad77-d75e9385fb43)". Snapshot technology used: Microsoft Volume Shadow Copy Service (VSS).

Snapshot technology error (0xE0008526): Backup Exec could not locate a Microsoft Volume Shadow Copy Services (VSS) software or hardware snapshot technology for this job. Select a valid VSS snapshot technology for the target computer.

Check the Windows Event Viewer for details.

V-79-57344-34086 - Snapshot Technology: Initialization failure on: "Search instance\Search-DB 1 ([servername]\SHAREPOINT\WSS_Search_[servername])". Snapshot technology used: Microsoft Volume Shadow Copy Service (VSS).

Snapshot technology error (0xE0008526): Backup Exec could not locate a Microsoft Volume Shadow Copy Services (VSS) software or hardware snapshot technology for this job. Select a valid VSS snapshot technology for the target computer.

Check the Windows Event Viewer for details.

Operating Systems:

Comments 5 CommentsJump to latest comment

Colin Weaver's picture

When a backup job is NOT running, run VSSADMIN LIST WRITERS  on the server being backed up and if any of them are not in a stable state then fix that first (reboot may be needed)

IA_Alan_Lamb's picture

They all seem to be fine.

vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2005 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: {de62895c-411d-4849-b8ea-b8826bd58061}
State: [1] Stable
Last error: No error

Writer name: 'SqlServerWriter'
Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
Writer Instance Id: {3811e07e-588e-4908-96b3-c66d8cfa07c5}
State: [1] Stable
Last error: No error

Writer name: 'SharePoint Services Writer'
Writer Id: {da452614-4858-5e53-a512-38aab25c61ad}
Writer Instance Id: {965a76a6-4df1-48fb-a923-359a34ee150f}
State: [1] Stable
Last error: No error

Writer name: 'FRS Writer'
Writer Id: {d76f5a28-3092-4589-ba48-2958fb88ce29}
Writer Instance Id: {650cbc33-48c6-494b-b29a-1b27dff5e30e}
State: [1] Stable
Last error: No error

Writer name: 'ASR Writer'
Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
Writer Instance Id: {ec8a2430-8643-42d4-b9d0-261d837ffde3}
State: [1] Stable
Last error: No error

Writer name: 'MSSearch Service Writer'
Writer Id: {cd3f2362-8bef-46c7-9181-d62844cdc0b2}
Writer Instance Id: {379d10da-c133-4b72-a8fd-6dd4b1c93f4d}
State: [1] Stable
Last error: No error

Writer name: 'FSRM Writer'
Writer Id: {12ce4370-5bb7-4c58-a76a-e5d5097e3674}
Writer Instance Id: {0756d936-dce2-4ba7-ae6a-2538d502cfa5}
State: [1] Stable
Last error: No error

Writer name: 'WMI Writer'
Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
Writer Instance Id: {1bfc9b6f-2f9a-4d7c-9d22-809438f0c42b}
State: [1] Stable
Last error: No error

Writer name: 'IIS Config Writer'
Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
Writer Instance Id: {6e23e976-6338-411c-acab-9026e6ff6791}
State: [1] Stable
Last error: No error

Writer name: 'Microsoft Exchange Writer'
Writer Id: {76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}
Writer Instance Id: {02b1ccae-8ce7-478f-9a4f-b2dec23ef673}
State: [1] Stable
Last error: No error

Writer name: 'Dhcp Jet Writer'
Writer Id: {be9ac81e-3619-421f-920f-4c6fea9e93ad}
Writer Instance Id: {640cb947-f4fd-4563-bc5b-ebb8c8acbc56}
State: [1] Stable
Last error: No error

Writer name: 'Shadow Copy Optimization Writer'
Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
Writer Instance Id: {f3a34b3f-6c6b-4609-ab4f-cae55e54e8f2}
State: [1] Stable
Last error: No error

Writer name: 'BITS Writer'
Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
Writer Instance Id: {227cc280-4146-4e56-96a7-d5e78bfa6569}
State: [1] Stable
Last error: No error

Writer name: 'SPSearch4 VSS Writer'
Writer Id: {35500004-0201-0000-0000-000000000000}
Writer Instance Id: {7475fae0-346f-4840-93a6-85a503aef1d8}
State: [1] Stable
Last error: No error

Writer name: 'COM+ REGDB Writer'
Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
Writer Instance Id: {03706690-44a6-4bd8-b5fc-06bbd3884d8f}
State: [1] Stable
Last error: No error

Writer name: 'Registry Writer'
Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
Writer Instance Id: {965323d9-05dd-4c83-99e1-48325e5be8e5}
State: [1] Stable
Last error: No error

Writer name: 'NPS VSS Writer'
Writer Id: {35e81631-13e1-48db-97fc-d5bc721bb18a}
Writer Instance Id: {8e0b3638-7bf9-4d64-b03c-439eea99d2ce}
State: [1] Stable
Last error: No error

Writer name: 'Certificate Authority'
Writer Id: {6f5b15b5-da24-4d88-b737-63063e3a1f86}
Writer Instance Id: {120c0b4d-b8b1-45a3-8af0-db9c54e5916e}
State: [1] Stable
Last error: No error

Writer name: 'IIS Metabase Writer'
Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
Writer Instance Id: {bb178223-08ce-4545-abb7-c71f4f09cf85}
State: [1] Stable
Last error: No error

Writer name: 'TS Gateway Writer'
Writer Id: {368753ec-572e-4fc7-b4b9-ccd9bdc624cb}
Writer Instance Id: {7e35f033-0790-42ec-b668-1af2bcfb2129}
State: [1] Stable
Last error: No error

Writer name: 'NTDS'
Writer Id: {b2014c9e-8711-4c5c-a5a9-3cf384484757}
Writer Instance Id: {82111cdd-3d8d-4d28-87c0-6332d74e31e7}
State: [1] Stable
Last error: No error

sidd3009's picture

Hello Alan,

You might want to refer to this: http://www.symantec.com/business/support/index?page=content&id=TECH125459

Also, what are we backing up? Are we making use of the Advanced Disk-based Backup Option(ADBO) for performing an offhost backup? 

 

Regards,

Siddhant Saini
Advanced Technical Support Engineer, Symantec Corporation 
www.symantec.com

IA_Alan_Lamb's picture

Hi Sidd

I had a look at that link and ran through the suggestions but they made no difference.

It's a local backup of an SBS2008 machine, this is the only server in the building so I could do with getting a decent backup of it.  It's not using ADBO.

 

Any other suggestions?

IA_Alan_Lamb's picture

Just to let everyone know. We installed the latest update for backup exec and now it seems to be working again.

Thanks.

SOLUTION