Re: Is something broken with the filespace last backup date?
2002-09-18 13:50:08
It is only updated on a full incremental or incrbydate. Selective does not
update this field. I cannot remember if partial incremental does or not,
but I think not because then the incrbydate will not work. So, it is not
broken, it is probably working as designed.
Paul D. Seay, Jr.
Technical Specialist
Naptheon Inc.
757-688-8180
-----Original Message-----
From: Gerhard Rentschler [mailto:g.rentschler AT RUS.UNI-STUTTGART DOT DE]
Sent: Tuesday, September 17, 2002 10:55 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Is something broken with the filespace last backup date?
Hello,
we use the field "Last backup start Date/Time" from "q filespace f=d" to
find obsolete filespaces which no longer exist. Unfortunately, the content
of this field seems to be unreliable. We see cases where neither the start
date/time nor the completion time is not empty. However, "q occupancy" shows
a significant amount of data and files backed up in TSM. Other cases show a
start time more than a year ago. But the log shows data from this filespace
backed up yesterday. What's going wrong? TSM server is 5.1.1.4 on AIX 4.3.3.
The clients are 3.1.0.7 on OSF1 V4.0 and 5.1.0.0 on Linux Kernel 2.4.19-pr.
Regards Gerhard
---
Gerhard Rentschler email:g.rentschler AT rus.uni-stuttgart DOT de
Regional Computing Center tel. ++49/711/685 5806
University of Stuttgart fax: ++49/711/682357
Allmandring 30a
D 70550
Stuttgart
Germany
|
|
|