Start a Conversation

This post is more than 5 years old

Solved!

Go to Solution

3529

May 28th, 2014 02:00

NMM 3.0.1 Exchange 2010 SP3 RU5 Backup Failing

Hi All,

We cannot seem to backup Exchange 2010 SP3 RU5 ever since the networker server was upgraded to 8.1

previously we were running NMM 2.3 and client version was 7.5 which was backing up all DB's fine on this exchange version.

Now when we attempt to run a backup we get the following

List of valid saveset entries for APPLICATIONS on client server1.company.com

...

Initializing data to display...

NMM ... Using client name SERVER01, the version of the Exchange server is Exch

nge 2010.

86738 1401265704 1 0 0 8180 6668 0 server1.company.com nsrsnap_vss_save NSR notice 33 System Version: %d.%d Build %d %s 4 1 1 6 1 1 1 1 4 7601 44 1 S

86741 1401265704 1 0 0 8180 6668 0 server1.company.com nsrsnap_vss_save NSR notice 40 Computer Name: %s     User Name: %s (%s) 3 12 9 SERVER01 0 19 NT AUTHORITY\SYSTEM 13 6 SYSTEM

86745 1401265704 1 5 0 8180 6668 0 server1.company.com nsrsnap_vss_save NSR notice 81 Version information for %s:\n Original file name: %s\n Version: %s\n Comments: %s 4 23 59 C:\Program Files\EMC NetWorker\nsr\bin\nsrsnap_vss_save.exe 23 20 nsrsnap_vss_save.exe 44 11 3.0.1.2.280 44 47 Supporting Microsoft Volume Shadow Copy Service

102317 1401265704 0 0 0 8180 6668 0 server1.company.com nsrsnap_vss_save NSR info 60 The current installed NetWorker version for client %s is %s. 2 0 13 SERVER01-bck 0 5 8.1.1

0 1401265704 1 0 0 8180 6668 0 server1.company.com nsrsnap_vss_save NSR notice 71 NMM .. changing backup name %s to primary name %s for multi NIC client. 2 0 13 SERVER01-bck 0 22 server1.company.com

52681 1401265704 0 0 0 8180 6668 0 server1.company.com nsrsnap_vss_save NSR info 28 NetWorker Server Version: %s 1 0 71 NetWorker 8.1.1.3.Build.289 NetWorker Source Capacity Data Zone Enabler

102357 1401265704 0 0 0 8180 6668 0 server1.company.com nsrsnap_vss_save NSR info 67 Unknown Application Information parameter: %s, may not be supported 1 0 29 NSR_SAVE_FROM_SAVEGRP_NSRSNAP

102357 1401265704 0 0 0 8180 6668 0 server1.company.com nsrsnap_vss_save NSR info 67 Unknown Application Information parameter: %s, may not be supported 1 0 29 NSR_SAVE_FROM_SAVEGRP_NSRSNAP

102345 1401265704 0 0 0 8180 6668 0 server1.company.com nsrsnap_vss_save NSR info 59 Data mover host name not specified. Assuming local host: %s 1 12 22 server1.company.com

102324 1401265705 0 0 0 8180 6668 0 server1.company.com nsrsnap_vss_save NSR info 28 Inserting %s in saveset list 1 0 37 APPLICATIONS:\Microsoft Exchange 2010

102338 1401265705 0 0 0 8180 6668 0 server1.company.com nsrsnap_vss_save NSR info 51 Backup is level FULL. Set GLR compatibility to YES. 0

80271 1401265705 0 0 0 8180 6668 0 server1.company.com nsrsnap_vss_save NSR info 137 NMM .. Valid snapshot policy. Group: "%s" Snapshot Policy: "%s" Snapshots Per Day: "%s"  Retain: "%s" Backup Snapshots: "%s" Level: "%s". 6 0 29 OCN0213-0002-COMPANY-EXC2 0 12 RolloverOnly 0 1 1 0 1 0 0 3 All 0 4 full

98101 1401265705 5 0 0 8180 6668 0 server1.company.com nsrsnap_vss_save NSR critical 102 NMM ... incorrect saveset name specified.  Please specify the correct Exchange version in the saveset. 0

80875 1401265705 0 0 0 8180 6668 0 server1.company.com nsrsnap_vss_save NSR info 43 NMM snapshot backup completed successfully. 0

102329 1401265705 0 0 0 8180 6668 0 server1.company.com nsrsnap_vss_save NSR info 29 createInstanceBackup() failed 0

0 1401265705 3 0 0 8180 6668 0 server1.company.com nsrsnap_vss_save NSR error 11 %s: failed  1 0 37 APPLICATIONS:\Microsoft Exchange 2010

63309 1401265705 0 0 0 8180 6668 0 server1.company.com nsrsnap_vss_save NSR info 15 NMM .. bye bye. 0

102333 1401265705 3 0 0 8180 6668 0 server1.company.com nsrsnap_vss_save NSR error 21 Exiting with failure. 0

63309 1401266692 0 0 0 1980 3776 0 server1.company.com nsrsnap_vss_save NSR info 15 NMM .. bye bye. 0

102333 1401266692 3 0 0 1980 3776 0 server1.company.com nsrsnap_vss_save NSR error 21 Exiting with failure. 0

3088 98101 28/05/2014 09:28:25 DEBUG 6668 0 nsrsnap_vss_save NSR critical NMM ... incorrect saveset name specified.  Please specify the correct Exchange version in the saveset.

I read through the compatibility guide and can see that only up to 2010 SP3 RU4 is supported, however reading through various articles on this site i can see others are running RU5 without issues.

Has anyone please encountered this issue and if so how do i resolve it, i cannot find anything for "Please specify correct exchange version in the save saveset"

when i do a nsrsnap_vss_save -v -?

96585:nsrsnap_vss_save:NMM .. Initialization success -- Exchange shell successf

lly initialized. Required for Exchange 2010 or Exchange 2013.

96585:nsrsnap_vss_save:NMM .. Initialization success -- Exchange shell successf

lly initialized. Required for Exchange 2010 or Exchange 2013.

APPLICATIONS:\Microsoft Exchange 2010"

"APPLICATIONS:\Microsoft Exchange 2010\DB7 -- Passive"

"APPLICATIONS:\Microsoft Exchange 2010\DB6 -- Passive"

"APPLICATIONS:\Microsoft Exchange 2010\DB1 -- Passive"

"APPLICATIONS:\Microsoft Exchange 2010\DB10 -- Passive"

"APPLICATIONS:\Microsoft Exchange 2010\DB11 -- Passive"

"APPLICATIONS:\Microsoft Exchange 2010\DB4 -- Passive"

"APPLICATIONS:\Microsoft Exchange 2010\DB2 -- Passive"

"APPLICATIONS:\Microsoft Exchange 2010\DB8 -- Passive"

"APPLICATIONS:\Microsoft Exchange 2010\DB3 -- Passive"

"APPLICATIONS:\Microsoft Exchange 2010\DB9 -- Passive"

"APPLICATIONS:\Microsoft Exchange 2010\PF2 -- Standalone"

"APPLICATIONS:\Microsoft Exchange 2010\DB5 -- Active"

102332:nsrsnap_vss_save:Exiting with success.

We have tried adding APPLICATIONS:\Microsoft Exchange 2010 to save and trying on the DB level to for example APPLICATIONS:\Microsoft Exchange 2010\DB7 -- Passive nothing seems to work.

5 Posts

June 11th, 2014 07:00

Problem was resolved EMC provided us with a binary to replace it was the nmm_vss_save.exe if memory recalls correctly fixed all our issues.

Can backup exchange SP3 CU5 fine now.

5 Posts

May 28th, 2014 02:00

Networker client version is 8.1.1.5

4 Operator

 • 

1.3K Posts

May 28th, 2014 03:00

GovinderM,

Have you tried reaching the support yet ? Looks like NetWorker is assuming you have a different version of Exchange on your machine !!

5 Posts

May 28th, 2014 03:00

Yes NMM is running on 3.0.1 and networker client is 8.1.1.5

and we did a clean uninstall of 2.3 and then rebooted and installed 3.0.1 couple of times now

79 Posts

May 28th, 2014 03:00

Did you also upgrade NMM to 3.01? Unless I'm mistaken, this requires a clean uninstall of NMM 2.3 and then a fresh install of 3.01.

5 Posts

May 28th, 2014 04:00

Yep call is raised with support but not getting anywhere at the moment. Exchange log files are filling up the drives fast as they are not being truncated hence i thought i'd post here see if i can get a responce from someone who may have a simular problem.

I think being on 2010 SP3 Rollup 5 is the issue and maybe NMM see's this has too new? don't know

We cannot roll back the RU5 to RU4 which is supported as we operate in a  2012 R2 AD domain which is only supported by exchange RU5.

June 9th, 2014 18:00

Please can you post the contents of the Application Information field in the second tab of the client configuration

June 9th, 2014 18:00

I was advised a couple of weeks back that RU5 has been qualified and will be listed in the next version of the Software Compatibility Guide

1.7K Posts

June 11th, 2014 07:00

Hi Govinder,

Can you please share with us the following information?:

- Screenshot of all tabs of Exchange client configuration.

- List of all values entered in Application Information field.

- Rendered output of nmm.raw from Exchange client, or attach the entire nmm.raw file.

Is this a DAG or stand-alone Exchange environment?

What is the version of NetWorker server (please specify version and build).

Thank you,

Carlos

30 Posts

August 5th, 2014 07:00

Hi,

It looks like I have the same situation. Does anybody can confirm?

avegrp: suppressed 13 lines of verbose output

NMM ... Using client name MAIL-MSP, the version of the Exchange server is Exchange 2010.

96585:nsrsnap_vss_save:NMM .. Initialization success -- Exchange shell successfully initialized. Required for Exchange 2010 or Exchange 2013.

98101:nsrsnap_vss_save:NMM ... incorrect saveset name specified.  Please specify the correct Exchange version in the saveset.

80875:nsrsnap_vss_save:NMM snapshot backup completed successfully.

Internal error.

68151 1407247648 2 0 0 8504 8988 0 name.dmn nsrsnap_vss_save NSR warning 39 nsrsnap_vss_save: Exiting with failure. 0

P, may not be supported

50411:nsrsnap_vss_save:nsrsnap_vss_save: Data mover host name not specified. Assuming local host: name.dmn

89199:nsrsnap_vss_save:nsrsnap_vss_save: Backup is level FULL. Set GLR compatibility to YES.

4 Operator

 • 

1.3K Posts

August 5th, 2014 08:00

You might have to reach out to support for the patched binary.

30 Posts

August 5th, 2014 23:00

Thank you very much. Asked EMC for file

No Events found!

Top