Unsolved
This post is more than 5 years old
32 Posts
0
3492
NMM DAG Exchange Backup issue.
Hi All,
I am facing some issue with new configuration of NMM Exchange 2013 U9 backup in Networker.
Networker and NMM version 8226 and OS is 2012 Win server.
3 Physical Nodes : All nodes has backup NIC assigned for backups.
Service User has all access for domain and Exchange.
Physical client instance configured with backup IP name (as per host file)
eurcwsmsg103-b.cws.sasol.com
eurcwsmsg104-b.cws.sasol.com -- Primary for now
eurcwsmsg105-b.cws.sasol.com
FS backup works fine for Nodes - Tested
Single node backup works fine - Tested
When i Configure the backup with DAG name I get the error in NMM .raw
136563 7/18/2016 2:07:55 PM 5 0 0 39032 51848 0 eurcwsmsg104.cws.sasol.com nsrsnap_vss_save NSR critical NMM .. Exchange Shell Exception Object reference not set to an instance of an object. in function IsPassiveOnServer
136553 7/18/2016 2:08:00 PM 5 0 0 39032 51848 0 eurcwsmsg104.cws.sasol.com nsrsnap_vss_save NSR critical NMM .. Exchange2010 Shell interface is unavailable. This may indicate that the EMC powershell library was not properly registered.
I tried everything to resolve this issue
# by using change option.
# Re-install the new downloaded package on all the nodes and reboot
# try to manually register EMC power Shell
in NMC I get following error message from today.
APPLICATIONS:\Microsoft Exchange 2013: Backup of [APPLICATIONS:\Microsoft Exchange 2013] failed
40:nsrsnap_vss_save:Backup is level INCR. Set GLR compatibility to NOT_ELIGIBLE.
80271:nsrsnap_vss_save:NMM .. Valid snapshot policy. Group: "Daily-PROD-SAP-DB-01" Snapshot Policy: "RolloverOnly" Snapshots Per Day: "1" Retain: "0" Backup Snapshots: "All" Level: "incr".
NMM ... Using client name EURCWSMSG104, 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.
47363:nsrsnap_vss_save: nsrpsd service is running on eurcwsmsg104.cws.sasol.com.
82624:nsrsnap_vss_save:Save set name APPLICATIONS:\Microsoft Exchange 2013 is valid.
63352:nsrsnap_vss_save:NMM .. start the creation of a replica. Replica will be of type Default - which is VSS determined Non Transportable.
107095:nsrsnap_vss_save:NMM .. An error was detected during the replica creation. Details in nmm.raw on eurcwsmsg104.cws.sasol.com and in the Windows Application or System Event Log.
49931:nsrsnap_vss_save:RM .. 024080 ERROR:The selected component EURCWSMDBEU007 was not found in the current writer metadata. Make sure it is online.
Microsoft DiskPart version 6.3.9600
Copyright (C) 1999-2013 Microsoft Corporation.
On computer: EURCWSMSG104
Automatic mounting of new volumes disabled.
Microsoft DiskPart version 6.3.9600
Copyright (C) 1999-2013 Microsoft Corporation.
On computer: EURCWSMSG104
Automatic mounting of new volumes enabled.
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 1468603304 3 0 0 22076 13108 0 eurcwsmsg104.cws.sasol.com nsrsnap_vss_save NSR error 21 Exiting with failure. 0
=============================================================================================
Not sure how it's coming as I am using top level save set for backup. "APPLICATIONS:\Microsoft Exchange 2013"
Need your help to resolve this issue.
Thanks in advance
Nitesh_Turkar
32 Posts
0
July 18th, 2016 07:00
ERROR message on NMC : New
APPLICATIONS:\Microsoft Exchange 2013: Backup of [APPLICATIONS:\Microsoft Exchange 2013] failed
_vss_save: DB EURCWSMDBEU004
99145:nsrsnap_vss_save: DB EURCWSMDBEU003
99145:nsrsnap_vss_save: DB EURCWSMDBNA005
99145:nsrsnap_vss_save: DB EURCWSMDBNA006
99145:nsrsnap_vss_save: DB EURCWSMDBNA004
99145:nsrsnap_vss_save: DB EURCWSMDBEU002
99145:nsrsnap_vss_save: DB EURCWSMDBNA002
99145:nsrsnap_vss_save: DB EURCWSMDBNA001
99145:nsrsnap_vss_save: DB EURCWSMDBEU009
99145:nsrsnap_vss_save: DB EURCWSMDBEU001
63320:nsrsnap_vss_save:NMM has detected that no valid saveset entries have been requested.
nsrsnap_vss_save: Exchange federated .. backup did not complete and no data was backed up.
07/18/16 14:10:55.728936 Unregistered session id:2, fd:2104, idx:1, ssn_max_pollfd:1, 1(512)
97614:nsrsnap_vss_save:nsrsnap_vss_save: Exchange federated .. createInstantBackup failed with error 0xc0000001 Fatal error and cannot continue.
nsrsnap_vss_save(382): Entering SendRecoverJobFailure().
Internal error.
07/18/16 14:10:55.734940 Unregistered session id:1, fd:1004, idx:0, ssn_max_pollfd:0, 0(512)
nsrsnap_vss_save(394): Exiting SendBackupJobFailure().
nsrsnap_vss_save: Sending backup status to nsrsnap
102333 1468843855 3 0 0 39032 51848 0 eurcwsmsg104.cws.sasol.com nsrsnap_vss_save NSR error 21 Exiting with failure. 0
07/18/16 14:11:05.012767 Unregistered session id:1, fd:1924, idx:0, ssn_max_pollfd:0, 0(512)
Nitesh_Turkar
32 Posts
0
July 18th, 2016 13:00
All DBs are in Healthy state and mounted.
gautamgp
226 Posts
0
July 19th, 2016 09:00
Nitesh Bhai,
I feel you DAG client configuration may be wrong. You said that you have created the Physical clients with Backup IP, but the DAG might not have Backup IP and while you are creating the client for DAG it would be trying to look for the clients with the Actual DNS Names. You can check by creating the clients with the Actual DNS names.
Nitesh_Turkar
32 Posts
0
July 21st, 2016 09:00
Hey
Client configuration looks perfect. EMC engineers already check it couple of times
What else I can check on DAG end to make this configuration work.
I understand the VLAN are different for PROD and BACKUP but both have inter trust. so the communication between both VLANs is perfect. (No Firewall in picture)
On DAG end has the access to use backup IP for communication.
I completely agree, that I need to create clients by using PROD name if this configuration doesn't work
I m wondering if I could make this work as per this configuration.
Not sure about the below point.
Regards
gautamgp
226 Posts
0
July 21st, 2016 20:00
I don't think you can assign Backup IP to the Cluster. I am not really certain that the current configuration would work, You can check with Support. We have configured backup for a similar configuration for a customer where we created Clients with the PROD names and then let DDBoost ifgroup route the backups using the backup Network.