Joni,

TSM captures the Windows 2000 system state via the "SYSTEMOBJECT" domain
(it is part of the ALL-LOCAL domain). So if you run "dsmc backup
systemobject" or just do a regular incremental backup of the ALL-LOCAL
domain, you will capture the system state. This information is stored in
the "SYSTEM OBJECT" file space on the TSM server.

A redbook you should look into with more detailed information about this
is SG24-6141 - "Deploying the Tivoli Storage Manager Client in a Windows
2000 Environment". You can find this at www.redbooks.ibm.com.

You'll probably hear this from others, but there are some caveats involved
with backing up the system object. The major consideration is the system
files, which are always backed up regardless of whether they have changed.
Backing up a lot of Windows machines' system files every night can have a
profound impact on your TSM server's database and storage pool growth.
Some things to consider:

- Bind the system object files to a management class that keeps relatively
few versions. You can do this with the following include statement:

   INCLUDE.SYSTEMOBJECT ALL yourmgmtclassname

- Consider backing up the system object on a less frequent basis than your
other backups (i.e. weekly), unless the system state changes quite
frequently. With the latest TSM client, you can exclude file systems via
the DOMAIN statement by prefixing the file system with a '-' (minus) sign.
For example:

   DOMAIN ALL-LOCAL -SYSTEMOBJECT

This will set the domain to all local drives except for the system object.
Then your daily backup schedule can back up everything but the system
object. Once a week (or whatever frequency you choose), run another
scheduled event to execute the "dsmc backup systemobject". One way to do
this (since there is no ACTION=BACKUP setting on the server) is to create
a TSM client macro file that contains the command:

   BACKUP SYSTEMOBJECT

For example, if this file is C:\TSM\baclient\sysobj.mac then you can
create a schedule like this:

   DEFINE SCHEDULE STANDARD BACKSYSOBJ ACTION=MACRO
OBJECTS="C:\TSM\baclient\sysobj.mac"

I'm sure others will have thoughts/suggestions on this subject, too.   :-)

Regards,

Andy

Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
Internet e-mail: storman AT us.eyebm DOT com (change eye to i to reply)

The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.




Joni Moyer <joni.moyer AT HIGHMARK DOT COM>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
01/17/2003 12:06
Please respond to "ADSM: Dist Stor Manager"


        To:     ADSM-L AT VM.MARIST DOT EDU
        cc:
        Subject:        Windows 2000 System State



Hello,

I am responsible for the administrative side of TSM and I am not very
familiar with the client side.  Does anyone know the answer to the
following question?

Can you tell me if TSM gets the System State on Windows 2000 Servers. The
system state is comprised of the following:
COMM+ Class Registration Database
Registry
System Files.

We would need the system state if we needed to restore a server or repair
a
damaged server.
If it does can you tell me how to identify the system state in the TSM
backups.

Thanks!!!

Joni Moyer
Systems Programmer
joni.moyer AT highmark DOT com
(717)975-8338