This post is more than 5 years old

3 Posts

11958

October 6th, 2012 16:00

Networker 8.0 - Backup Windows 2008R2 with NMM 2.4

Hello,

We are evaluating Networker and I have a problem with NMM client.

I'm trying to backup a Windows 2008 R2, using NMM 2.4.

The errors I'm getting for both C:\ and SYSTEM COMPONENTS:\ are:

------------------------------

73064:nsrsnap_vss_save:Version information for C:\Program Files\EMC NetWorker\nsr\bin\nsrsnap_vss_save.exe:

    Original file name: nsrsnap_vss_save.exe

    Version: 2.4.0.375

    Comments: NetWorker Module for Microsoft Applications (x64)

50423:nsrsnap_vss_save:nsrsnap_vss_save: Unknown Application Information parameter: device interface, may not be supported

50410:nsrsnap_vss_save:nsrsnap_vss_save: Must provide Application Information NSR_SNAP_TYPE value

62872:nsrsnap_vss_save:nsrsnap_vss_save: snapvss_validateAparams()failed to validate one or more Application Information parameters

68151:nsrsnap_vss_save:nsrsnap_vss_save: Exiting with failure.

------------------------------

The client is configured with Backup command: nsrsnap_vss_save.exe and Application information:

NSR_SNAP_TYPE=vss

NSR_IGNORE_MISSING_SYSTEM_FILES=yes

NSR_DEVICE_INTERFACE=DATA_DOMAIN

NSR_DIRECT_ACCESS=Yes

I've also tried only with NSR_SNAP_TYPE=vss, but got the same error.

VSS Service is running.

If i'm doing backup only with Networker client, everything works smoothly, but with NMM I never got a backup running.

Could you point me to the right direction? I don't know what I'm doing wrong.

Thank you,

CR

6 Posts

October 8th, 2012 05:00

Hi,

We are also in the mids of evaluating Networker 8 and NMM 2.4 with EMC. So far these are the findings:

- For clients with DB (SQL2005,2008,2012) needs to be backed up with NMM (File system and database). To be able to DR recovery purpose, you need to create 3 separate groups for a single client.

  • Filesystem for NMM group - backup command as you use above

     Backup command: nsrsnap_vss_save.exe

     App Information:

     NSR_SNAP_TYPE=VSS

     NSR_IGNORE_MISSING_SYSTEM_FILES=YES

  • Group to backup DISASTER_RECOVERY:\ only - normal backup command
  • Normal MSSQL group.

- NMM Admin Guide, Page 77: In the users attribute, add the following values for the NMM client hosts

      User=administrator, host=NMM_client_host

     User=system, host=NMM_client_host

- and make sure the NMM group configuration is set to these (Thanks to Carlos from the other thread)

=========================================================

Inactivity time out: This has to be set to "0" (unlimited) to prevent time outs in the group when the snapshot is being taken. Big snapshots can take long time to be created.

Savegrp parallelism: set to "0" as the parallelism should be set at client level for NMM backups.

Client retries: has to be set to "0" so that there are not more than one call to VSS, otherwise backup will fail as snapshot is already in progress.

===========================================================

Hope thats help.

4 Operator

 • 

14.3K Posts

October 7th, 2012 07:00

Is there any reason why would you use NMM to backup file system of the client at all?

3 Posts

October 7th, 2012 10:00

On that server, we've installed SQL2008 and then installed NMM to test backup of databases.

After that, backup of filesystem said: "You have NMM installed, please use NMM to configure backup"

4 Operator

 • 

14.3K Posts

October 7th, 2012 10:00

Ah ok, now I understand.  I know in the past if you had NMM you had to use it for fs backup since it replaced client software.  I believe this has been changed in 2.4 (at least I hope so) so there is no need to use NMM for file system backup part (only SQL and that one will most likely use SQL module which is now integrated with NMM so you can use VDI instead of VSS - unless you do not plan to protect SQL database with transaction logs).

3 Posts

October 7th, 2012 23:00

Actually it hasn't changed.

I performed a succesfull backup with traditional client for FS, then I've installed NMM 2.4.

When I try to perform a backup to the FS, it shoots following error:

------------------------------------------------------------------------------

89998:save:The NetWorker Module for Microsoft is installed. Configure the backup with NetWorker Module for Microsoft Applications program only.

Failed with error(s)

------------------------------------------------------------------------------

So I configured it, by adding

Backup command: nsrsnap_vss_save.exe

App Information:

NSR_SNAP_TYPE=VSS

NSR_IGNORE_MISSING_SYSTEM_FILES=YES

When I try to backup:

--------------------------------------------------------------

73064:nsrsnap_vss_save:Version information for C:\Program Files\EMC NetWorker\nsr\bin\nsrsnap_vss_save.exe:

    Original file name: nsrsnap_vss_save.exe

    Version: 2.4.0.375

    Comments: NetWorker Module for Microsoft Applications (x64)

50423:nsrsnap_vss_save:nsrsnap_vss_save: Unknown Application Information parameter: DIRECT_ACCESS, may not be supported

50410:nsrsnap_vss_save:nsrsnap_vss_save: Must provide Application Information NSR_SNAP_TYPE value

62872:nsrsnap_vss_save:nsrsnap_vss_save: snapvss_validateAparams()failed to validate one or more Application Information parameters

68151:nsrsnap_vss_save:nsrsnap_vss_save: Exiting with failure.

--------------------------------------------------------------

The group has no snapshot configured.

Client has Client Direct and DataDomain unchecked.

4 Operator

 • 

14.3K Posts

October 8th, 2012 10:00

I thought DISASTER_RECOVERY saveset was enhanced in NW8 in a way that one pass backup was needed and further incrementals could go against it.  In such case, you would need two instead of 3 groups.

1.7K Posts

October 9th, 2012 00:00

Hi Hrvoje,

You are right about the improvement of DISASTER_RECOVERY saveset in NW 8 however NMM still needs to separate VSS based backups and DISASTER_RECOVERY (ASR) based backups.

We still need to create 3 groups as stated by Iman18.

Thank you.

Carlos.

4 Operator

 • 

14.3K Posts

October 9th, 2012 01:00

Ah I see... the code change in NW8 is not what is found in NMM.  Well, if they could just make it package just like NMDA so that you can still use core NW, that would be great.  Few weeks ago person from EMC claimed that was made, but I guess that was not correct statement (or at least that person who told me that was under wrong impression).

70 Posts

February 23rd, 2013 19:00

Hi All

I have did the same exact way to backup File systems

- For clients with DB (2012) i tryed the following things

1    Filesystem for NMM group - saveset-unchecked disaster recovery only or do i need to try -All here ?

       Backup command: nsrsnap_vss_save.exe    

       App Information:     NSR_SNAP_TYPE=VSS     NSR_IGNORE_MISSING_SYSTEM_FILES=YES

2     Group to backup DISASTER_RECOVERY:\ and critical drives and what backup command i have to use here ?

3      Normal MSSQL group.Can you please let me know these group and client property details also how you configured my next test will be this SQL DB 2012           Read only db test

Can someone help me out on this as i am new to NW and trying to do POC .

Thank you.

No Events found!

Top