Skipping "C:\" although Saveset is set to "All" and failing "Disaster_Recovery:\"

Run 'vssadmin list writers' and see if system writer is being showed failed.

Hi Jens,

I suspect there is some issue with the System Writer or with some VSS component.

if you run vssadin listw riters, as Mehrota suggested, you should see all the writers (especially SYSTEM WRITER) as status [1] stable and "no error".

Did you, by any chance tried to browse the content of those backups? Just open NW client on the client and find out if there is ny valid backup for C:\

Thank you,

Carlos.

ok,

unless I-m missing something this is an odd behaviour.

Could you please run this command?

savegrp - D3vvv -c client_name group_name > C:\save.out 2>&1

then please attach the C:\save.out

This to be ran on the NW server

Thank you,

Carlos

If I open Networker Client and browse for C:\ I just see the backups that I do for saveset C:\ . In NMC ->Media -> Indexes same: Whenever saveset is All , index for saveset C:\ shows no backup for that time...

output of vssadmin list writers shows no errors:

vssadmin 1.1 - Verwaltungsbefehlszeilenprogramm des Volumeschattenkopie-Dienstes

(C) Copyright 2001-2005 Microsoft Corp.

Verfassername: "Task Scheduler Writer"

   Verfasserkennung: {d61d61c8-d73a-4eee-8cdd-f6f9786b7124}

   Verfasserinstanzkennung: {1bddd48e-5052-49db-9b07-b96f96727e6b}

   Status: [1] Stabil

   Letzter Fehler: Kein Fehler

Verfassername: "VSS Metadata Store Writer"

   Verfasserkennung: {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06}

   Verfasserinstanzkennung: {088e7a7d-09a8-4cc6-a609-ad90e75ddc93}

   Status: [1] Stabil

   Letzter Fehler: Kein Fehler

Verfassername: "Performance Counters Writer"

   Verfasserkennung: {0bada1de-01a9-4625-8278-69e735f39dd2}

   Verfasserinstanzkennung: {f0086dda-9efc-47c5-8eb6-a944c3d09381}

   Status: [1] Stabil

   Letzter Fehler: Kein Fehler

Verfassername: "System Writer"

   Verfasserkennung: {e8132975-6f93-4464-a53e-1050253ae220}

   Verfasserinstanzkennung: {97573503-b312-4ca6-89d7-45727fd0b23b}

   Status: [1] Stabil

   Letzter Fehler: Kein Fehler

Verfassername: "SqlServerWriter"

   Verfasserkennung: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}

   Verfasserinstanzkennung: {359e60c5-720b-4c17-8cf9-224ae04b05e1}

   Status: [1] Stabil

   Letzter Fehler: Kein Fehler

Verfassername: "ASR Writer"

   Verfasserkennung: {be000cbe-11fe-4426-9c58-531aa6355fc4}

   Verfasserinstanzkennung: {7e40d56e-3031-429f-ae93-baed2daac238}

   Status: [1] Stabil

   Letzter Fehler: Kein Fehler

Verfassername: "Shadow Copy Optimization Writer"

   Verfasserkennung: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}

   Verfasserinstanzkennung: {5c051298-fd53-4525-9468-5f6606994538}

   Status: [1] Stabil

   Letzter Fehler: Kein Fehler

Verfassername: "WMI Writer"

   Verfasserkennung: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}

   Verfasserinstanzkennung: {33128199-92e7-442c-9ba9-119aad9980fd}

   Status: [1] Stabil

   Letzter Fehler: Kein Fehler

Verfassername: "Registry Writer"

   Verfasserkennung: {afbab4a2-367d-4d15-a586-71dbb18f8485}

   Verfasserinstanzkennung: {cbec4606-b6c4-4b97-8997-ed35fde002f6}

   Status: [1] Stabil

   Letzter Fehler: Kein Fehler

Verfassername: "COM+ REGDB Writer"

   Verfasserkennung: {542da469-d3e1-473c-9f4f-7847f01fc64f}

   Verfasserinstanzkennung: {db895b68-06bb-406e-bfeb-a20af8c3b090}

   Status: [1] Stabil

   Letzter Fehler: Kein Fehler

Verfassername: "NTDS"

   Verfasserkennung: {b2014c9e-8711-4c5c-a5a9-3cf384484757}

   Verfasserinstanzkennung: {749a18c4-56fb-46a6-acc7-d2b947f11aeb}

   Status: [1] Stabil

   Letzter Fehler: Kein Fehler

Verfassername: "DFS Replication service writer"

   Verfasserkennung: {2707761b-2324-473d-88eb-eb007a359533}

   Verfasserinstanzkennung: {26bbd90a-fd42-46bf-9e52-0dc9947f73d4}

   Status: [1] Stabil

   Letzter Fehler: Kein Fehler

Verfassername: "Dhcp Jet Writer"

   Verfasserkennung: {be9ac81e-3619-421f-920f-4c6fea9e93ad}

   Verfasserinstanzkennung: {75111493-f3bd-47e8-b63e-6915ad5b71c5}

   Status: [1] Stabil

   Letzter Fehler: Kein Fehler

Networker support said that VSS should be the problem. Requested output /nsr/tmp/sg folder of group while saving only "DISASTER_RECOVERY:\" saveset with Debug-Level 9.

Hi Carlos,

as requested from EMC Support I ran the group only with "DISASTER_RECOVERY:\" saveset with Debug-Level 9. Finally we've got a real error message that sounds familiar:

System Writer - Error saving file path C:\program files (x86)\mcafee\virusscan enterprise\x64\engineserver.exe that is associated with Shadow Copy path \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy34\program files (x86)\mcafee\virusscan enterprise\x64\engineserver.exe. Das System kann die angegebene Datei nicht finden. C:\program files (x86)\mcafee\virusscan enterprise\x64\

I know now 2 work-arounds for that:

1. create empty dummy-file for "C:\program files (x86)\mcafee\virusscan enterprise\x64\engineserver.exe"
2. save -a '"ignore-all-missing-system-files=yes"'

Do you know how this problem derives? The file "virusscan enterprise\x64\engineserver.exe" was moved to other folder months ago to folder "virusscan enterprise_\x64\engineserver.exe". How comes that VSS thinks it's still at the old location? Are there known methods for "resetting" VSS "brain"?

Thanks so far,

Jens

We removed McAfee package completely, deleted obsolete registry entries to missing file and reinstalled McAfee - Backup now works properly, no double backups anymore, C:\ backups with "All" again.

Registry keys (after uninstallation of McAfee) that affected the backup to fail:

HKLM\SYSTEM\ControlSet001\services\McAfeeEngineService

HKLM\SYSTEM\CurrentControlSet\services\McAfeeEngineService

That maybe came along with an unproper user attempt to upgrade McAfee. As we saw an additional folder

C:\Program Files (x86)\McAfee\VirusScan Enterprise_

(where the missing .exe was still to be found)

along with

C:\Program Files (x86)\McAfee\VirusScan Enterprise

So, maybe an OSI Layer 8 problem :-) instead of an unproper MSI upgrade process?

Thanks to all!