DennyP
ADSM.ORG Member
Envirimement:
IBM 6H2 2 way
AIX 4.3.3 ML10
2 GB Ram
2) IBM3575 Magstar 180's, 4 drives each
Backups directly to tapes
TSM 4.2.2.7 Server
TSM 4.2.2.5 AIX clients.
After the upgrade to the above versions of TSM, started getting ANS1074I User Abort
and RESULT CODE NOT ZERO= 4 messages. The incremental for the designated filesystem stopped at that point and continued with the next filesystem. No other message in dsmerror.log. Nothing in the activity log on the server.
Happened on multiple clients.
( I use korn shell script to back up each file system and generate log files on the client.)
I did not catch this until recently, so I have a lot of users who are disgruntled because we can't restore files that they ''accidently'' deleted.
Running an incremental manually (dsmc inc <fsname> -SUBDIR=YES) got similiar results.
I tried a number of things without correcting it until I changed the MAX MOUNTPOINTS to 2
(was 1).
Seems to be working OK now.
My question is:
WHY?
Denny P.
IBM 6H2 2 way
AIX 4.3.3 ML10
2 GB Ram
2) IBM3575 Magstar 180's, 4 drives each
Backups directly to tapes
TSM 4.2.2.7 Server
TSM 4.2.2.5 AIX clients.
After the upgrade to the above versions of TSM, started getting ANS1074I User Abort
and RESULT CODE NOT ZERO= 4 messages. The incremental for the designated filesystem stopped at that point and continued with the next filesystem. No other message in dsmerror.log. Nothing in the activity log on the server.
Happened on multiple clients.
( I use korn shell script to back up each file system and generate log files on the client.)
I did not catch this until recently, so I have a lot of users who are disgruntled because we can't restore files that they ''accidently'' deleted.
Running an incremental manually (dsmc inc <fsname> -SUBDIR=YES) got similiar results.
I tried a number of things without correcting it until I changed the MAX MOUNTPOINTS to 2
(was 1).
Seems to be working OK now.
My question is:
WHY?
Denny P.
