Please remember that the backup will NEVER run against the DAG client.
Also please note hat the backup has to be ran only against one node at a time, unless you set NSR_EXCH_BACKUP=passive or active in the 2 nodes (both should have the same value).
Based on the error message I think that the problem resides on the configuration of the client entry "MAHA-MUM-MB01", please check the aliases field of that client as well as in the client you are running the backup against. Check the daemon.raw on the client and you will find some further information (render it so you can read it).
As a minimum you should read NMM installation guide, configuration guide, application guide and release notes. They all contain important information and instructions you should be aware of.
yes , i was looking for an integarion agent for Exchange 2010 , still its not released i guess , so rest all VSS is a workaround and i will try again with checking all the paths
NMM 2.3 _is_ the integration agent for exchange 2010, you can perform backups and granular recovery if you set it up as described in the documentation. I don't think we'll see anything else in the near future.
How many Exchange servers are in your DAG cluster environment?
Did you install EMC Config Checker, EMC NetWorker client software and EMC NetWorker Module for Microsoft Applications on each member of DAG cluster?
Are there any errors in Config Checker results?
Also, on each server, run as administrator "Command Prompt" and type in: "nsrsnap_vss_save -?" (without quotes). Copy the result as these will be your Save sets when configuring "Backup Clients" on NetWorker server.
On NetWorker server create client resources for each DAG member, and client resource with the FQDN of dag cluster server. For each Networker client resource put recorded save sets (nsrsnap_vss_save). Client resource of FQDN dag name do not configure in any backup groups. In Apps&Modules tab, put nsrsnap_vss_save.exe in Backup command field, and fill in Apllication information box with these information:
NSR_SNAP_TYPE=vss
NSR_EXCH2010_BACKUP=active (or passive if backing up passive databases)
I didn't configure NMM for Exchange in a non-DAG environment, but as I can see in an official EMC documentation, setup is quite straight forward. You should not have any problems configuring backups.
Cosult EMC NetWorker Module for Microsoft Aplications Application Guide. You can download it from powerlink.emc.com, and then Support -> Technical Documentations And Advisories.
Thanks , its a small setup no DAG ,only one mailbox server and one CAS and mailbox are in a single database without DAG , i will try this on saturday and update you results thanks for support
For DAG environments I would recommend to use the following command to retrieve the valid savesets:
nsrsnap_vss_save -v -?
This will not only display the valid savesets, but will also show the status of the Exchange DB's (Active or passive).
This is quite important for the configuration, to avoid failures related to the configuration. For instance if you set NSR_EXCH2010_BACKUP=active, and the selected node is not hosting any active DB backup will fail, and you will need to look into the nmm.raw file (rendered) to find out the specific error message.
Also please consider this variable:
NSR_EXCH_RETAIN_SNAPSHOT=yes
This variable is intended only for cases where the snapshot policy is set to take more than one snapshot per day and not back it up to tape. This could also cause failures and, because of the complexity of the troubleshooting of NMM you would always try to avoid these kind of errors.
CarlosRojas
1.7K Posts
0
February 22nd, 2012 04:00
Hey Pratik,
Please remember that the backup will NEVER run against the DAG client.
Also please note hat the backup has to be ran only against one node at a time, unless you set NSR_EXCH_BACKUP=passive or active in the 2 nodes (both should have the same value).
Based on the error message I think that the problem resides on the configuration of the client entry "MAHA-MUM-MB01", please check the aliases field of that client as well as in the client you are running the backup against. Check the daemon.raw on the client and you will find some further information (render it so you can read it).
Let me know how it goes.
Thank you.
Carlos.
ble1
4 Operator
•
14.4K Posts
0
January 20th, 2012 08:00
The best approach would be to have support ticket opened then. You might get an answer here, but without knowing what you do it may cause more pain.
Panwar
79 Posts
0
January 20th, 2012 13:00
Hi Pratik
Please refer the forum link, it will help you in configuring Exchange 2010 backup with NMM 2.3.
https://community.emc.com/thread/120599
Regards
Panwar.
tonyalbers
75 Posts
0
January 21st, 2012 03:00
As a minimum you should read NMM installation guide, configuration guide, application guide and release notes. They all contain important information and instructions you should be aware of.
/tony
Zkk1
30 Posts
0
January 25th, 2012 03:00
I have downloaded and used read the guides but no valuable information it seems ,
Zkk1
30 Posts
0
January 25th, 2012 04:00
yes , i was looking for an integarion agent for Exchange 2010 , still its not released i guess , so rest all VSS is a workaround and i will try again with checking all the paths
i am very new to networker ,
tonyalbers
75 Posts
0
January 25th, 2012 04:00
Did you check the thread that Panwar wrote about?
/tony
tonyalbers
75 Posts
0
January 25th, 2012 04:00
NMM 2.3 _is_ the integration agent for exchange 2010, you can perform backups and granular recovery if you set it up as described in the documentation. I don't think we'll see anything else in the near future.
/tony
wmtW1BHxGX12559
1 Rookie
•
100 Posts
0
January 25th, 2012 04:00
How many Exchange servers are in your DAG cluster environment?
Did you install EMC Config Checker, EMC NetWorker client software and EMC NetWorker Module for Microsoft Applications on each member of DAG cluster?
Are there any errors in Config Checker results?
Also, on each server, run as administrator "Command Prompt" and type in: "nsrsnap_vss_save -?" (without quotes). Copy the result as these will be your Save sets when configuring "Backup Clients" on NetWorker server.
On NetWorker server create client resources for each DAG member, and client resource with the FQDN of dag cluster server. For each Networker client resource put recorded save sets (nsrsnap_vss_save). Client resource of FQDN dag name do not configure in any backup groups. In Apps&Modules tab, put nsrsnap_vss_save.exe in Backup command field, and fill in Apllication information box with these information:
NSR_SNAP_TYPE=vss
NSR_EXCH2010_BACKUP=active (or passive if backing up passive databases)
NSR_EXCH2010_DAG=dag.ecample.com
NSR_EXCH_RETAIN_SNAPSHOTS=yes
NSR_ALT_PATH=C:\NMMSnapshot
Hope this helps...
wmtW1BHxGX12559
1 Rookie
•
100 Posts
0
January 25th, 2012 05:00
I didn't configure NMM for Exchange in a non-DAG environment, but as I can see in an official EMC documentation, setup is quite straight forward. You should not have any problems configuring backups.
Cosult EMC NetWorker Module for Microsoft Aplications Application Guide. You can download it from powerlink.emc.com, and then Support -> Technical Documentations And Advisories.
Good luck!
Zkk1
30 Posts
0
January 25th, 2012 05:00
Thanks and what is the parameter in save set is it the same APPLICATIONS:\Microsoft Exchange 2010 or different
Zkk1
30 Posts
0
January 25th, 2012 05:00
Thanks , its a small setup no DAG ,only one mailbox server and one CAS and mailbox are in a single database without DAG , i will try this on saturday and update you results thanks for support
wmtW1BHxGX12559
1 Rookie
•
100 Posts
0
January 25th, 2012 05:00
Most certainly, it is. But, again, check with "nsrsnap_vss_save -?" on Exchange mailbox server.
CarlosRojas
1.7K Posts
0
January 25th, 2012 22:00
Hi all,
For DAG environments I would recommend to use the following command to retrieve the valid savesets:
nsrsnap_vss_save -v -?
This will not only display the valid savesets, but will also show the status of the Exchange DB's (Active or passive).
This is quite important for the configuration, to avoid failures related to the configuration. For instance if you set NSR_EXCH2010_BACKUP=active, and the selected node is not hosting any active DB backup will fail, and you will need to look into the nmm.raw file (rendered) to find out the specific error message.
Also please consider this variable:
NSR_EXCH_RETAIN_SNAPSHOT=yes
This variable is intended only for cases where the snapshot policy is set to take more than one snapshot per day and not back it up to tape. This could also cause failures and, because of the complexity of the troubleshooting of NMM you would always try to avoid these kind of errors.
Thank you.
Carlos.
Zkk1
30 Posts
0
January 27th, 2012 21:00
HI
These are the results
C:\Windows\system32>nsrsnap_vss_save -?
NMM .. changing backup name SCOAS-MBX1 to primary name scoas-mbx1.soharcollege f
or multi NIC client.
List of valid saveset entries for APPLICATIONS on client scoas-mbx1.soharcollege
...
Initializing data to display...
NMM ... Using client name SCOAS-MBX1, the version of the Exchange server is Exch
ange 2010.
"APPLICATIONS:\Microsoft Exchange 2010"
79598:nsrsnap_vss_save:NMM .. Exchange2010 Shell Object reference not set to an
instance of an object.
"APPLICATIONS:\Microsoft Exchange 2010\Public Folder Database 0904658189"
"APPLICATIONS:\Microsoft Exchange 2010\Mailbox Database 1114983022"
68150:nsrsnap_vss_save:nsrsnap_vss_save: Exiting with success.
and i created client with
APPLICATIONS:\Microsoft Exchange 2010\Public Folder Database 0904658189
APPLICATIONS:\Microsoft Exchange 2010\Mailbox Database 1114983022"
in backup command
addded nsrsnap_vss_save.exe
NSR_SNAP_TYPE=vss
NSR_EXCH2010_BACKUP=active
NSR_EXCH_RETAIN_SNAPSHOTS=yes
NSR_ALT_PATH=D:\NMMSnapshot
in a minute it gives failure result
with
savegrp: suppressed 2 lines of verbose output
Original file name: nsrsnap_vss_save.exe
Version: 2.3.0.87
Comments: NetWorker Module for Microsoft Applications (x64)
67112:nsrsnap_vss_save:nsrsnap_vss_save: Missing parameter: No -A parameters were specified.
67740:nsrsnap_vss_save:nsrsnap_vss_save: Ensure that 'Snapshot' is selected in Group entry in NMC.
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.