Exchange 2010 DAG Failed - EMC powershell library was not properly registered
Hi Community,
I’m Running My Exchange 2010 on Dag Environment with 3 Nodes (Win2k8) and DBs Started to fail with below Error. Tried to fix it with NMM Repair option but no good. Please give me some thoughts with your expertise to get out of the Issue.
Networker Version 8.1.1.5 (nw811_win_x64_297)
NMM nmm301_win_x64
Thanks,
Dinusha
APPLICATIONS:\Microsoft Exchange 2010\Database1: Backup of [APPLICATIONS:\Microsoft Exchange 2010\Database1] failed
102357:nsrsnap_vss_save:Unknown Application Information parameter: DIRECT_ACCESS, 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: xxxx.xxxx.local
102338:nsrsnap_vss_save:Backup is level FULL. Set GLR compatibility to YES.
I would suggest you to restart all NW services on node SRV-MBX-2 and run the command again:
nsrsnap_vss_save -v -?
If result goes OK attempt a new backup, if it fail then review the configuration and change to backup "All" DB's instead of only Active, or change the PSOL to set a different node in position 1 in the priority list.
it was supposed to reply to your previous reply after running the nsrsnap_vss_save -v -?
actually before running the command i reinstalled the nmm 3.0 as a workaround and fortunately it helps me getting a proper output for the command that lists the DB i have on the DAG members ...
so i overcome the original error for the powershell library initialization ....
now after running the backup i'm getting the below error, and for further invistigation i'm attaching also the nmm.raw from node1 ...
the error:
92347:nsrsnap:***************** Snapshot Management operation has started, logging to "C:\Program Files\EMC NetWorker\nsr\logs\nwsnap.raw" *****************11/04/14 13:47:35.579037 [nsr/save/nsrsnap.c 607] Calling nsrrm_host
52051:nsrsnap:Printing savecmd=nsrsnap_vss_save after parsing
79549:nsrsnap:[nsr/save/nsrsnap.c 1713] Invoking command: "nsrsnap_vss_save -A optype=conventional -A NSR_SAVE_FROM_SAVEGRP_NSRSNAP=Yes -A "NSR_SNAP_TYPE=vss" -A "CIRCULAR_PROMOTION_POLICY=Promote" -A "NSR_FEDERATED_BACKUP=yes" -A "NSR_FEDERATED_PSOL=SRV-MBX-2,SRV-MBX-1" -A "NSR_EXCH_INCL_SA=TRUE" -A "NSR_ALT_PATH=C:\Exch_consistency" -A "NSR_EXCH2010_DAG=DAG-2013.alhasa.gov.sa" -A "NSR_EXCH2010_BACKUP=active" -A "NSR_EXCH_CHECK=no" -A NSR_PARENT_JOBID=33143 -c DAG-2013.alhasa.gov.sa -g "Exch_MB" -LL -m DAG-2013.alhasa.gov.sa -s srv-backup.alhasa.gov.sa -a "DIRECT_ACCESS=No" -l full -q -W 78 -A snap_sessionid=1415098057 "11/04/14 13:47:37.248190 [nsr/save/nsrsnap.c 1730] Calling start_savecmd..
nsrsnap_vss_save: Exchange federated ..This is a federated backup for Exchange DAG.
96585:nsrsnap_vss_save:NMM .. Initialization success -- Exchange shell successfully initialized. Required for Exchange 2010 or Exchange 2013.
nsrsnap_vss_save: Exchange federated .. Only backup databases that are in active state.
nsrsnap_vss_save: Exchange federated .. A preferred server order list has been provided.
nsrsnap_vss_save: Exchange federated .. Server order checked for DBs:
SRV-MBX-2
SRV-MBX-1
nsrsnap_vss_save: Exchange federated .. initial evaluation of listed database saveset. This may take some time.
nsrsnap_vss_save: Exchange federated .. Databases in DAG have been evaluated for backup..continuing.
99143:nsrsnap_vss_save:
99147:nsrsnap_vss_save:nsrsnap_vss_save: Exchange federated .. These Exchange databases have not been added to the backup list.
99148:nsrsnap_vss_save:The Exchange database may be a standalone or Public Folder and identified to be skipped.
99149:nsrsnap_vss_save:The current state of the DB does not match the configured backup state identifed, is dismounted or suspended.
99143:nsrsnap_vss_save:
99143:nsrsnap_vss_save:
Starting slave backup job on host : SRV-MBX-2.
51340:nsrsnap_vss_save:jobhandler(292): Created Job ID: 33148
Save command: nsrsnap_vss_save.exe -s srv-backup.alhasa.gov.sa -g Exch_MB -m SRV-MBX-2.alhasa.gov.sa -l full -W 78 -LL -z DAG-2013.alhasa.gov.sa -A optype=conventional -A NSR_SAVE_FROM_SAVEGRP_NSRSNAP=Yes -A NSR_SNAP_TYPE=vss -A CIRCULAR_PROMOTION_POLICY=Promote -A NSR_FEDERATED_BACKUP=yes -A NSR_FEDERATED_PSOL=SRV-MBX-2,SRV-MBX-1 -A NSR_EXCH_INCL_SA=TRUE -A "NSR_ALT_PATH=C:\\Exch_consistency" -A NSR_EXCH2010_DAG=DAG-2013.alhasa.gov.sa -A NSR_EXCH2010_BACKUP=active -A NSR_EXCH_CHECK=no -A NSR_PARENT_JOBID=33143 -A DIREC
Starting slave backup job on host : SRV-MBX-1.
51340:nsrsnap_vss_save:jobhandler(292): Created Job ID: 33149
Save command: nsrsnap_vss_save.exe -s srv-backup.alhasa.gov.sa -g Exch_MB -m SRV-MBX-2.alhasa.gov.sa -l full -W 78 -LL -z DAG-2013.alhasa.gov.sa -A optype=conventional -A NSR_SAVE_FROM_SAVEGRP_NSRSNAP=Yes -A NSR_SNAP_TYPE=vss -A CIRCULAR_PROMOTION_POLICY=Promote -A NSR_FEDERATED_BACKUP=yes -A NSR_FEDERATED_PSOL=SRV-MBX-2,SRV-MBX-1 -A NSR_EXCH_INCL_SA=TRUE -A "NSR_ALT_PATH=C:\\Exch_consistency" -A NSR_EXCH2010_DAG=DAG-2013.alhasa.gov.sa -A NSR_EXCH2010_BACKUP=active -A NSR_EXCH_CHECK=no -A NSR_PARENT_JOBID=33143 -A DIREC
95937:nsrsnap_vss_save:A slave job failure has been identified, stopping all slave jobsnsrsnap_vss_save: Exchange federated ..Updated saveset response with hresult 0x54f.
aliv1
2 Posts
2402
0
Posted June 30th, 2014 01:00
I'm experiencing exactly same issue with Exchange 2010 in Networker 8.0 + NMM 2.4 environment.