Unsolved
This post is more than 5 years old
1 Rookie
•
124 Posts
0
2927
windows 2012 exchange dag 2013 backup failure after success
Hi
after a few days of successful backups i am now getting this error. I have run C:\Windows\Microsoft.NET\Framework64\v4.0.30319\regasm "C:\Program Files\EMC NetWorker\nsr\bin\libnmexchmgmt.dll" but still get the error any suggestions?
Microsoft .NET Framework Assembly Registration Utility version 4.0.30319.33440
for Microsoft .NET Framework version 4.0.30319.33440
Copyright (C) Microsoft Corporation. All rights reserved.
Types registered successfully
C:\Windows\system32>nsrsnap_vss_save -v -?
NMM .. changing backup name ALSEX3 to primary name alsex3.ialch.co.za for multi
NIC client.
List of valid saveset entries for APPLICATIONS on client alsex3.ialch.co.za ...
Initializing data to display...
NMM ... Using client name ALSEX3, the version of the Exchange server is Exchange
2013.
NMM .. Exchange2010 Shell interface is unavailable. This may indicate that the E
MC powershell library was not properly registered.
96585:nsrsnap_vss_save:NMM .. Initialization success -- Exchange shell successfu
lly 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
"APPLICATIONS:\Microsoft Exchange 2013"
102332:nsrsnap_vss_save:Exiting with success.
boerbokrib
1 Rookie
1 Rookie
•
124 Posts
0
May 6th, 2015 23:00
Hi all logs are clear.
The system is as follows
1 Attachment
daemon.txt
boerbokrib
1 Rookie
1 Rookie
•
124 Posts
0
May 6th, 2015 23:00
CarlosRojas
1.7K Posts
1
May 6th, 2015 23:00
Hi boerbokrib
What NW client and NMM version and build are you currently using?
What is your NW server version?
Have you checked Application and System event logs?
Please attach the nmm.raw file.
Thank you,
Carlos
CarlosRojas
1.7K Posts
1
May 6th, 2015 23:00
Hi again,
Have you looked into that DNS error? Is it already solved? Please note that is quite important, s looks like thecluster IP is not registered in DNS.
On the other hand please attach the nmm.raw file from the client, not the daemon.raw please.
Thank you,
Carlos
boerbokrib
1 Rookie
1 Rookie
•
124 Posts
0
May 6th, 2015 23:00
I have uninstalled and reinstalled nmm and still the same error.
APPLICATIONS:\Microsoft Exchange 2013: Backup of [APPLICATIONS:\Microsoft Exchange 2013] failed
formation parameter: CIRCULAR_PROMOTION_POLICY, may not be supported
102357:nsrsnap_vss_save:Unknown Application Information parameter: NSR_EXCH_INCL_SA, 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: alsex4.ialch.co.za
102338:nsrsnap_vss_save:Backup is level FULL. Set GLR compatibility to YES.
80271:nsrsnap_vss_save:NMM .. Valid snapshot policy. Group: "Exchange_DAG_win" Snapshot Policy: "test exchange" Snapshots Per Day: "1" Retain: "0" Backup Snapshots: "All" Level: "full".
85460:nsrsnap_vss_save:NMM .. Valid snapshot policy for Federated backup. Group: "Exchange_DAG_win" Snapshot Policy: "test exchange" Snapshots Per Day: "1" Retain: "0" Backup Snapshots: "All" Level: "full".
nsrsnap_vss_save: Exchange federated ..This is a federated backup for Exchange DAG.
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 GetServersDAGFQDN
Internal error.
I have run the regasm as below.
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\regasm "C:\Program Files\EMC NetWorker\nsr\bin\libnmexchmgmt.dll" but still get the error any suggestions?
Microsoft .NET Framework Assembly Registration Utility version 4.0.30319.33440
for Microsoft .NET Framework version 4.0.30319.33440
Copyright (C) Microsoft Corporation. All rights reserved.
Types registered successfully
but still same error. I have deleted diskshadows.
I have renamed the /nsr/tmp folder but still no luck.
sddc_guy
159 Posts
0
May 7th, 2015 00:00
Known issue with Clusters.
Once the CNO is created in AD, a DNS Ressoource without Pointer is Created.
My Suggestion during Cluster / DAG installs is alsways the Powers_Hell:
That create and updates PTR Records.
boerbokrib
1 Rookie
1 Rookie
•
124 Posts
0
May 7th, 2015 00:00
Hi Carlos.
Am in the process of sorting out the dns issue.
here is the nmm.raw sorry
1 Attachment
nmm.txt
elvinperez
87 Posts
0
May 7th, 2015 05:00
Hi ALL,
Normally this unregistered DLL errors are resolved by rebooting the server or reinstalling software networker.
Regards,
Elvin...
boerbokrib
1 Rookie
1 Rookie
•
124 Posts
0
May 7th, 2015 05:00
ok
The dns account has been recreated.
i have stopped service and deleted shdow copies on each node and restarted the nodes for dag.
I have also rebooted the networker backup servre.
But still getting the same error?
APPLICATIONS:\Microsoft Exchange 2013: Backup of [APPLICATIONS:\Microsoft Exchange 2013] failed
formation parameter: CIRCULAR_PROMOTION_POLICY, may not be supported
102357:nsrsnap_vss_save:Unknown Application Information parameter: NSR_EXCH_INCL_SA, 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: alsex4.ialch.co.za
102338:nsrsnap_vss_save:Backup is level FULL. Set GLR compatibility to YES.
80271:nsrsnap_vss_save:NMM .. Valid snapshot policy. Group: "Exchange_DAG_win" Snapshot Policy: "test exchange" Snapshots Per Day: "1" Retain: "0" Backup Snapshots: "All" Level: "full".
85460:nsrsnap_vss_save:NMM .. Valid snapshot policy for Federated backup. Group: "Exchange_DAG_win" Snapshot Policy: "test exchange" Snapshots Per Day: "1" Retain: "0" Backup Snapshots: "All" Level: "full".
nsrsnap_vss_save: Exchange federated ..This is a federated backup for Exchange DAG.
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 GetServersDAGFQDN
Internal error.
system log and application log is clear
nmm log has same error about library.
c:\Program Files\EMC NetWorker\nsr\applogs>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.33440
for Microsoft .NET Framework version 4.0.30319.33440
Copyright (C) Microsoft Corporation. All rights reserved.
Types registered successfully
c:\Program Files\EMC NetWorker\nsr\applogs>nsrsnap_vss_save -v -?
NMM .. changing backup name ALSEX4 to primary name alsex4.ialch.co.za for multi
NIC client.
List of valid saveset entries for APPLICATIONS on client alsex4.ialch.co.za ...
Initializing data to display...
NMM ... Using client name ALSEX4, the version of the Exchange server is Exchange
2013.
NMM .. Exchange2010 Shell interface is unavailable. This may indicate that the E
MC powershell library was not properly registered.
96585:nsrsnap_vss_save:NMM .. Initialization success -- Exchange shell successfu
lly 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
"APPLICATIONS:\Microsoft Exchange 2013"
102332:nsrsnap_vss_save:Exiting with success.
1 Attachment
EMC Config Checker.docx
CarlosRojas
1.7K Posts
0
May 7th, 2015 05:00
Hi,
What version and build of NW client, NMM and NW server are you currently using?
Thank you,
Carlos
boerbokrib
1 Rookie
1 Rookie
•
124 Posts
0
May 7th, 2015 05:00
boerbokrib
1 Rookie
1 Rookie
•
124 Posts
0
May 7th, 2015 05:00
Hi
I have done both of those as above.
boerbokrib
1 Rookie
1 Rookie
•
124 Posts
0
May 7th, 2015 05:00
I have also used regasm /u to unregistered and re-register even used /codebase.
boerbokrib
1 Rookie
1 Rookie
•
124 Posts
0
May 7th, 2015 05:00
how do i register the library properly?
NMM .. Exchange2010 Shell interface is unavailable. This may indicate that the E
MC powershell library was not properly registered.
I am using regasm
boerbokrib
1 Rookie
1 Rookie
•
124 Posts
0
May 7th, 2015 06:00
I have rebooted both nodes.