DISASTER_RECOVERY:\ issue

Hi.

Thanks for your answer!!
I can't remove that HW , I tried to skip that HW drive backup but the same issue has come with same error.

Use should move this thread to NetWorker forum.  Also, which HW VSS provider do you use and did you try the same with native (MS) provider?

Not the drive, but VSS provider.  Depending on NW version, you are able to force usage of MS VSS provider.  I assume that one is used during restore and it fails as record can be processed by HW one.

I'm moving this into the Networker Forum

pl check below provider output and the NW version is : 8.0

C:\Users\exiap>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\exiap>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: {83ae633f-5807-4451-ac4b-9280ed8f5f27}
   State: [1] Stable
   Last error: No error

Writer name: 'Shadow Copy Optimization Writer'
   Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
   Writer Instance Id: {c4376f90-5db2-4c41-be85-33f2afc80647}
   State: [1] Stable
   Last error: No error

Writer name: 'ASR Writer'
   Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
   Writer Instance Id: {d08edb49-2c0b-4325-a232-1f722f26c47d}
   State: [1] Stable
   Last error: No error

Writer name: 'BITS Writer'
   Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
   Writer Instance Id: {51cbf4c8-b697-4108-a3e5-15ab081307e9}
   State: [1] Stable
   Last error: No error

Writer name: 'Registry Writer'
   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
   Writer Instance Id: {76f5f0c9-0bfb-49f1-ba79-9de3e8ccfdb5}
   State: [1] Stable
   Last error: No error

Writer name: 'COM+ REGDB Writer'
   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
   Writer Instance Id: {09cca447-205f-4a9c-a812-189fa3e8d5e6}
   State: [1] Stable
   Last error: No error

C:\Users\exiap>

I initially thought this was restore, but now I see this is backup.  Questions:

- what Windows OS this is?

- which version of NW

- do you have NTFS volumes involved or something else as well (similar error happens if you have FAT)

The error code itself translates to VSS_E_VOLUME_NOT_SUPPORTED_BY_PROVIDER.  Note also, that you may see this in some instances where multiple snapshots are requested against same volume so you may wish to try to set client parallelism to 1 to avoid it.

Also,

Can you check if the respective drive support snapshots ? you do the going to the properties of the drive.

Hello Surjeet,

If my understanding is correct, you are using NW 8.0 and trying to run backup for Windows 2008 client ??

Apart from Disaster recovery component, Are VSS components also failing ?

Are you running backup with save set "ALL" or you have mentioned drives and other components individually ?

Please reply to these questions, we will try to resolve your issue if its not yet resolved.

Regards,

Pawan

Thanks pawan for reply.

Yes.. I am runing backup with "ALL" save set.

Hello Surjeet,

First thing, Do you want to run backup for Disaster recovery ? If not, you can skip Disaster recovery component with save set "ALL" by adding VSS:DISASTER_RECOVERY=off in the Apps & Modules tab under the Save Operations.

If you want to run backup of Disaster recovery, then you need to trouble shoot VSS issue.

You have posted list of writers and all are looking good.  Please check in event logs on your windows client if there is any VSS related errors. Those events will be helpful to fix VSS issue. 

Regards,

Pawan