What we found to work well is to use NTBACKUP to backup the SYSTEMSTATE
then backup the system.   The backup runs faster due to a single file
for the systemstate and we have not had a problem with recovery.

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
TSM_User
Sent: Saturday, April 30, 2005 10:46 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: DOMAIN Settings

I believe you must be at TSM server level V5.2 or above in order to
backup a Windows 2003 server's system state.  You could change your
domain statment to:
 "Domain ALL-LOCAL -SYSTEMSTATE -SYSTEMSERVICES"
to stop backing them up.  I would strongly suggest that you implement a
system state backup to a flat file using NT Backup if you can't upgrade
your TSM server.


"Gill, Geoffrey L." <GEOFFREY.L.GILL AT SAIC DOT COM> wrote:
Are there any recommendations for the DOMAIN setting in the dsm.opt for
Windows 2003 clients running TSM version 5.2 or above and a TSM server
level at 5.1.6.3?



The reason I ask is because I am seeing this error in the activity log
for some nodes that fall in to this category. I believe it is pointing
to the System State filespace.



04/27/05 20:34:58 ANR9999D smnode.c(18984): ThreadId<192> Session 6529
for node xxxx-xxxx : Invalid filespace for backup group

member: 3.




Thanks,



Geoff Gill
TSM Administrator
NT Systems Support Engineer
SAIC
E-Mail: gillg AT saic DOT com
Phone: (858) 826-4062

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around
http://mail.yahoo.com