This post is more than 5 years old

15 Posts

5207

November 11th, 2013 22:00

NMM 3 and Networker 8.1 Hyper-V Backup

Hello,

We have upgrade the Backup server from 7.6 to 8.1.

We have also an hyper-v host OS Windows 2008 R2 and  we have upgrade the client from NMM 2.3 to NMM 3.

Now when I trying to start the group I get an error - NSR info nsrsnap_vss_save: Invalid argument: -g is specified without snap_sessionID

and the group failed.

please help

1.7K Posts

August 20th, 2014 06:00

Hello Cleto,

NMM doesn't honour the extra flags passed by the configuration in the group, the browse and retention have to be set at client level, and not group level.

Thank you,

Carlos

1.7K Posts

November 12th, 2013 07:00

Hi Dima,

Have you upgraded following these steps?:

1.- Uninstall NMM 2.3

2.- Uninstall NW 7.x client

3.- Install NW 8.1 client

4.- Install NMM 3.0

If so, can you please try the NMC wizard to change the client configuration and give it another try?

Can you please provide us with the full details of the client configuration in NMC?

Is it stand-alone or clustered Hyper-V server?

Thank you,

Carlos

15 Posts

November 12th, 2013 22:00

HI Carlos,

Thank you for your answer.

About the upgrade we first upgrade the client in place.

Yesterday, I a have

1.- Uninstall NMM 3.0

2.- Uninstall NW 8.1 client

3. Delete the folder in C:\Program Files\Leagato

4.- Install NW 8.1 client

5.- Install NMM 3.0

I have tried with NMC wizard to change the user. but no help

Client Configuration:

SaveSet - APPLICATIONS:\Microsoft Hyper-V

Backup Command - nsrsnap_vss_save.exe

Application Information - NSR_SNAP_TYPE=vss

The Hyper-V Server is a standalone Server.

Please Help

Best Regards

Dmitry

15 Posts

November 13th, 2013 00:00

Hi Carlos,

thank you for your reply,

This is the log -

52701 1384290572 1 0 0 8176 2380 0 "Hyper-V Host" nsrsnap_vss_save NSR notice 19 Command line:\n  %s 1 0 511 C:\Program Files\EMC NetWorker\nsr\bin\nsrsnap_vss_save.exe -A optype=conventional -A NSR_SAVE_FROM_SAVEGRP_NSRSNAP=Yes -A NSR_SNAP_TYPE=vss -A NSR_PARENT_JOBID=64042 -c "Hyper-V Host" -g Hyper-V -LL -m "Hyper-V Host" -s "Backup Server".icl-ips.com -y Tue Nov 26 23:09:02 GMT+0200 2013 -w Tue Nov 26 23:09:02 GMT+0200 2013 -t 1383847804 -l incr -q -W 78 -A snap_sessionid=1384290571 -A NSR_SAVE_FROM_SAVEGRP_NSRSNAP=Yes -A NSR_PS_DEBUG_ID=1384290571 -A NSRSNAP_JOBID=64045 APPLICATIONS:\Microsoft H

86738 1384290572 1 0 0 8176 2380 0 "Hyper-V Host" 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 1384290572 1 0 0 8176 2380 0 "Hyper-V Host" nsrsnap_vss_save NSR notice 40 Computer Name: %s     User Name: %s (%s) 3 12 7 "Hyper-V Host" 0 19 NT AUTHORITY\SYSTEM 13 6 SYSTEM

86745 1384290572 1 5 0 8176 2380 0 "Hyper-V Host" 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 9 3.0.0.282 44 36 NetWorker Module for Microsoft (x64)

91945 1384290572 0 0 0 8176 2380 0 "Hyper-V Host" nsrsnap_vss_save NSR info 78 nsrsnap_vss_save: The current installed NetWorker version for client %s is %s. 2 0 19 "Hyper-V Host" 0 3 8.1

52681 1384290572 0 0 0 8176 2380 0 "Hyper-V Host" nsrsnap_vss_save NSR info 28 NetWorker Server Version: %s 1 0 46 NetWorker 8.1.0.1.Build.199 Business Edition/8

50423 1384290572 0 0 0 8176 2380 0 "Hyper-V Host" nsrsnap_vss_save NSR info 85 nsrsnap_vss_save: Unknown Application Information parameter: %s, may not be supported 1 0 29 NSR_SAVE_FROM_SAVEGRP_NSRSNAP

50411 1384290572 0 0 0 8176 2380 0 "Hyper-V Host" nsrsnap_vss_save NSR info 77 nsrsnap_vss_save: Data mover host name not specified. Assuming local host: %s 1 12 19 "Hyper-V Host"

50412 1384290572 0 0 0 8176 2380 0 "Hyper-V Host" nsrsnap_vss_save NSR info 74 nsrsnap_vss_save: Invalid argument: -g is specified without snap_sessionID 0

62872 1384290572 0 0 0 8176 2380 0 "Hyper-V Host" nsrsnap_vss_save NSR info 108 nsrsnap_vss_save: snapvss_validateAparams()failed to validate one or more Application Information parameters 0

63309 1384290572 0 0 0 8176 2380 0 "Hyper-V Host" nsrsnap_vss_save NSR info 15 NMM .. bye bye. 0

Best Regards

Dmitry.

1.7K Posts

November 13th, 2013 00:00

Hi Dimitri,

Any chance to get a copy of the nmm.raw file rendered so that I can check the entire backup command sent to NMM?

Thank you,

Carlos

1.7K Posts

November 13th, 2013 02:00

Hi Dimitri,

Still I cannot see it clearly.

What about the configuration of the client, is it checked to be Deduplication Backup? Do you have the Data Domain backup check-box enabled? Do you have selected "IP".

Also I suppose this is stand-alone Hyper-V server, correct?

Also, about the wizard, you said "I used the wizard to change the user", do you mean to change the client?

Thank you,

Carlos

4 Operator

 • 

14.4K Posts

November 13th, 2013 02:00

I'm not an expert, but I like humor at the end with bye bye.  On more serious note, obviously issue is "-g Hyper-V" part.  I'm not an expert about NMM nor 8.1, but I suspect this might be backup type field or something similar.  Was this setup made with older NMM and now it is used with 3.0?  I ask this as setup may contain something which is depreciated in new version causing error.  Did you use wizard?  If yes, perhaps doing it manual would create different outcome.

Actually, I have to revisited what I said.  We see following info messages:

  • "Hyper-V Host" nsrsnap_vss_save NSR info 85 nsrsnap_vss_save: Unknown Application Information parameter: %s, may not be supported 1 0 29 NSR_SAVE_FROM_SAVEGRP_NSRSNAP
  • "Hyper-V Host" nsrsnap_vss_save NSR info 77 nsrsnap_vss_save: Data mover host name not specified. Assuming local host: %s 1 12 19 "Hyper-V Host"
  • "Hyper-V Host" nsrsnap_vss_save NSR info 74 nsrsnap_vss_save: Invalid argument: -g is specified without snap_sessionID 0
  • "Hyper-V Host" nsrsnap_vss_save NSR info 108 nsrsnap_vss_save: snapvss_validateAparams()failed to validate one or more Application Information parameters 0

The error really is "snapvss_validateAparams()failed to validate one or more Application Information parameters". And when I look above the only parameter is NSR_SAVE_FROM_SAVEGRP_NSRSNAP.  In another thread we have been told that means browse and retention policy overrides have been provided in the Advanced tab of the Group Properties and solution is to remove the overrides and re-run the backup it will work.  Check the link and give it a try (before Carlos comes back and gives you real solution as he usually does ).

15 Posts

November 13th, 2013 03:00

Dear Hrvoje Crvelin,

Thank you for your reply,

bye bye and failed succusfully is a great Massages

i tried what you write and its worked - i have remove the Brows and Retention Policy from the Group and its worked.

after that i had another issue with one of the VM's but i fixed it.

I have to say that the Browse and Retention Policy work fine on another groups.

Now I have a new question why it was not worked.

Maybe there was soem old configuration. can someone explain which configuration I need to so I will backup the hyper-v and the policy will be on the group.

15 Posts

November 13th, 2013 04:00

Hi Carlos,

We are doing the Backup to Tapes.

we do ot have or use Data Domain.

The Data Domain did not checked.

Yes it is the stand alone Hyper-V Host.

and Also you are correct that I Used the wizard in the NMC to change the client.

Best Reagrds

Dmitry

1.7K Posts

November 13th, 2013 04:00

Hi Dimitri,

The snapshot policies have changed from NW 7.x to NW 8.1, so that could be one of the reasons why it was failing.

Not sure what changed were don at browse/retention policies but, if using the wizard, you should be able to configure them correctly adopting valid NW 8.1 policies.

Thank you,

Carlos

4 Operator

 • 

14.4K Posts

November 13th, 2013 05:00

DimaV wrote:

Now I have a new question why it was not worked.

I wish I could answer, but I plan to scratch NMM and 8.1 only by the beginning of next year so until then workflow and configuration parameters remain mystery to me. With hint of what fixed it, it might be easier for other folks here to to reverse engineer what happened and provide answer.

2 Posts

August 20th, 2014 05:00

Removed group browse and  retention policies and it worked. I wonder why??

Top