Hi David,
You should use:
include.systemstate all
where is the name of the desired management class.
New backup objects will appear bound to the specified management class.
Older objects will still show up as bound to the older class, but the
system state as a whole will be managed to the
> If a Windows client (v6.2) excludes a file is part of the Systemstate
> backup, is that file still backed up as part of the systemstate?
I assume you are talking about using an EXCLUDE statement to do this, in
which case the answer is yes, it is still backed up (the EXCLUDE is
ignored). You cann
mmand line is your friend.
"Good enough" is the enemy of excellence.
"ADSM: Dist Stor Manager" wrote on 2009-09-30
05:34:45:
> [image removed]
>
> Re: systemstate error
>
> Robert Ouzen Ouzen
>
> to:
>
> ADSM-L
>
> 2009-09-30 05:35
>
> Sen
Hi Andy
I checked it and the file vnetinst.dll did not exist on the server , I have
another server with the same configuration (Windows 2008 and Tsm client
6.1.0.2) the systemstate backup is running correctly and there too the file
vnetinst.dll did not exist !!!
On the server with the error I
Robert,
Microsoft defines system state as being "a collection of several key
operating system elements and their files". Microsoft does not support
restoring a subset of system state. TSM has been implemented to follow
Microsoft guidelines in this regard. Thus if a system state file cannot be
foun
