I'm running into backup issues that have seemed to come out of nowhere. It either abends on TSA or BPCD(NetBackup) related issues. I know I need to update my OS to 6.5.3, (running 6.5.2) but I've upgraded to TSA5UP18. Not sure based on these abends if it's a Veritas problem or a Novell problem or little of both. TSA load line looks like this: Load TSAFS.NLM /CacheMemoryThreshold=1 /ReadBufferSize=65536. Any info would be appreciated. Thanks.
Mark


Server WWT-MAIN halted Tuesday, August 30, 2005 8:00:55.498 pm
Abend 1 on P00: Server-5.70.02: Page Fault Processor Exception (Error code 00000000)

Registers:
CS = 0060 DS = 007B ES = 0068 FS = 007B GS = 007B SS = 0068
EAX = 00000000 EBX = 00000000 ECX = 00000000 EDX = 00000000
ESI = 1B042000 EDI = 6F783894 EBP = 9790DEE0 ESP = 9790DECC
EIP = 58C0239C FLAGS = 00010246
58C0239C 8B8824040000 MOV ECX, [EAX+00000424]=?
EIP in TSAFS.NLM at code start +0001339Ch
Access Location: 0x00000424

The violation occurred while processing the following instruction:
58C0239C 8B8824040000 MOV ECX, [EAX+00000424]
58C023A2 85C9 TEST ECX, ECX
58C023A4 741A JZ 58C023C0
58C023A6 51 PUSH ECX
58C023A7 E8D43E0300 CALL TSAFS.NLM|tsaFree
58C023AC 8B8766010000 MOV EAX, [EDI+00000166]
58C023B2 83C404 ADD ESP, 00000004
58C023B5 C7840324040000 MOV [EBX+EAX+00000424], 00000000
0000000058C023C0 8BB766010000 MOV ESI, [EDI+00000166]
58C023C6 01DE ADD ESI, EBX



Running process: BPCD.NLM 11 Process
Thread Owned by NLM: BPCD.NLM
Stack pointer: 9790DA50
OS Stack limit: 979062E0
Scheduling priority: 67371008
Wait state: 5050090 Wait for interrupt
Stack: --00000000 ?
--00000000 ?
--00000030 ?
--6F783884 ?
--6F783894 ?
--9790DF10 ?
58C2DE27 (TSAFS.NLM|DSET_Destroy+47)
--6F783894 ?
--00000000 ?
--43150147 ?
--00000039 ?
--00000000 ?
58C36A4F (TSAFS.NLM|internTsaKSpinLock+F)
--58C6E384 ?
--00000030 ?
--9832B1A0 ?
--6F783884 ?
--9790DF30 ?
58C2E5D7 (TSAFS.NLM|DSET_DestroyCache+137)
--6F783884 ?
--00000000 ?
--9832B1A0 ?
--984A1D47 ?
--9832B1A0 ?
--984A1D53 ?
--9790DF54 ?
58C3AFDC (TSAFS.NLM|ScanNextDataSet+31C)
--6F783884 ?
--00010039 ?
--00000184 ?
--88F8C060 ?
--9790E12E ?
--00000463 ?
--5868C968 ?
--9790E168 ?
589B73D2 (SMDR.NLM|NWSMTSScanNextDataSet+B9)
--00000001 ?
--984A1D53 ?
--984A1D47 ?
--984A1D43 ?
-5D2DD8DA ?
--57814A80 ?
5D42F533 ?
--00000001 ?
--984A1D53 ?
--984A1D47 ?
--984A1D43 ?
--9790DFB9 ?
-5D2DCBD5 ?
-5D2D7694 ?
5D41C84A ?
--88AEB641 ?
--8847B060 ?
--9790DFC4 ?
--000000A2 ?
--88AEB641 ?
--6F697062 ?
--77623A3A ?
--65746972 ?
--00000300 ?
--00000000 ?
--000000A2 ?
--000000A2 ?
--00000000 ?
--57814A80 ?
--9790E074 ?
--9790E055 ?
-5D2DDF75 ?
-5D2D7694 ?
5D43BE8F ?
--88AEB641 ?
--8847B102 ?
--00000000 ?
--88AEB641 ?
--6D656D20 ?
--88AEB641 ?
--00000000 ?
--20525245 ?
--0000202D ?
--00000000 ?
--00000000 ?
--00000000 ?
--00000000 ?
--00000000 ?
--00000000 ?
--00000000 ?
--00000000 ?
--00000000 ?
--00000000 ?
--00000000 ?
--00000000 ?
--00000000 ?
--00000000 ?
--5F726174 ?
--65736162 ?
--5F563A3A ?
--72615476 ?
--4D67734D ?
--00000000 ?
--9790E0DC ?

Additional Information:
The CPU encountered a problem executing code in TSAFS.NLM. The problem may be in that module or in data passed to that module by a process owned by BPCD.NLM.


Server WWT-MAIN halted Monday, August 29, 2005 1:53:26.888 pm
Abend 1 on P00: Server-5.70.02: Page Fault Processor Exception (Error code 00000000)

Registers:
CS = 0060 DS = 007B ES = 0068 FS = 007B GS = 007B SS = 0068
EAX = 02037E64 EBX = 323AA1A4 ECX = 00000000 EDX = 00020001
ESI = 00000000 EDI = 00000000 EBP = 590DACCC ESP = 590DACB8
EIP = 57AD5A25 FLAGS = 00010246
57AD5A25 F6404E TEST byte ptr [EAX+4E]=?
EIP in TSAFS.NLM at code start +0003DA25h
Access Location: 0x02037EB2

The violation occurred while processing the following instruction:
57AD5A25 F6404E TEST byte ptr [EAX+4E]
57AD5A28 40 INC EAX
57AD5A29 740A JZ 57AD5A35
57AD5A2B F64516 TEST byte ptr [EBP+16]
57AD5A2E 02746980 ADD DH, [ECX+EBP*2-80]
57AD5A32 650CFB GS:
OR AL, FB
57AD5A35 8B931E030000 MOV EDX, [EBX+0000031E]
57AD5A3B 83FA03 CMP EDX, 00000003
57AD5A3E 7562 JNZ 57AD5AA2
57AD5A40 8BBBC2010000 MOV EDI, [EBX+000001C2]



Running process: TSA Open: 8E50A0C0 Process
Thread Owned by NLM: SERVER.NLM
Stack pointer: 590DA83C
OS Stack limit: 590D3000
Scheduling priority: 67371008
Wait state: 5050090 Wait for interrupt
Stack: --00000000 ?
--00000000 ?
--B1B1B1B1 ?
--00000007 ?
--323AA1A4 ?
--590DAD10 ?
57AB5C73 (TSAFS.NLM|JOB_InsertOpenList+2E3)
--323AA1A4 ?
--00000007 ?
--00000000 ?
--00020001 (SERVER.NLM|BIOSDriveCount+3539)
--00000000 ?
--00000000 ?
--00000007 ?
--431359A6 ?
--00000000 ?
--00000000 ?
--00000000 ?
--0000000E ?
--8E50A12C ?
--00000000 ?
--8E50A0C0 ?
--590DAF34 ?
57AB7067 (TSAFS.NLM|tsaOpenThread+147)
--8E50A0C0 ?
--20415354 ?
--6E65704F ?
--4538203A ?
--30413035 ?
--00003043 ?
4C4046E0 (COMN.NSS|CleanupSnapshotBeast+390)
--00000000 ?
--4D409AFC ?
--590DAD50 ?
4BEE3C74 (NSS.NLM|cacheRelease+74)
--4D409AFC ?
--4D409AFC ?
--01DA1EB6 ?
--590DADF4 ?
4C406289 (COMN.NSS|COMN_Write+7B9)
--0D8E95A0 ?
--0D8E95A0 ?
--00000000 ?
--000000AC ?
--00000000 ?
--00000010 ?
--51D80202 ?
--00000000 ?
4C404600 (COMN.NSS|CleanupSnapshotBeast+2B0)
--00000000 ?
--4C023000 ?
--00000000 ?
--00000000 ?
--00000001 ?
--00001000 ?
--2BAA4CDC ?
--2BAA4CF0 ?
--0000000C ?
--00000000 ?
--000AC0CC ?
--00000000 ?
--2BAA4CA0 ?
--0D8E9614 ?
--0D8E95A0 ?
--00000000 ?
--00000000 ?
--0D8E95A0 ?
--000AC600 ?
--00000001 ?
0022E842 (SERVER.NLM|kScheduleFastWorkToDo+16)
-4BF7E144 (MAL.NSS|MALCallbackEvent+0)
0022E862 (SERVER.NLM|kScheduleFastWorkToDo+36)
--4EAF2E40 ?
4C2B283F (MAL.NSS|MalMMCallBack+FF)
-4BF7E094 (MAL.NSS|MMCallbackLock+0)
--00000000 ?
--8DDD0B7C ?
--00000000 ?
48C433F7 (MM.NLM|MM_CompleteMessage+33)
--88080A1E ?
--4EAF9180 ?
48C43404 (MM.NLM|MM_CompleteMessage+40)
--8DDD0B7C ?
--95557000 ?
--00000000 ?
--00000009 ?
--8DDD0B7C ?
48C698CB (MM.NLM|UpdateIOStatsCallback+B3)
--8DDD0B7C ?
--76726553 ?
--30207265 ?
--38343A30 ?
--8DDD0B00 ?
48C433F7 (MM.NLM|MM_CompleteMessage+33)
--88080A1E ?
--8DDD0B7C ?
48C43404 (MM.NLM|MM_CompleteMessage+40)
--8DDD0B7C ?
--00000000 ?
--00000000 ?

Additional Information:
The CPU encountered a problem executing code in TSAFS.NLM. The problem may be in that module or in data passed to that module by a process owned by SERVER.NLM.