Several of my clients who've attempting to use 11d for SharePoint backups ran into the same problem (or very similar problems). To be honest, there were a number of issues we ran into when using BackupExec to backup SP. (Restore failures anyone?) A number of my clients are now using other solutions (most of them use DocAve) to backup their SP deployments. In my experiance, DocAve is just a better fit for SharePoint...it's faster on backup and restores (like a lot faster...10x, when Symantec restores even succeed), and it gives you full-fidelity restoration, which BackupExec doesn't yet do. (I think in BE only docs can be restored individually, not list items, events, links, tasks, contacts, etc...and even then the doc versions, created date, and modified date are not restored properly, which stinks.) Anyhow, sorry I dont have a work-around for your present situation...I never found one, so my clients just went outside Symantec. Thankfully, (for what it's worth), the DocAve stuff was compatible with BackupExec and could be run concurrently - with DocAve handling the SP stuff and Symantec handling the other network protection. (I think most of the other SP data protection solution providers do too.) Symantec just hasn't quite come up-to-speed with their SharePoint solution yet.