Um ... I meant "Mr Albert." Yeah that's it!
Sorry, Eddie -- I have seen you correcting others in this list and
should have looked more closely.
None of this makes much sense. NwAdmin is the NetWorker Server GUI --
it will not run as a result of schedules. Maybe you mean that a
scheduled job started at that time? Was it an NMEx job or a normal
filesystem job (e.g. "all")?
Are there really *no* events in the App Log on the Exchange Server? If
this is a *crash* then there must be something there. I am less sure
what a bunch of login popups suggests -- a brief drop in network
connectivity? A sudden flurry of NetWorker-generated packets on the
network? The Exchange Server may not have seen that -- thus no events,
just a bunch of Outlook clients that went away and now want to come
back.
My guess, from your brief description, is that NetWorker is not directly
causing this problem, although it might be causing some environmental
anomaly that triggers it.
Thanks,
_Scott
(ex-developer for NMEx)
-----Original Message-----
From: Albert Eddie Contractor AFRPA CIO/IT
[mailto:Eddie.Albert AT AFRPA.PENTAGON.AF DOT MIL]
Sent: Friday, November 03, 2006 12:56 PM
To: EMC NetWorker discussion; Bingham, Scott
Subject: RE: [Networker] Exchange 2003 Crashes when Backup server is on
Scott,
First of all my name is Eddie (military folks and the setup /shrug) no
troubles there just FYI.
I Just spent 3 hours on the phone with the EMC West Coast LarryB. We
went through App Logs, System Logs, the Daemon Logs on Networker, etc...
NO discoveries. Checking the log we discovered that NWADMIN fired at
0900 and was done at 09:00:15--15 whole seconds after start. We know
that if the backup server is shut-off before 0900 we don't have the
problem, but if the backup server is on, all users start receiving
pop-ups asking for login credentials and passwords for exchange.
The only other thing that would coincide with communication from the
backup server to the exchange server is I receive the Networker reports
(bootstrap, etc) via SMTP. The only two events that occurred prior to
the symptom (that we are aware of) is the time change and an off-line
defrag of the exchange server.
Anyone else have any ideas on this?
Basic setup + basic backup = High Tech Problem /shrug
Both EMC Tech Support and I are scratching our heads over this one.
> -----Original Message-----
> On Behalf Of Scott Bingham
>
> Exchange Server tends to be very good about logging events to
> the Application Log. Any help in there?
>
> -----Original Message-----
> On Behalf Of Albert Eddie Contractor AFRPA CIO/IT
>
> My Environment:
> Windows 2003
> Exchange 2003
> NetWorker 7.2.1
> Exchange Module 4.1.x.x
> Outlook 2003 (11.5608.5606)
>
> 0900 during the week this week has been a bad time.
>
> @ 0900 our Exchange Server starts having trouble. Anyone who
> has Outlook open is getting POP-UPS asking for login credentials.
>
> But ONLY if our backup server is turned on. If we turn the
> backup server off, voila the exchange server is fine.
>
> It does not appear as though backups are being run, although
> a SKIP is scheduled for 0900 Weekdays.
>
> Has anyone else experienced this?
To sign off this list, send email to listserv AT listserv.temple DOT edu and
type "signoff networker" in the
body of the email. Please write to networker-request AT listserv.temple DOT edu
if you have any problems
wit this list. You can access the archives at
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
|
