We spent close to 2 weeks chasing a NMM 2.3 issue on Exchange DAG
backups. All tracked down to name resolution / domain naming. And
this is something we take pride in knowing, or at least think we know.
We thought we had everything covered, but it turns out not everything
has to be FQDN, in fact short name was the only was some things would
work.
1st tier didn't get it (spent several days, tons of man hours and a 3
hour EMC webex, and they couldn't find it). Took EMC 2nd tier guy a
couple of hours, and we lucked into it.
Good luck.
David M. Browning Jr.
IT Project Coordinator Enterprise Backups and Help Desk
-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On
Behalf Of Phil Myers
Sent: Friday, July 20, 2012 7:36 PM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: Re: [Networker] Exchange 2010 NMM 2.3 DNS fail
I'm in contact with support now; 1st tier couldn't help so it's been
escalated.
________________________________________
From: Werth, Dave [dave.werth AT garmin DOT com]
Sent: Friday, July 20, 2012 8:33 PM
To: 'EMC NetWorker discussion'; Phil Myers
Subject: RE: [Networker] Exchange 2010 NMM 2.3 DNS fail
I've had my NMM backup for Exchange bring up long dead servers before as
well. It was not a DNS problem. It's happened to me a couple of times
and both times I contacted NetWorker support and we worked through the
problems. I can't remember the details of the fix now but it was
different each time. If you really want me to I suppose I could look
through the incident reports on the support service but I don't have the
time at the moment. I suggest you contact them for help.
Dave Werth
Garmin AT, Inc.
Salem, Oregon
-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On
Behalf Of Phil Myers
Sent: Friday, July 20, 2012 3:41 PM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: Re: [Networker] Exchange 2010 NMM 2.3 DNS fail
Thanks for the reply. As I mentioned in the post, the hostnames
mentioned in the error message no longer exist and haven't for months.
They are not referenced in DNS. They are not listed in the hosts files
on either the NW server nor the exchange client. I don't understand
where NMM or Networker is getting these names?
Phil Myers
Network Administrator
Management Information Systems
pmyers2 AT conemaugh DOT org
O: (814) 534-1559
F: (814) 534-1383
Conemaugh Health System
1086 Franklin Street, Johnstown, PA 15905-4398
www.conemaugh.org
EXCELLENCE. EVERY PATIENT. EVERY TIME.
This electronic message transmission contains information from the
Conemaugh Health System that may be proprietary, confidential and/or
privileged. The information is intended only for the use of the
individual(s) or entity named above. If you are not the intended
recipient, be aware that any disclosure, copying, or distribution or use
of the contents of this information is prohibited. If you have received
this electronic transmission in error, please notify the sender
immediately by replying to the address listed in the "From" field.
-----Original Message-----
From: Stanley R. Horwitz [mailto:stan AT temple DOT edu]
Sent: Friday, July 20, 2012 6:12 PM
To: EMC NetWorker discussion; Phil Myers
Subject: Re: [Networker] Exchange 2010 NMM 2.3 DNS fail
Phil,
The error report you provided contains references to a DNS issue, so I
suggest you investigate DNS connectivity if you have not yet done so.
Good luck.
On 07 20, 2012, at 5:24 PM, Phil Myers wrote:
> I have an exchange 2010 server whose backup failed with the following:
>
>
> NetWorker savegroup: (alert) Exchange 2010 NMM Mail4 completed, Total
1 client(s), 1 Failed. Please see group completion details for more
information.
>
>
>
> Failed: mail4
>
>
>
> Start time: Fri Jul 20 16:58:33 2012
>
> End time: Fri Jul 20 17:02:10 2012
>
>
>
>
>
> --- Unsuccessful Save Sets ---
>
>
>
> 2010 NMM Mail4" Snapshot Policy: "Serverless Backup" Snapshots Per
Day: "1" Retain: "0" Backup Snapshots: "All" Level: "full".
>
> Failed to initialize PowerShell session, retrying to initialize
Powershell session using credentials...
>
> 39076:nsrsnap_vss_save: SYSTEM warning: DNS lookup failed for
chs-exvs2: The requested name is valid, but no data of the requested
type was found.
>
> 39076:nsrsnap_vss_save: SYSTEM warning: DNS lookup failed for
chs-exvs1: The requested name is valid, but no data of the requested
type was found.
>
> 39076:nsrsnap_vss_save: SYSTEM warning: DNS lookup failed for
file03.conemaugh.org: The requested name is valid, but no data of the
requested type was found.
>
> 39076:nsrsnap_vss_save: SYSTEM warning: DNS lookup failed for file03:
The requested name is valid, but no data of the requested type was
found.
>
> 47363:nsrsnap_vss_save: nsrpsd service is running on
MAIL4.CONEMAUGH.ORG.
>
> NMM ... Using client name MAIL4, the version of the Exchange server is
Exchange 2010.
>
> 82624:nsrsnap_vss_save:Save set name APPLICATIONS:\Microsoft Exchange
2010 is valid.
>
> 63335:nsrsnap_vss_save:NMM backup failed to complete successfully.
>
> Internal error.
>
> 68151 1342817964 2 0 0 10168 10672 0 mail4.conemaugh.org
> nsrsnap_vss_save 39 nsrsnap_vss_save: Exiting with failure. 0
>
> rning: DNS lookup failed for chs-exvs2: The requested name is valid,
> but no data of the requested type wa
>
>
>
> --- Successful Save Sets ---
>
>
>
> * mail4:Probe savefs mail4: succeeded.
>
> legato: index:chs-dag.conemaugh.org level=full, 42 MB 00:02:33
1227 files
>
>
> The backup worked correctly for weeks until last night. Absolutely no
changes were made to either Networker configs or NMM or Exchange.
>
> The problem with this is that the host names mentioned in the error
are long dead servers. They haven't been running in over a year.
>
> I have tried the following:
>
>
> 1. Deleting the NSR peer information on both NW server and the
Mail4 client.
>
> 2. Stopping networker services on both the client and the NW
server, deleting the nsr/tmp and nsr/res/nsrladb folders, then
restarting the services.
>
> 3. Uninstalling NMM completely and reinstalling it
>
> Any ideas?
>
> Thank you
> Phil
>
> Phil Myers
> Network Administrator
> Management Information Systems
> pmyers2 AT conemaugh DOT org<mailto:youremail AT conemaugh DOT org>
> O: (814) 534-1559
> F: (814) 534-1383
>
> Conemaugh Health System
> 1086 Franklin Street, Johnstown, PA 15905-4398
> www.conemaugh.org<http://www.conemaugh.org>
>
> EXCELLENCE. EVERY PATIENT. EVERY TIME.
>
> This electronic message transmission contains information from the
Conemaugh Health System that may be proprietary, confidential and/or
privileged. The information is intended only for the use of the
individual(s) or entity named above. If you are not the intended
recipient, be aware that any disclosure, copying, or distribution or use
of the contents of this information is prohibited. If you have received
this electronic transmission in error, please notify the sender
immediately by replying to the address listed in the "From" field.
________________________________
This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient. If you are not the intended
recipient, please be aware that any disclosure, copying, distribution or
use of this e-mail or any attachment is prohibited. If you have received
this e-mail in error, please contact the sender and delete all copies.
Thank you for your cooperation.
|
