BE Errors on a file/directory that should be excluded. Why is it even looking at this directory?
This issue has been solved. See solution.
Gai-jin
November 4th, 2009
I recently added an exclusion to the selection list for all of our servers to exclude the endpoint protection directory, since I was often getting errors on backups related to temp files that couldn't be found.
The entry in the selection list shows:
\\Server.domain.com\c:\Program Files\Symantec\Symantec Endpoint Protection\*.* /subdir /exclude
I'm still getting exceptions on my backup logs though for this directory, such as:
Backup- \\Server.domain.com\System?State VSS Snapshot warning. File c:\program files (x86)\symantec\symantec endpoint protection\smclu\setup\smcinst.exe is not present on the snapshot.
Did I do something wrong in creating the exclusion? What can I do to correct this so I don't continue seeing exceptions on my daily backups?
Filed under: Backup Exec, Backup and Archiving
The exclusion applies only to
The exclusion applies only to file system backup and not to system state backup. The backup of system state happens through VSS. So, it is VSS who is looking for this file, because of its presence somewhere in the registry. It can happen if there was some unclean install of the application, which is making it look for those files. You may try creating an exclusoin on the target machine using ntbackup(assuming this to be a Windows 2003 server, Windows 2008 may not have this option). In ntbackup you can enable exclusions, by going to tools-> options and excludes tab. This may work. But, if it does not work, your real fix would be to repair this application to which this file belongs and make sure the file is present there. You may check following MS document for more information:
http://support.microsoft.com/kb/883357
http://support.microsoft.com/kb/233427
Excluding through ntbackup would apply these registry changes in turn.
Please mark it a solution, if this is useful.
Thanks
Thanks for your reply. I
Thanks for your reply. I did check, and the file listed in the exception doesn't exist. Looking at the path and filename, it appears to be a live update related file for Symantec Endpoint Protection. I've also noticed that the directory c:\program files(x86)\symantec\symantec endpoint protection\smclu\ has a last modified date within the last 24 hours, but has no contents. Is it possible that SEP is running liveupdate as the backup job tries to capture the system state, and when liveupdate deletes the files before the backup is done, it's causing trouble?
It looks like this is
It looks like this is apparently a known issue with SEP:
http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2009081016003348?Open&seg=ent
Currently there is no fix for it, though deleting the registry key associated with this file will temporarily allow backups to complete normally.
Gai-jin
Would you like to reply?
Login or Register to post your comment.