pba72

updated

6 years ago

P

pba72

1 Rookie

•

40 Posts

0

1568

October 16th, 2013 14:00

check edb file ?

Hello

I have a trouble with backup exchange 2010, there is error

83164:nsrsnap_vss_save:NMM .. An error was detected during the replica creation.  Details in nmm.raw on MAILBOX and in the Windows Application or System Event Log.

49931:nsrsnap_vss_save:RM .. 024178 ERROR:Terminating this job because there is a -1022 error in the eventlog (Event ID 439). E:\Exchange\db.edb may be corrupt. Repair or restore the file before restarting this job. Check the event in the application event log on MAILBOX for more information.

it seems that edb is correct .... no error in event log about corrupted edb file ....

Regards Pavel

  • TimQuan

    6 Operator

    •

    1242 Posts

    775

    1

    Posted October 16th, 2013 18:00

    Cause

    NMM checks the Windows Application Event log for possible errors.  NMM does this to prevent backing up a corrupted database. However, if the corruptoin has been repaired NMM backups will still fail because the JET errors still exist in the Windows Event logs from the previous instance.

    Resolution

    Make a copy of the current Application and System Event logs and clear these event logs, then retry the backup.

    Add the parameter, NSR_CHECK_JET_ERRORS, in the 'Application Information' (Apps & Modules tab) attribute of the client resource.  This parameter will change how NMM responds to such errors.  the following is the Application Guide help for the paraetmer for Exchange 2010...

    NSR_CHECK_JET_ERRORS=value

    Specifies the JET database errors to check for in the event log before taking a snapshot.
    Note: If errors are found, the snapshot fails. Values include the following:
      447 (Exchange Server 2007 only)
      448 (Exchange Server 2007 only)
      1018
      1019
      1022
      all
      none

    Values can be separated with a comma, for example:
    NSR_CHECK_JET_ERRORS=1018,1019
    The default is All.

  • pba72

    1 Rookie

    •

    40 Posts

    775

    0

    Posted October 17th, 2013 11:00

    In application logs there were records with event id 1022 (information and from another application ???). I cleared logs and backup now :-)

    many thanks