NMM 8.2.1 client configuration for MS exchange 2013 backup

Mount Location is required for Consistency checking, Please remember to provide a folder path to the mount location which is common for all the hosts under the DAG, for Example D:\NMM, please remember to mention the folder name not only the drive letter.

If you are checking the Check box for consistency check then during the consistency check the mount location will be used, if you don't use the consistency check check box then the folder will not be used any time. But this is mandatory to provide the mount location.

Note : If you enable consistency checking then the backup time will be lenthy because before backing up the consistency of the database will be checked.

cant´t blieve this is your DAG Server:FRQDN Name " DAG01.16.1.87"  .... please use the FQDN

Hello deb,

as you said i have created one folder with the name Mount in Drive  C:  and completed client configuration successful and then when i was triggered back up it is giving below error.

Below i have attached notepad as well for client log

i'm not getting you  exactly can you please elaborate a bit more HyperV_Guy

The DAG Name you have given it is unable to execute it sounds like.

1. What is the NetBIOS name of the DAG?
2. What is the Fully Qualified Domain Name of the DAG?
3. is the DAG Name FQDN / NetBIOS name is resolving in DNS properly? please try to ping the Dag name from your Backup server and check if the Dag Name is proper,

@Deb

now i'm getting below error while i am trying to take backup

after i fixed the FQDN error for DAG and i have created snapshot policy for this backup with

1)snopshots to be taken set to 1

2) retain=0  

3) back up of snapshots to device = all

even though it is giving error like below

please help me in regards of snapshot policy for this backup.

Regards,

sk_kavala

I do not see any error given in your reply, you can use Rollover Snapshot policy in the Group properties of Dag, and assign the Media Pool where you are planning to send the Exchange backup as snapshot pool

Please like my post if you like it, please mark my reply "helpful" if it helps to understand the question, Please mark reply as "Correct Answer" if it resolves your query

Deb,

i can't able to take backup of exchange due to below error

79248:nsrsnap:Ignoring unrecognized option 'q', use '-?' to see usage

92347:nsrsnap:***************** Snapshot Management operation has started, logging to "C:\Program Files\EMC NetWorker\nsr\logs\nwsnap.raw" *****************05/15/15 10:45:06.033398 [nsr/save/nsrsnap.c 611] Calling nsrrm_host

05/15/15 10:45:06.064579 [nsr/save/nsrsnap.c 886] Calling get_pool_name..

52051:nsrsnap:Printing savecmd=nsrsnap_vss_save after parsing

05/15/15 10:45:06.267710 [nsr/save/nsrsnap.c 1693] Calling snap_wait..

APPLICATIONS:\Microsoft Exchange 2013

05/15/15 10:45:31.315186 [nsr/save/nsrsnap.c 1714] Calling parse_fs_logs_and_prefix..

107092: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: 8.2.1.0.681 Comments: Supporting Microsoft Volume Shadow Copy Service

102357:nsrsnap_vss_save:Unknown Application Information parameter: NSR_SAVE_FROM_SAVEGRP_NSRSNAP, may not be supported

102357:nsrsnap_vss_save:Unknown Application Information parameter: NSR_SAVE_FROM_SAVEGRP_NSRSNAP, may not be supported

102345:nsrsnap_vss_save:Data mover host name not specified. Assuming local host: rci-has-mbx02.hastinapur.res

102338:nsrsnap_vss_save:Backup is level FULL. Set GLR compatibility to YES.

80271:nsrsnap_vss_save:NMM .. Valid snapshot policy. Group: "DAG" Snapshot Policy: "RolloverOnly" Snapshots Per Day: "1"  Retain: "0" Backup Snapshots: "All" Level: "full".

NMM ... Using client name RCI-HAS-MBX02, the version of the Exchange server is Exchange 2013.

136553:nsrsnap_vss_save:NMM .. Exchange2010 Shell interface is unavailable. This may indicate that the EMC powershell library was not properly registered.

96585:nsrsnap_vss_save:NMM .. Initialization success -- Exchange shell successfully initialized. Required for Exchange 2010 or Exchange 2013.

136584:nsrsnap_vss_save:NMM .. Exchange Shell Exception  in function GetServersDAG

136553:nsrsnap_vss_save:NMM .. Exchange2010 Shell interface is unavailable. This may indicate that the EMC powershell library was not properly registered.

136584:nsrsnap_vss_save:NMM .. Exchange Shell Exception  in function GetServersDAG

136553:nsrsnap_vss_save:NMM .. Exchange2010 Shell interface is unavailable. This may indicate that the EMC powershell library was not properly registered.

136584:nsrsnap_vss_save:NMM .. Exchange Shell Exception  in function GetServersDAG

136584:nsrsnap_vss_save:NMM .. Exchange Shell Exception  in function GetServersDAG

136553:nsrsnap_vss_save:NMM .. Exchange2010 Shell interface is unavailable. This may indicate that the EMC powershell library was not properly registered.

136584:nsrsnap_vss_save:NMM .. Exchange Shell Exception  in function GetServersDAG

136553:nsrsnap_vss_save:NMM .. Exchange2010 Shell interface is unavailable. This may indicate that the EMC powershell library was not properly registered.

136584:nsrsnap_vss_save:NMM .. Exchange Shell Exception  in function GetServersDAG

89403:nsrsnap_vss_save:NMM ..DAG name DAG01.hastinapur.res entered for client not in a DAG. Cannot continue, please check spelling and name resolution.

37959:nsrsnap_vss_save:The group or resource is not in the correct state to perform the requested operation.

63335:nsrsnap_vss_save:NMM backup failed to complete successfully.

Internal error.

102333 1431666927 3 0 0 5828 14780 0 rci-has-mbx02.hastinapur.res nsrsnap_vss_save NSR error 21 Exiting with failure. 0

APPLICATIONS:\Microsoft Exchange 2013: Backup of [APPLICATIONS:\Microsoft Exchange 2013] failed

Please ignore my last post.. Although the error reported i have highlighted is correct. Please check the below things for resolution

Step 1.

Try to re-register NetWorker Power Shell library for Exchange:

Open command prompt and cd to following location: C:\Windows\Microsoft.NET\Framework64\v4.0.30319

Then run following command: regasm "xxx\EMC NetWorker\nsr\bin\libnmexchmgmt.dll"
***Replace xxx with NetWorker installation path (e.g. C:\Program Files)


If this is not resolving the issue then follow step 2 otherwise you can ignore the step


Step 2.

On NetWorker Server perform following action

• Start the command prompt as administrator
• Stop the services: net stop nsrexecd
• Kill the stale services: taskkill /f /im nsr*
• Go to 'nsr' directory and rename 'tmp' and /res/jobsdb folder
• Restart the services: net start nsrd & net start gstd

136553:nsrsnap_vss_save:NMM .. Exchange2010 Shell interface is unavailable. This may indicate that the EMC powershell library was not properly registered.

136584:nsrsnap_vss_save:NMM .. Exchange Shell Exception  in function GetServersDAG

136553:nsrsnap_vss_save:NMM .. Exchange2010 Shell interface is unavailable. This may indicate that the EMC powershell library was not properly registered.

Refer to the KB Article

https://support.emc.com/kb/169852

I think you have a problem here “136553:nsrsnap_vss_save:NMM .. Exchange2010 Shell interface is unavailable. This may indicate that the EMC powershell library was not properly registered.”

Please check the below things for resolution

Step 1.

Try to re-register NetWorker Power Shell library for Exchange:

Open command prompt and cd to following location: C:\Windows\Microsoft.NET\Framework64\v4.0.30319

Then run following command: regasm "xxx\EMC NetWorker\nsr\bin\libnmexchmgmt.dll"

***Replace xxx with NetWorker installation path (e.g. C:\Program Files)

If this is not resolving the issue then follow step 2 otherwise you can ignore the step

Step 2.

On NetWorker Server perform following action

· Start the command prompt as administrator

· Stop the services: net stop nsrexecd

· Kill the stale services: taskkill /f /im nsr*

· Go to 'nsr' directory and rename 'tmp' and /res/jobsdb folder

· Restart the services: net start nsrd & net start gstd

Thanks..

Deb | Debabrata Chakraborty

EMCISA, EMCIE - Data Domain, EMCIE - NetWorker, MCITP, MCTS, MCSA, CCNA

EMC NetWorker, EMC Data Domain, Symantec NetBackup

Please Like my Post if you liked it, Please Mark it as Helpful if it helped you, and mark it as Correct Answer if it resolved your query

Deb,

i haven't performed any of your suggestion for diagnosis despite error has been changed again

kindly have a look at below error

************************************DAG 2013******************************************************

92347:nsrsnap:***************** Snapshot Management operation has started, logging to "C:\Program Files\EMC NetWorker\nsr\logs\nwsnap.raw" *****************05/21/15 11:45:54.109878 [nsr/save/nsrsnap.c 611] Calling nsrrm_host

05/21/15 11:45:54.141115 [nsr/save/nsrsnap.c 886] Calling get_pool_name..

52051:nsrsnap:Printing savecmd=nsrsnap_vss_save after parsing

05/21/15 11:45:54.406615 [nsr/save/nsrsnap.c 1693] Calling snap_wait..

APPLICATIONS:\Microsoft Exchange 2013

05/21/15 11:46:24.502469 [nsr/save/nsrsnap.c 1714] Calling parse_fs_logs_and_prefix..

107092: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: 8.2.1.0.681 Comments: Supporting Microsoft Volume Shadow Copy Service

102357:nsrsnap_vss_save:Unknown Application Information parameter: NSR_SAVE_FROM_SAVEGRP_NSRSNAP, may not be supported

102357:nsrsnap_vss_save:Unknown Application Information parameter: NSR_SAVE_FROM_SAVEGRP_NSRSNAP, may not be supported

102345:nsrsnap_vss_save:Data mover host name not specified. Assuming local host: rci-has-mbx02.hastinapur.res

102338:nsrsnap_vss_save:Backup is level FULL. Set GLR compatibility to YES.

80271:nsrsnap_vss_save:NMM .. Valid snapshot policy. Group: "DAG" Snapshot Policy: "RolloverOnly" Snapshots Per Day: "1"  Retain: "0" Backup Snapshots: "All" Level: "full".

NMM ... Using client name RCI-HAS-MBX02, the version of the Exchange server is Exchange 2013.

96585:nsrsnap_vss_save:NMM .. Initialization success -- Exchange shell successfully initialized. Required for Exchange 2010 or Exchange 2013.

38008:nsrsnap_vss_save:The NetWorker canonical client name could not be retrieved for DAG01.hastinapur.res.

37959:nsrsnap_vss_save:The group or resource is not in the correct state to perform the requested operation.

63335:nsrsnap_vss_save:NMM backup failed to complete successfully.

Internal error.

102333 1432188977 3 0 0 9564 2304 0 rci-has-mbx02.hastinapur.res nsrsnap_vss_save NSR error 21 Exiting with failure. 0

APPLICATIONS:\Microsoft Exchange 2013: Backup of [APPLICATIONS:\Microsoft Exchange 2013] failed

It is what it Says. You most likely have no cname assigned in DNS, AKA Reverse Lookup.

Per Default, Cluster Named Objects, when created do not generate cnames ( opposed to host record from Domain joined Hosts )

Code

$res = Get-ClusterResource "Cluster Name"
Set-ClusterParameter -Name PublishPTRRecords -Value 1 -InputObject $res
Stop-ClusterResource -Name $res
Start-ClusterResource -Name $res

Gui ( on Cluster Name Ressource )

Finally i got it resolved by modifying  the  below thing in application information

from= NSR_SNAP_TYPE=vss             To = NSR_SNAP_TYPE=VSS

and also added DAG FQDN name in aliases of client properties then issue has been resolved.

now everything fine.

thanks to all  for your valuable inputs.