Hi Robert,
as far as I know the effect of '21' is, that errors will be forwarded to '1'
- which is '/dev/console'
As there is a log for the webclient (dsmwebcl.log) you could just throw the
error messages away with '2/dev/null'
Isabel
Robert Dowsett schrieb:
Hi everyone.
We have recently
.
From previous Messeges of the List I checked, that the Diskpool has
caching disabled and the clients have no compression allowed.
I was away from work for a while and meanwhile a serverupdate has been
done.
If anyone can point me to the source of this error, please help!
Thanks in advance,
Isabel
Hi Listmembers,
some of our nodes suddenly fail their daily backup with a returncode 4.
They receive some file-errors, but sometimes it's returncode 0 and
sometimes it's returncode 4. I can't see the difference... In the
eventlog they show failed.
Please help!
Greetings,
Isabel Gerhardt
04/19
Thanks for responses!
I will try the following:
1) set highmig fairly low during main backup time so there'll be enough space in
diskpool
2) set maxsize to a value that I know is lower than the filesizes where the
message occurs
Still it would be better to solve the actual problem: the
Hi,
has anybody experiences with setting up and using snmp with TSM?
I am not getting further than setting up the connection.
When I try to work with the variables (as shown in the Administrator's
Guide) I get errormessages.
Maybe there is more docu in some place where I can find further Info.