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

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"

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

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.

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.

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.

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

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.