UNSOLVED

Dinusha

updated

12 years ago

D

Dinusha

1 Rookie

•

52 Posts

0

10507

June 26th, 2014 02:00

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.

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

NMM ... Using client name xxxx.xxxx.local, the version of the Exchange server is Exchange 2010.

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.

NMM .. Exchange Shell Exception  in function GetServersDAG

NMM .. Exchange Shell Exception  in function GetServersDAG

89403:nsrsnap_vss_save:NMM ..DAG name xxxx.xxxx.local 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 1403768035 3 0 0 27360 24700 0 xxxx.xxxx.local nsrsnap_vss_save NSR error 21 Exiting with failure. 0

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

  • aliv1

    2 Posts

    2402

    0

    Posted June 30th, 2014 04:00

    This was permissions problem in our case, this thread pointed me to right direction:

    Re: NMM error

  • CarlosRojas

    1 Rookie

    •

    1693 Posts

    2402

    0

    Posted July 6th, 2014 23:00

    Hello Dinusha

    Did the issue get resolved by https://community.emc.com/message/558000#558000 ?

    If not, please let us know the current status.

    Thank you,

    Carlos

  • Mhmd_Saad

    8 Posts

    2402

    0

    Posted November 2nd, 2014 03:00

    Hi Folks,

    Carlos Rojas

    Ahmed Bahaa

    i have the same problem with Exchange 2013 ...

    C:\Windows\Microsoft.NET\Framework64\v4.0.30319>nsrsnap_vss_save -A NSR_EXCH_DAG=dag-2013 -?

    86745: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: 3.0.0.282

            Comments: NetWorker Module for Microsoft (x64)

    NMM .. changing backup name SRV-MBX-1 to primary name srv-mbx-1.alhasa.gov.sa for multi NIC client.

    List of valid saveset entries for APPLICATIONS on client srv-mbx-1.alhasa.gov.sa ...

    Initializing data to display...

    NMM ... Using client name SRV-MBX-1, the version of the Exchange server is Exchange 2013.

    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.

    NMM .. Exchange Shell Exception  in function GetServersDAG

    NMM .. Exchange Shell Exception  in function GetDatabaseDistinguishedName

    NMM .. Exchange Shell Exception  in function GetDatabaseObjectClass

    NMM .. Exchange Shell Exception  in function CheckDBExists

    NMM .. Exchange Shell Exception  in function IsPublicFolderDatabase

    NMM .. Exchange Shell Exception  in function IsMounted

    NMM .. Exchange Shell Exception  in function GetDatabaseDistinguishedName

    NMM .. Exchange Shell Exception  in function GetDatabaseObjectClass

    NMM .. Exchange Shell Exception  in function CheckDBExists

    NMM .. Exchange Shell Exception  in function IsPublicFolderDatabase

    NMM .. Exchange Shell Exception  in function IsMounted

    NMM .. Exchange Shell Exception  in function GetDatabaseDistinguishedName

    NMM .. Exchange Shell Exception  in function GetDatabaseObjectClass

    NMM .. Exchange Shell Exception  in function CheckDBExists

    NMM .. Exchange Shell Exception  in function IsPublicFolderDatabase

    NMM .. Exchange Shell Exception  in function IsMounted

    NMM .. Exchange Shell Exception  in function GetDatabaseDistinguishedName

    NMM .. Exchange Shell Exception  in function GetDatabaseObjectClass

    NMM .. Exchange Shell Exception  in function CheckDBExists

    NMM .. Exchange Shell Exception  in function IsPublicFolderDatabase

    NMM .. Exchange Shell Exception  in function IsMounted

    NMM .. Exchange Shell Exception  in function GetDatabaseDistinguishedName

    NMM .. Exchange Shell Exception  in function GetDatabaseObjectClass

    NMM .. Exchange Shell Exception  in function CheckDBExists

    NMM .. Exchange Shell Exception  in function IsPublicFolderDatabase

    NMM .. Exchange Shell Exception  in function IsMounted

    "APPLICATIONS:\Microsoft Exchange 2013"

    68150:nsrsnap_vss_save:nsrsnap_vss_save: Exiting with success.

    permissions are set properly ...


    re-registered the powershell library using the below, but the problem still exist ...

    C:\Windows\system32>Cd C:\Windows\Microsoft.NET\Framework64\v4.0.30319

    C:\Windows\Microsoft.NET\Framework64\v4.0.30319>regasm "C:\Program Files\EMC NetWorker\nsr\bin\libnmexchmgmt.dll"

    Microsoft .NET Framework Assembly Registration Utility version 4.0.30319.17929

    for Microsoft .NET Framework version 4.0.30319.17929

    Copyright (C) Microsoft Corporation.  All rights reserved.

    Types registered successfully

  • CarlosRojas

    1 Rookie

    •

    1693 Posts

    2402

    0

    Posted November 3rd, 2014 03:00

    Hi,

    Can you please run the following command and attach a txt file with the full output?:

    nsrsnap_vss_save -v -?

    Once the command completes, please check the Application and System event logs in case the command failed.

    Thank you,

    Carlos

  • CarlosRojas

    1 Rookie

    •

    1693 Posts

    2402

    0

    Posted November 4th, 2014 02:00

    Hello @Mohammad S. Mogahed,

    Did you have the chance to follow the steps provided?

    Thank you,

    Carlos

  • CarlosRojas

    1 Rookie

    •

    1693 Posts

    2402

    0

    Posted November 4th, 2014 03:00

    Did you reinstall NMM on the 2 Exchange nodes?

    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.

    Thank you,Carlos

  • Mhmd_Saad

    8 Posts

    2402

    0

    Posted November 4th, 2014 03:00

    Hi Carlos,

    Thanks for your usual support and interest ...

    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

    11/04/14 13:47:35.610234 [nsr/save/nsrsnap.c 878] Calling get_pool_name..

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

    APPLICATIONS:\Microsoft Exchange 2013\MBX Database 2 APPLICATIONS:\Microsoft Exchange 2013\Mailbox Database 1599281466 APPLICATIONS:\Microsoft Exchange 2013\MBX Database 1 APPLICATIONS:\Microsoft Exchange 2013\Mailbox Database 1509257692 APPLICATIONS:\Microsoft Exchange 2013\MBX Database 3 APPLICATIONS:\Microsoft Exchange 2013\VIP Database 1

    11/04/14 13:47:37.263772 [nsr/save/nsrsnap.c 1743] Calling snap_wait..

    11/04/14 13:50:07.484699 [nsr/save/nsrsnap.c 1764] Calling parse_fs_logs_and_prefix..

    86745: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: 3.0.0.282

        Comments: NetWorker Module for Microsoft (x64)

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

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

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

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

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

    50411:nsrsnap_vss_save:nsrsnap_vss_save: Data mover host name not specified. Assuming local host: srv-mbx-2.alhasa.gov.sa

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

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

    85460:nsrsnap_vss_save:NMM .. Valid snapshot policy for Federated backup. Group: "Exch_MB" Snapshot Policy: "RolloverOnly" Snapshots Per Day: "1"  Retain: "0" Backup Snapshots: "All" Level: "full".

    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.

    Internal error.

    68151 1415098205 2 0 0 10028 3552 0 srv-mbx-2.alhasa.gov.sa nsrsnap_vss_save NSR warning 39 nsrsnap_vss_save: Exiting with failure. 0

    APPLICATIONS:\Microsoft Exchange 2013\VIP Database 1: Backup of [APPLICATIONS:\Microsoft Exchange 2013\VIP Database 1] failed

    APPLICATIONS:\Microsoft Exchange 2013\MBX Database 3: Backup of [APPLICATIONS:\Microsoft Exchange 2013\MBX Database 3] failed

    APPLICATIONS:\Microsoft Exchange 2013\Mailbox Database 1509257692: Backup of [APPLICATIONS:\Microsoft Exchange 2013\Mailbox Database 1509257692] failed

    APPLICATIONS:\Microsoft Exchange 2013\MBX Database 1: Backup of [APPLICATIONS:\Microsoft Exchange 2013\MBX Database 1] failed

    APPLICATIONS:\Microsoft Exchange 2013\Mailbox Database 1599281466: Backup of [APPLICATIONS:\Microsoft Exchange 2013\Mailbox Database 1599281466] failed

    APPLICATIONS:\Microsoft Exchange 2013\MBX Database 2: Backup of [APPLICATIONS:\Microsoft Exchange 2013\MBX Database 2] failed

    1 Attachment

  • Mhmd_Saad

    8 Posts

    2402

    0

    Posted November 4th, 2014 04:00

    Yes i've re-installed the NMM on both DAG nodes and the command ran successfully on both ...

    tried all the suggestions you provide and inverted the selection between them ... but no hope

    same error as above ... all configurations are ok ...