Backup exec 9.2 NDMPD.nlm abends server - Veritas Backup Exec

This is a discussion on Backup exec 9.2 NDMPD.nlm abends server - Veritas Backup Exec ; We are running Netware 6.5sp5, BackupExec 9.2. 1391 Since upgrading to NW6.5 and BE 9.2 we are unable to get a backup. Server abends every night in module NDMPD.nlm with page fault. Server is patched to most recent level of ...

+ Reply to Thread
Results 1 to 6 of 6

Thread: Backup exec 9.2 NDMPD.nlm abends server

  1. Backup exec 9.2 NDMPD.nlm abends server


    We are running Netware 6.5sp5, BackupExec 9.2. 1391

    Since upgrading to NW6.5 and BE 9.2 we are unable to get a backup. Server
    abends every night in module NDMPD.nlm with page fault.
    Server is patched to most recent level of NetWare and BackupExec. We are
    only attempting FULL backups due to the Archive Bit problem. Abend log entry
    follows.

    Server config: IBM e345 dual xeon processor (hyperthreading enabled), 4GB
    RAM, SCSI RAID5

    Anyone else having/had this issue??

    ************************************************** *******
    Novell Open Enterprise Server, NetWare 6.5
    PVER: 6.50.05

    Server AGRHLN001 halted Thursday, March 16, 2006 12:09:42.238 am
    Abend 1 on P00: Server-5.70.05: Page Fault Processor Exception (Error code
    00000000)

    Registers:
    CS = 0008 DS = 0068 ES = 0068 FS = 0068 GS = 007B SS = 0068
    EAX = 00000000 EBX = FCC1FCE0 ECX = A25923A9 EDX = 000001A0
    ESI = 12C5FBC0 EDI = FCD1FB20 EBP = 00000000 ESP = 8D5983AC
    EIP = 00323105 FLAGS = 00010202
    00323105 8B6D00 MOV EBP, [EBP+00]=?
    EIP in SERVER.NLM at code start +00117185h
    Access Location: 0x00000000

    The violation occurred while processing the following instruction:
    00323105 8B6D00 MOV EBP, [EBP+00]
    00323108 C1E005 SHL EAX, 05
    0032310B 8D9580020000 LEA EDX, [EBP+00000280]
    00323111 01D0 ADD EAX, EDX
    00323113 8B10 MOV EDX, [EAX]
    00323115 8917 MOV [EDI], EDX
    00323117 8938 MOV [EAX], EDI
    00323119 C7857C02000001 MOV [EBP+0000027C], 00000001
    00000000323123 8B532C MOV EDX, [EBX+2C]
    00323126 8B480C MOV ECX, [EAX+0C]



    Running process: VxNDMP_849025a0 Process
    Thread Owned by NLM: NDMPD.NLM
    Stack pointer: 8D59840C
    OS Stack limit: 8D588E00
    CPU 0 (Thread 806B2140) is in a NO SLEEP state
    Scheduling priority: 67371008
    Wait state: 5050100 Delayed
    Stack: A1254FB7 (AD_ASPI.NLM|ClearThisLoaderBusy+2B0B)
    --8D5983D0 ?
    --00000000 (LOADER.NLM|KernelAddressSpace+0)
    --00000001 (LOADER.NLM|KernelAddressSpace+1)
    --8D5984AC ?
    --00000001 (LOADER.NLM|KernelAddressSpace+1)
    A12502EE (AD_ASPI.NLM|DeBuildTCB+7E)
    --00000001 (LOADER.NLM|KernelAddressSpace+1)
    --8D5983D0 ?
    --806B2140 (CONNAUD.NLM|connNumList+8DA9)
    --00000000 (LOADER.NLM|KernelAddressSpace+0)
    --00000000 (LOADER.NLM|KernelAddressSpace+0)
    --00000000 (LOADER.NLM|KernelAddressSpace+0)
    --00000000 (LOADER.NLM|KernelAddressSpace+0)
    --FFD606E0 ?
    --00FFFFFE ?
    --00000001 (LOADER.NLM|KernelAddressSpace+1)
    --00000000 (LOADER.NLM|KernelAddressSpace+0)
    --00010001 ?
    --00000000 (LOADER.NLM|KernelAddressSpace+0)
    --B04F5600 ?
    --BA7545E0 ?
    --806B1100 (CONNAUD.NLM|connNumList+7D69)
    --11111111 ?
    00223581 (SERVER.NLM|SchedSwitch+2A9)
    --E1FE4B2A ?
    --0000935A (LOADER.NLM|KernelAddressSpace+935A)
    --0000935A (LOADER.NLM|KernelAddressSpace+935A)
    --00006C90 (LOADER.NLM|KernelAddressSpace+6C90)
    --00000000 (LOADER.NLM|KernelAddressSpace+0)
    --00006C90 (LOADER.NLM|KernelAddressSpace+6C90)
    --00000000 (LOADER.NLM|KernelAddressSpace+0)
    --00000000 (LOADER.NLM|KernelAddressSpace+0)
    --0000935A (LOADER.NLM|KernelAddressSpace+935A)
    --0000FFEA (LOADER.NLM|KernelAddressSpace+FFEA)
    8C2096C9 ?
    --0000FFEA (LOADER.NLM|KernelAddressSpace+FFEA)
    --00000000 (LOADER.NLM|KernelAddressSpace+0)
    --0000935A (LOADER.NLM|KernelAddressSpace+935A)
    --00000000 (LOADER.NLM|KernelAddressSpace+0)
    --8D5984D8 ?
    --0000FFEA (LOADER.NLM|KernelAddressSpace+FFEA)
    --00000000 (LOADER.NLM|KernelAddressSpace+0)
    --00006C90 (LOADER.NLM|KernelAddressSpace+6C90)
    --00000000 (LOADER.NLM|KernelAddressSpace+0)
    --00000000 (LOADER.NLM|KernelAddressSpace+0)
    --8077C7E0 ?
    --FB224000 (LOADER.NLM|PAEPageDirBase+4000)
    --8077C7E1 ?
    --00000000 (LOADER.NLM|KernelAddressSpace+0)
    --00000001 (LOADER.NLM|KernelAddressSpace+1)
    --8BB31E80 ?
    --80749720 ?
    --8077C7E0 ?
    002357A9 (SERVER.NLM|CValidateMappedAddress+11)
    --8077C7E0 ?
    --00000001 (LOADER.NLM|KernelAddressSpace+1)
    --00000001 (LOADER.NLM|KernelAddressSpace+1)
    C006D873 (THREADS.NLM|LinkTCSToTGCS+5F)
    --8077C7E0 ?
    --00000001 (LOADER.NLM|KernelAddressSpace+1)
    --00000001 (LOADER.NLM|KernelAddressSpace+1)
    --841A30E0 ?
    --00000246 (LOADER.NLM|KernelAddressSpace+246)
    --8D5984D0 ?
    --0000BE02 (LOADER.NLM|KernelAddressSpace+BE02)
    --000041E8 (LOADER.NLM|KernelAddressSpace+41E8)
    --12C5F960 ?
    C006ACCF (THREADS.NLM|free+F)
    --12C5F960 ?
    8435D659 (TSAFS.NLM|tsaFree+29)
    --12C5F960 ?
    --A7B38E24 ?
    --8D5984E8 ?
    8431231A (TSAFS.NLM|FreeTSAReadBuffer+1A)
    --12C5F964 ?
    --0000BE02 (LOADER.NLM|KernelAddressSpace+BE02)
    --000041E8 (LOADER.NLM|KernelAddressSpace+41E8)
    --839ED3E4 ?
    --8D5984F4 ?
    84353D68 (TSAFS.NLM|DSET_DestroyReadBufferQueueHeadNoLock+2 8)
    --A7B38E24 ?
    --8D598530 ?
    843129B1 (TSAFS.NLM|ReadDataSet+521)
    --839ED3E4 ?
    --00000175 (LOADER.NLM|KernelAddressSpace+175)
    --00000001 (LOADER.NLM|KernelAddressSpace+1)
    --8077C2A0 ?
    --00000000 (LOADER.NLM|KernelAddressSpace+0)
    --8C64A580 ?
    --000041E8 (LOADER.NLM|KernelAddressSpace+41E8)
    --A8378DFE ?
    --839ED748 ?
    --00000000 (LOADER.NLM|KernelAddressSpace+0)
    --8C709038 ?
    --0000056C (LOADER.NLM|KernelAddressSpace+56C)
    --8421C6A8 ?
    --8C709020 ?
    8400AC8B (SMDR.NLM|NWSMTSReadDataSet+C4)
    --00000001 (LOADER.NLM|KernelAddressSpace+1)

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



  2. Re: Backup exec 9.2 NDMPD.nlm abends server

    John,

    Two things - AFAIK hyperthreading should always be disabled for Newtare as
    it is used only by Windows, and you need to backrev your SMDR.NLM as the one
    that came with the latest service pack is messed up. Try
    http://support.novell.com/cgi-bin/se...i?/2971717.htm for more
    information.

    Shivaji
    --
    Shivaji Samanta
    Wytheville Community College
    "John" wrote in message news:4419cc6a@ROSASTDMZ05....
    >
    > We are running Netware 6.5sp5, BackupExec 9.2. 1391
    >
    > Since upgrading to NW6.5 and BE 9.2 we are unable to get a backup. Server
    > abends every night in module NDMPD.nlm with page fault.
    > Server is patched to most recent level of NetWare and BackupExec. We are
    > only attempting FULL backups due to the Archive Bit problem. Abend log
    > entry
    > follows.
    >
    > Server config: IBM e345 dual xeon processor (hyperthreading enabled),
    > 4GB
    > RAM, SCSI RAID5
    >
    > Anyone else having/had this issue??
    >
    > ************************************************** *******
    > Novell Open Enterprise Server, NetWare 6.5
    > PVER: 6.50.05
    >
    > Server AGRHLN001 halted Thursday, March 16, 2006 12:09:42.238 am
    > Abend 1 on P00: Server-5.70.05: Page Fault Processor Exception (Error code
    > 00000000)
    >




  3. Re: Backup exec 9.2 NDMPD.nlm abends server

    In article <4419cc6a@ROSASTDMZ05.>, John wrote:

    > We are only attempting FULL backups due to the Archive Bit problem.


    FULL backup will always clear the archive bit. You can avoid it
    altogether by doing COPY backup. COPY just ignores the archive bit
    completely. Saves a smidge of time, too.

    I don't think that's the cause of the abend, but thought it was worth
    mentioning.

    As for hyperthreading on NetWare, it depends on the server and what it
    runs. If you have SMP-aware applications and more than one processor,
    then it's best to not use HT in my experience. What happens is that
    tasks are offloaded to the second logical processor, which is still the
    first physical processor. The second physical processor has very
    little load and the first one is overloaded.

    On single processor systems with no SMP apps, I have used HT
    successfully. The performance gain isn't spectacular, but it's
    noticeable for some processes.

    -Barry.



  4. Re: Backup exec 9.2 NDMPD.nlm abends server

    Barry,

    After I updated my servers for NW65sp5 I found that where my full backups
    were about 100GB, my daily differentials were about 60 GB - which does not
    make sense, as they were around 4 GB before the service pack was applied. I
    then found that of the three servers, ALL files were being backed up on the
    2 NW6.5sp5 servers and only the changed files on one NW6 server, so I guess
    that means that the archive bits were NOT being set in the weekly full
    backups for the two patched NW6.5 servers. TID 2971717 does indicate that
    one of the problems fixed in the TSA5UP18 release is "Archive date was not
    set on traditional volumes during backups" . Now I have all NSS volumes,
    but I think this was my problem, so I copied the files from the TSA5UP18
    release and the next week by differentials dropped back to ~4GB.

    Does that make sense, or am I barking up the wrong tree ?

    Shivaji
    --
    Shivaji Samanta
    Wytheville Community College
    "Barry St.John" wrote in message
    news:VA.0000012e.0f711cbc@adoanotfbugpme.org...
    > In article <4419cc6a@ROSASTDMZ05.>, John wrote:
    >
    >> We are only attempting FULL backups due to the Archive Bit problem.

    >
    > FULL backup will always clear the archive bit. You can avoid it
    > altogether by doing COPY backup. COPY just ignores the archive bit
    > completely. Saves a smidge of time, too.
    >
    > I don't think that's the cause of the abend, but thought it was worth
    > mentioning.
    >
    > As for hyperthreading on NetWare, it depends on the server and what it
    > runs. If you have SMP-aware applications and more than one processor,
    > then it's best to not use HT in my experience. What happens is that
    > tasks are offloaded to the second logical processor, which is still the
    > first physical processor. The second physical processor has very
    > little load and the first one is overloaded.
    >
    > On single processor systems with no SMP apps, I have used HT
    > successfully. The performance gain isn't spectacular, but it's
    > noticeable for some processes.
    >
    > -Barry.
    >
    >




  5. Re: Backup exec 9.2 NDMPD.nlm abends server

    Yeah, you're on the right track. My reply to John was in response to
    his comment about doing FULL backups because of the archive bit
    problem. Even with the buggy software if you do a FULL backup it's
    going waste cycles trying to clear and archive bit. So my point is if
    you don't care about the archive bit, then do a COPY backup.

    -Barry.


  6. Re: Backup exec 9.2 NDMPD.nlm abends server

    We are also running BE 9.2 R 1391 on a NW 6.5 SP5 box and we don't have any problems. We did awhile back turn off hyperthreading in the BIOS.

+ Reply to Thread