TSM Problem + Symantec Backup Exec System Recovery

[Dormelchen]

Hello,
we backup Servers with TSM (Client Version TSM 5.5.0 + Win 2003)
We have Symantec BESR for Desaster Recovery + remote recovery.
We backup Systempartition C: to another Server in the network with BESR 6.5 and 8.
We schedule / planning these backups from 1 Server called BackupServer.

Now we have Symantec BESR 8.0 on some Servers and i get a lot of errors in the dsmschederr.log.
And i dont know how to eliminate these messages:

22.04.2008 02:10:48 ANS5250E An unexpected error was encountered.
TSM function name : fioStatFs
TSM function : Invalid file system '\\?\symantecsnapshot0\' drive type '6'
TSM return code : 131
TSM file : psfsinfo.cpp (1564)

the log is full of these messages.

Any ideas ?
Exlcude list ?

Please Help

Thanks

[moon-buddy]

Off hand I would look at the offending files and try excluding them.

Also you, may want to make sure that you limit your TSM backups to local Domains.

[Dormelchen]

in my dsm.opt i have :
DOMAIN C: D: SYSTEMSTATE

EXCLUDE "C:\pagefile.sys"
EXCLUDE.DIR "C:\Documents and Settings\*"
EXCLUDE.BACKUP "C:\IBMBIO.COM"
EXCLUDE.BACKUP "C:\IBMDOS.COM"
EXCLUDE.BACKUP "C:\IO.SYS"
EXCLUDE.DIR "*:\Recycled"
EXCLUDE.DIR "*:\Recycler"
EXCLUDE.DIR "D:\backup"

So it is limit to local domain ?

[nezih]

what is the objects value of your scheduled job
(it calls \\?\symantecsnapshot0\ share?)

[Dormelchen]

The Backup is scheduled by an Managementserver.
Backup from this client (with the errors) to an Backup Server
(Network).

With Version 6.5 symantec Backup Exec System Recovery there are no problems. Logfiles from TSM are empty.
Some Clients have 6.5 - the newer server have 8.0 (4 new Server)

Backup with TSM runs at 2 am every day incremental.
Backup with Symantec runs last Day in month at 10 pm.


But where is \\?\symantecsnapshot0\ ????

cannot see it
Can i exclude it ??

[heada]

I would exclude it. It is obviously part of the Symantec backup and thus not needed in TSM and more than likely you wouldn't ever want to restore it. You may want to confirm this with your Symantec support group.

-Aaron