I agree that, at the very least, this issue should be
documented, if not fixed. APAR IC29793 has been opened
to address this shortcoming. I can not say how or when
it will be closed at this time.
APAR abstract:
QUERY FILESPACE SYSTEM OBJECT LAST BACKUP START DATE, DAYS SINCE
LAST BACKUP STARTED, ETC. NOT REPORTED IN STATISTICS.
APAR text:
QUERY FILESPACE FORMAT=DETAILED for the SYSTEM OBJECT filespace
does not report any statistics for Last Backup Start Date/Time,
Days Since Last Backup Started, Last Backup Completion Date/Time
or Days Since Last Backup Completed.
Sample output:
ANS8000I Server command: 'q fi storman 'SYSTEM OBJECT' f=d'
Node Name: STORMAN
Filespace Name: SYSTEM OBJECT
Platform: WinNT
Filespace Type: NTFS
Capacity (MB): 0.0
Pct Util: 0.0
Last Backup Start Date/Time:
Days Since Last Backup Started:
Last Backup Completion Date/Time:
Days Since Last Backup Completed:
These statistics should be filled in; if they can not be filled
in for technical reasons, then at the very least this
restriction should be documented.
Also, the Capacity and Pct Util statistics are misleading. While
it is difficult to attach any meaning to Capacity for the
SYSTEM OBJECT (because it isn't a file system), perhaps Capacity
could be set to the actual number of MB backed up, and Pct Util
set to 100? Either that, or it should be documented that these
values will always display as 0.
LOCAL FIX:
Check dsmsched.log on the client machine to verify that the
SYSTEM OBJECT was backed up successfully.
Regards,
Andy
Andy Raibeck
IBM Tivoli Systems
Tivoli Storage Manager Client Development
e-mail: [EMAIL PROTECTED]
"The only dumb question is the one that goes unasked."
"Short, Anne" <[EMAIL PROTECTED]>@VM.MARIST.EDU> on 03/05/2001 09:21:34
PM
Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:
Subject: Re: Win2000 system objects
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
