Check your Domain Statement in dsm.opt. The defualt ALL-LOCAL with 4.12 is
to include the System Object (includes registry, event logs, comp+db, system
files, Cert Serv Db, AD, frs, cluster db - depends if pro, dc etc on which
of these the system object contains).
If your DOMAIN STATEMENT does not include ALL-LOCAL (EG DOMAIN C:\ D:\) then
it will not include the system object and your registry will get backed up
if the option backup registry is set to yes (the defualt). (But you will be
missing the rest of the system ojbects).
The dsmerror.log does show that the ADSM.SYS is being excluded, but Tivoli
really should have mentioned this design change in the readme.
Tim Rushforth
City of Winnipeg
-----Original Message-----
From: Short, Anne [mailto:[EMAIL PROTECTED]]
Sent: Thursday, February 01, 2001 7:42 AM
To: [EMAIL PROTECTED]
Subject: Re: Which client version is best for a Win2000-server ?
We have a TSM 4.1.2 server on W2K, as well as the 4.1.2 client to back
itself up. TSM has consistently reported that there has never been a backup
of the SYSTEM OBJECT. After reading through all the helpful information in
the subject post by Wanda and Tim, I modified my include/exclude list to
ensure that the adsm.sys directory gets backed up, assuming that was my
problem. I can confirm this morning via the dsmerror.log and dsmsched.log
that those objects are now getting backed up, but it still reports that the
SYSTEM OBJECT has not been backed up.
What am I missing? What exactly is the SYSTEM OBJECT it is complaining
about? I use the dumpel.exe to dump the event logs so they get backed up as
part of the normal back up of the C: drive. And per the dsmsched.log, I get
a successful backup of the Registry every night. I'm a UNIX person at
heart, so excuse me if this is some obvious NT thing I'm missing.
Anne Short
Lockheed Martin Enterprise Information Systems
Gaithersburg, Maryland
301-240-6184
CODA/I Storage Management
