Unsolved

This post is more than 5 years old

3 Posts

3525

January 10th, 2017 00:00

EMC networker 9.0.1 log files size

Hello everyone,

we have implemented a backup sollution based on EMC Networker and EMC DATA DOMAIN 2500 to save and restore VM on Microsoft Failover cluster (using Hyper-v version 3.0 on windows server 2012 datacenter x64 edition), we got a problem with the nsrnmmsv.raw files which is grow very fast (it's size now exceed 10 Go).

so, what is the source of this problem, and how i can resolve it.

Hope that you give me an ansewer as soon as possible.

thank you.

2.4K Posts

January 10th, 2017 02:00

I am pretty sure you will be asked first what your actual NMM version is. If it was a production relase you will be asked to update (NW and NMM) please be aware that you should run the latest 'cumulative hotfixes' version 9.0.1.6 for both products which has been relased yesterday.

3 Posts

January 10th, 2017 02:00

Hello,

thank you for the ansewer, i think my current NMM version is 3.0, and the current version of NW is 9.0.1.0, Now i will check the cumulative hotfixes release note. in order to confirm the cause of problem.

thanks again.

26 Posts

January 10th, 2017 02:00

Hi,

First thing you should check is if the backup is using a debug mode, to check that go to the client in NMC and check if there is : nsrnmmsv -DX (where X is a debug level), you should remove -DX so that the debugging is disabled.

Note : Debugging make the log files really big, so you should only use it for troubleshooting.

Good Luck

155 Posts

January 11th, 2017 05:00

Cant believe NMM 3.0 is working with NW server 9.0.1.0. It will be good to you same level of NMM version as that of your NW server. Huge nsrnmmsv.raw files will be because of the debug parameter used as mentioned earlier by Largou

3 Posts

January 11th, 2017 07:00

hello,

i'm sorry the nmm version is nmm 9.0.1.614.

Thank you

2.4K Posts

January 11th, 2017 10:00

I am pretty sure that NMM 3.0 will work with NW server 9.0.1.0 ... as long an appropriate NW client version will be used.

However, such combination might not be supported because it most likely will not have been tested.

I briefly looked through the Compatibility Guide. Unfortunately, you cannot use a 'reverse view' (enter the NW software version and find out the other supported components). For NMM 3.0 it seems that this version is only supported up to a NW 8.1 client.

155 Posts

January 12th, 2017 00:00

I haven't tested this, hence cant talk much about it.....but NMM 9.x uses nsrnmmsv binary to trigger a backup on the other hand NMM 3.0 uses  nsr_vss_save.

155 Posts

January 12th, 2017 00:00

melloul Did you get a chance to check debug ?

1.7K Posts

January 12th, 2017 01:00

Hello melloul

First, you need to make sure NW client and NMM versions are the exact same version and build.

Second, please check whether you have any debug set in the debug command, as already mentioned in previous posts (nsrnmmsv.exe -Dx) if so please remove the -Dx option (where x is a number from 1 to 9).

Also check whether you have the following viable applied within the application information field of the client configuration:

NSR_PS_DEBUG_LEVEL=x

If so please remove it from the client configuration.

And last, as already asked as well, please check if you have any file under:

C:\Program Files\EMC NetWorker\nsr\debug

Thank you,

Carlos

6 Operator

 • 

14.4K Posts

 • 

56.2K Points

January 15th, 2017 17:00

I guess the first thing I would do is to check what is inside the log and to try to see which message(s) are flooding the log. Based on that, it would be easier to say anything else...

No Events found!

Top