NMM 8.2.1 EXCHANGE 2010

Question

I do have networker 8.2.1 nmm 8.2.1.

My exchange backups did ran 100% for months.. the hardware support people did a upgrade on the firmware on the exchnge server. When the server boot, the disk dis not present to the exchange box. after they fixed it my exchange backups failed witherror "cannot create replica.."

I then enter the parameter NSR_CHECK_JET_ERRORS= NONE and backup run smooth again. Pease help why did this fix the problem and what does thos parameter do.

sddc_guy · Accepted Answer

that is exactly wht you Need to do.

Since the Harware was not available, the Exchange Store could not be mounted and sends a error to the eventlog.

because we do not want to backup a "corruot" database, we do not start the backup if These Errors are in the log

That is the Default behviour of our irccd vss Client..

Save you log and clear all entries and you are fine

ble1 · Answer

In MDB restore doesn't work. Carlos Rojas said following:

NSR_CHECK_JET_ERRORS=values of backup failures

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 none.

I'm not EXCH guy, but based on what you said and above, I would argue that either (a) you had this enabled before or/and (b) NMM version you use does no longer use none as default assuming (c) what you said is correct - that this and only this parameter introduction leads to error free backup.

Now, normally you would expect backup to run without (c) so you posted this question - fair enough. Can you tell us if previously you had (a)? Also, what is the NMM version you run (along with build as there are two 8.2.1 versions out now)?

When you would get an error, can you show us what would event log catch?

ble1 · Answer

As noted above, we (you) must first figure out which error is triggering this.  Event logs or NMM logs might contain this information.  From there, once you know the error, isolating and fixing it is much easier ride.

javctn · Answer

HI thx for the response, how can I then get rid of these errors so that I can run without the parameter

javctn · Answer

thx for your response. So toeraticaly if I clear the event logs it might work.

javctn · Answer

Thank you very much. I verified this and it worked. Whala..

NetWorker

NMM 8.2.1 EXCHANGE 2010

Was this post helpful?