hello, me was bitten as well. Had I not tested full server restore I would only have recognised missing backup of whole file system in real disaster recovery case :( Had I tested it before the acces rights change the result would be quite same.
I find this suggestion (see below) *must* be part of documentation at the least (Andy?) regards Juraj Salak -----Ursprüngliche Nachricht----- Von: Jurjen Oskam [mailto:[EMAIL PROTECTED] Gesendet: Freitag, 07. November 2003 07:54 An: [EMAIL PROTECTED] Betreff: Re: [tsm] Perl TSM daily reporting script. On Thu, Nov 06, 2003 at 06:37:15PM +0000, Patrick Audley wrote: > David> Patrick, Looks nice. But I hope you aren't going to rely > David> on the schedule completion status to tell you whether a > David> backup has been successful. You really need to mine the > David> last backup dates of q filespace f=d (or the equiv select). > > Ah... no I hadn't realized that :) I'm actually quite new to TSM > and this is exactly the feedback that I was hoping to get. I've added > that to the todo list. Yes, I've been bitten by this. A Windows 2000 client ran the Client Acceptor under the LocalSystem account. One day, the Windows administrator changed a drive to exclude LocalSystem from having access. The TSM client didn't use a DOMAIN statement. This resulted in that drive to be skipped without *any* message, warning or error. If the drive would have been in a DOMAIN statement, an error would have been issued. There is an APAR for this behaviour, but that is closed as a suggestion because IBM finds it too much trouble to fix. -- Jurjen Oskam PGP Key available at http://www.stupendous.org/