I opened a PMR with Tivoli for this very same problem. I was told "working
as designed". If you peruse the dsmsched.log, you will see that all the
different pieces of the system object are getting successfully backed up. I
honestly can't remember the reasoning I was given by Tivoli support that
explained this as working as designed...but at the time it seemed to make
sense, though I disagree that this is not a problem with this version of the
client. To report that something is not getting backed up when it clearly
is, should be considered a problem and not a design change!
Anne Short
Lockheed Martin Enterprise Information Systems
Gaithersburg, Maryland
301-240-6184
CODA/I Storage Management
-----Original Message-----
From: John Bremer [mailto:[EMAIL PROTECTED]]
Sent: Monday, March 05, 2001 6:16 PM
To: [EMAIL PROTECTED]
Subject: Win2000 system objects
Greetings,
I'm new to the forum.
I am upgrading my clients to TSM 4.1 from ADSM 3.1.8. A Win2000 client
with three partitions C: D: P: backs up successfully. I'm using a domain
statement, nothing else special in the options file.
Since upgrading to TSM 4.1 client, I now see filespace 'System
Object'. The documentation says servers at 3.7.3 and higher support the
"feature" to backup system objects as a group.
Fine by me, but when I query filespace for this node, there is no start
time, no completion time, no capacity utilization, etc. for filespace
'System Object'.
We run e-mail notification scripts off these date/time fields, and they're
going to fail without these completion statistics.
Nothing unusual in the dsmsched.log. In fact, the last message is
"Successful incremental backup of Registry".
Thanks to anyone for any input to this problem.
John Bremer
LANL
