Reinhard,
> With the new client software and after rebooting the machine, the situation
> has not changed. Files to be backed up are still recalled.
This behavior was also 'available' in version 3.x (forgot the level, I try to
forget HSM-problems I find as soon as possible.)
> Anyway,
Luci Ziebart writes:
> Couldn't you just restore from the database backup prior to the error? Provided
> of course that you do a daily database backup.
Yes, I could have done that. But that would have meant the loss of almost
2 day's worth of data, which is a lot on a heavily used TSM server.
Richard Sims writes:
> >last weekend, the backup of our biggest HSM filesystem (AIX 4.3.2,
> >ADSM 3.1.0.8) expired all files !!!
>
> Reinhard - My sympathies on that ugly problem. It superficially sounds
thanks
>as though the file system was not mounted, such that the
> backu
Stor Manager"|
|| |
|+--->
>|
||
| To: [EMAIL PROTECTED] |
| cc: (bcc: Luci Ziebart/MGIC) |
| Subject: Re: HSM disaster: all bac
>last weekend, the backup of our biggest HSM filesystem (AIX 4.3.2,
>ADSM 3.1.0.8) expired all files !!!
Reinhard - My sympathies on that ugly problem. It superficially sounds
as though the file system was not mounted, such that the
backup found just the empty mount point directory an
Hi,
last weekend, the backup of our biggest HSM filesystem (AIX 4.3.2,
ADSM 3.1.0.8) expired all files !!! I do not know the reason; the
only hint I get is one line in dsmerror.log:
TransErrno: Unexpected error from fioGetFS:statfs, errno = 4
My main concern now is: how do I handle the situation
