VSS Snapshot Warning

This may help, but you should make sure that you have the lastest VSS patch for your system installed on local and remote systems:

http://www.microsoft.com/downloads/details.aspx?FamilyID=ae17b7ef-3c02-496a-bb46-770c04e42b5c&DisplayLang=en  (server 2003)

http://www.microsoft.com/downloads/details.aspx?FamilyID=5eb76bda-8794-412a-9fd4-1bccbbc34c82&DisplayLang=en (server 2008 x64)

We are having the same issue with the same file. If anyone can offer any insight, it will be appreciated. Thanks!

VSS Snapshot warning. File c:\windows\system32\drivers\dcdbas32.sys is not present on the snapshot

Windows Server 2008 Ent SP1 - Backup Exec 12.5 rev 2213

We do not have Dell Server Administrator installed, but it is a Dell Poweredge 2950 Server that is running the backup exec software, and the error is for the local system state backup.

We have the same issue. We run Backup Exec 12.5 on Windows 2008 32 bit.

When I run a full backup I get the following error:

VSS Snapshot warning. File c:\windows\inf\oem1.inf is not present on the snapshot.

Before I had some problem with my tape drive. I removed it from the device list and reinstalled it using tapeinst.exe.

After this the backups ran again, but I get this snapshot warning.

How can I fix this problem? Thank you!

I was finally able to recreate this problem on a test system. This is being caused by any number of programs installed on Windows 2008 not uninstalling correctly, but the issue may even be in a place called the NT filespace (I have two more Microsoft internal OS databases to look at before I can conclude that), which is not accessible by any normal means. One of the most common offenders is VMWare Server version 1.xx. This is a Windows problem, not a BE problem, and BE is just reporting what Windows is telling it.

I have deleted every file with an internal reference to the reported files, and that does not help.

I am trying to find a solution, but if not, I will post a work-around. After I look at those OS databases, I will also post everything I have done and show where the problem is being created.

I am doing this as my time allows, so it could take a week. The issue is benign though.

Kevin,

Thank you for the information. The issue is indeed benign.

It is only annoying to have these warnings.

Thank you.

Tim, that is probably because you just reinstalled the file that the snapshot was looking for, so it now exists. I would bet that if you uninstall the application again, the warning would return.

That masked the warning, but probably is not a solution for anyone who actually wants to remove an application for good, like when this occurs after uninstalling VMWare.

Although this thread is a few weeks old and there is already an accepted solution i thought i would post here as i have run into an issue with the same file (c:\windows\system32\drivers\dcdbas32.sys).

I found this support article for a different file but similar issue http://seer.entsupport.symantec.com/docs/304833.htm

The problem i have there is a registry key in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\PnpLockdownFiles

that points to dcdbas32.sys but the file does not exist in \system32\drivers\

Unlike Timothy I havent installed Dell OpenManage on my server nor do i plan to ever install it and i dont think there is even a 64bit version of it (i may be wrong havent really looked into it). So can i just remove the registry key? or will that cause other issues? Will that even solve the problem?

Thanks

Paul, You should be able to remove that key with not problems, but I always suggest that you export it to the desktop first, just in case.

That said, I don't think that will make the error message go away. The error is being caused wherever the backup list of files is being created from the snapshot, and although I have not had time lately, I can't find where that is. It is not in the registry or in any file. I suspect it may be in the Windows namespace somewhere.

The workaround is to actually put a copy of the file in that directory. You could even create a blank text file and rename it to whatever the file your backup is reporting.