The error snapshot technology (0xE0008526)

[Skyline231]

Hi all,

I have problem with backup copy .mdb files on the SQL server, when I try doing backup copy always i get some error :

The error snapshot technology (0xE0008526):, Backup Exec could not find for this job software or hardware snapshot technology-based VSS Microsoft (VSS). Select a valid snapshot technology VSS to the target computer.

I don't know, what is it. Please help me with it.

[VJware]

SQL DBs should ideally be backed up using the Agent for SQL, else they would be excluded by Active File Exclusion feature.

Also, do ensure Advanced Disk Based Option / Offhost backup is not selected for the backup. Enable AOFO and explicitly set it to use the Microsoft VSS provider.

[Skyline231]

Afent for SQL was installed, I tried use AOFO, checked different version (Auto, System, Hardware) but i have same error:

V-79-57344-34086 - Technology Snapshot: failed initialization: "\\ srvsql2 \ X:". The technology used snapshots: Microsoft Volume Shadow Copy Service (VSS).

The error snapshot technology (0xE0008526):, Backup Exec could not find for this job software or hardware snapshot technology-based VSS Microsoft (VSS). Select a valid snapshot technology VSS to the target computer.

 For more information, see. Event Viewer Windows.

[VJware]

On the SQL server, check the Application Logs for any errors/warnings.

Also, open a cmd & run the following commands -

vssadmin list providers

vssadmin list writers

What are the results of these commands ?

[Skyline231]

C:\Users\!admin>vssadmin list providers
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2005 Microsoft Corp.

Provider name: 'Microsoft Software Shadow Copy provider 1.0'
   Provider type: System
   Provider Id: {b5946137-7b9f-4925-af80-51abd60b20d5}
   Version: 1.0.0.7

C:\Users\!admin>vssadmin list writers
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: {81b76c0c-595d-483d-96a1-ee3034829b60}
   State: [1] Stable
   Last error: No error

Writer name: 'SqlServerWriter'
   Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
   Writer Instance Id: {1715efc6-cad5-4407-bfba-149edf200348}
   State: [1] Stable
   Last error: No error

Writer name: 'ASR Writer'
   Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
   Writer Instance Id: {b59b9ecc-a52e-4193-a0b0-e9de78f5ec80}
   State: [1] Stable
   Last error: No error

Writer name: 'Shadow Copy Optimization Writer'
   Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
   Writer Instance Id: {bf5e67da-0898-45af-928b-c8cd8e601078}
   State: [1] Stable
   Last error: No error

Writer name: 'Registry Writer'
   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
   Writer Instance Id: {327d48bb-0e60-42aa-a838-710e3de59100}
   State: [1] Stable
   Last error: No error

Writer name: 'COM+ REGDB Writer'
   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
   Writer Instance Id: {af78ef8d-448c-4566-841e-e20aa5d4500f}
   State: [1] Stable
   Last error: No error

Writer name: 'WMI Writer'
   Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
   Writer Instance Id: {3173ee44-69ef-46c4-80c4-f3051c78a301}
   State: [1] Stable
   Last error: No error

Writer name: 'IIS Config Writer'
   Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
   Writer Instance Id: {71c9e86a-98cf-4291-8f49-d0a4122bcfc0}
   State: [1] Stable
   Last error: No error

[VJware]

Would you pls attach the Application Logs from the SQL server over here. Thanks.

Additionally, what is the version of SQL ?

Have you verified Advanced Disk Based Options such as Offhost backup are not enabled in the backup job ?

[pkh]

If you are using the SQL agent, then you should turn off AOF

[Skyline231]

Sorry for my English =)

You might not quite understand me correctly, I do not have a backup of the files themselves .mdf particular job, the server itself is copied correctly. Files capacity of 150 GB

Problem with it.

itself instance SQL server copied normal.

[CraigV]

...BE has Active File Exclusion which automatically excludes a number of file extentions, *.mdf and *.ldf being some of them. As mentioned above you need to turn of AFE in order to backup the flat files.

However, doing so gives you no advantage whatsoever other than saving money. If you have the SQL agent use that. You can do online backups and restores without impacting your production app or users.

Read below for more info:

https://www.veritas.com/community/articles/stating-case-using-agents-backup-exec

Don't use AOFO when using an application agent that backs up something like SQL/Exchange etc.

THanks!

[Skyline231]

Ok,

Thanks VJware for the quick reply.

CraigV, thanks for the help.