trafsta
16 years agoLevel 3
Skipped files on AOFO (VSS) Backup of Windows Server 2008 SP2 with Backup Exec 12.5 Rev 2213 (SP2)
Immediately after installing Service Pack 2 (SP2) on our Windows Server 2008 x86/x64 servers, Backup Exec has started to skip two files during backups:
Backup- \\server\System?State
VSS Snapshot warning. File c:\windows\system32\drivers\s3cap.sys is not present on the snapshot.
VSS Snapshot warning. File c:\windows\system32\drivers\storflt.sys is not present on the snapshot.
Previous to Win2k8 SP2 these files either did not exist or were not skipped for not being present in the snapshot. We are running the latest and greatest version of Backup Exec (12.5 Rev 2213 [SP2, Hotfixes 322898, 324947, 317436, 325647), and the latest version of the agents have been pushed to the clients.
I have tried putting global excludes on those two files just in case it would help, but it has not.
Is anyone else experienced this since upgrading to Win2k8 SP2? Or does anyone know how I can correct it?
Thanks!
Backup- \\server\System?State
VSS Snapshot warning. File c:\windows\system32\drivers\s3cap.sys is not present on the snapshot.
VSS Snapshot warning. File c:\windows\system32\drivers\storflt.sys is not present on the snapshot.
Previous to Win2k8 SP2 these files either did not exist or were not skipped for not being present in the snapshot. We are running the latest and greatest version of Backup Exec (12.5 Rev 2213 [SP2, Hotfixes 322898, 324947, 317436, 325647), and the latest version of the agents have been pushed to the clients.
I have tried putting global excludes on those two files just in case it would help, but it has not.
Is anyone else experienced this since upgrading to Win2k8 SP2? Or does anyone know how I can correct it?
Thanks!
- Hi,
Same issue and same circumstances. In our case it is a 2008 virtual machine running under Hyper-V. Could not find reference to the files in the registry.
I think the two missing files are from the previous version of Hyper-V Integration components which were updated in SP2. Appears these files are now named to vms3cap.sys and vmstorfl.sys. Being tired of the exceptions, I just made copies of those two files giving them the names it's looking for.
Until Symantec fixes this, at least I don't have to look at the same error every day!