Re: [Veritas-bu] Exchange Store Backup
2008-12-31 12:32:37
Anas
Clearly something did change ... on the Network side
!
Glad its sorted and glad you got it
resolved
Happy New Year !
Simon
Here's the
update:
To eliminate network issues, yesterday I
connected a cross cable between NBU master and exchange and ran a perfect
backup. Now I knew that there was a problem from the network and I can face my
network team who have failed to agree with me.
2 weeks ago I had a UPS failure in my main
datacenter which basically brought everything down for exactly 4 seconds.
Everything connected to that UPS restarted. My master was connected to it and
also my Cisco 6509 switch (responsible for server vlan). Now NBU box came up
before the switch. Switch port for NBU was originally configured for auto
negotiate speed. But since NBU came up before the switch finished initializing,
it automatically configured the port at half duplex.
It was a pain getting my network people to
dive into the issue until I physically went down to the switch with them and
looked at the running config myself. We were able to pinpoint the issue right
away and resolve it.
Thanks for your help everyone.
Anas
From: Simon Weaver
[mailto:Simon.Weaver AT iscl DOT net] Sent: Tue 12/30/2008 6:41
PM To: Anas Kayal;
Veritas-bu AT mailman.eng.auburn DOT edu Subject: RE: [Veritas-bu] Exchange
Store Backup
Hi
I am just about to go on leave, but sounds like the Network
needs to be looked into, and check the links between the Master and this Server,
including any switches and all speeds.
Unless anyone else can come up with a suggestion
:-(
Simon
Simon,
I already updated NIC drivers. There is no firewall between NBU
Master and Exchange.
I'm running 6.0 MP4 on both master and client. No exchange cluster
in the environment. I have enable level 5 logging and I see the 10054 error with
connection reset by peer.
I was even thinking about upgrading the maintenance pack to the
latest but unsure if it would help.
I noticed something today when monitoring the network traffic on
master and client. Backup starts for info store and once tape is mounted traffic
begins to flow and both machines have heavy traffic. At a certain point, usually
3-5 minutes into the backup, traffic dies to zero and after approx 1 minute, the
job fails.
Any ideas?
Anas
From: Simon Weaver
[mailto:Simon.Weaver AT iscl DOT net] Sent: Mon 12/29/2008 12:40
PM To: Anas Kayal;
Veritas-bu AT mailman.eng.auburn DOT edu Subject: RE: [Veritas-bu] Exchange
Store Backup
Usually file write error tar is normally indeed NIC /
Network related. Can also occur if the boxes are going through a firewall and
rules are not configured correctly.
Is it worth updating the NIC drivers just to be sure? I
appreciate nothing has changed, but even if there has been a minor change on the
speed of the Network, it may all need to be investigated.
What Maintenance Pack are you on? In fact, what level of
NBU is on the client and the Master? Also, confirm this is a single exchange
server, and not in a cluster.
It may also be worth enabling full logging on the client
itself to see what Netbackup is really complaining about. I do mean the
NetBackup logs and verbose logging to max (normally 5).
Logs are found in C:\Program
Files\Veritas\NetBackup\Logs\bpbkar (assuming its been created, if not run the
batch file in the logs folder).
Stop / Restart the NetBackup client service and try the
backup again.
Hope this is of some help
Simon
That’s what I meant … nothing
significant in the event logs during the backup. I have my maintenance schedule
for mailbox and public folder store to run between 2 and 6 am during which the
backup is running but I have never had problems with that before.
The backup is Info Store and BLB
(which I really hate too)
From: Simon Weaver
[mailto:Simon.Weaver AT iscl DOT net] Sent: Monday, December 29, 2008 12:47
AM To: Anas Kayal;
Veritas-bu AT mailman.eng.auburn DOT edu Subject: RE: [Veritas-bu] Exchange
Store Backup
But what
about the event logs "during" the backup itself? Specifically, the Application
log during the backup?
Also, is
the problem related to just doing an "Information Store" Backup or a BLB (Brick
Level Backups that I really, really hate!)
Thanks,
Simon
From: Anas Kayal
[mailto:anas AT up.org DOT qa] Sent: 28 December 2008 20:46 To:
Simon Weaver; Veritas-bu AT mailman.eng.auburn DOT edu Subject: RE:
[Veritas-bu] Exchange Store Backup
Actually
I have rebooted several times and nothing significant showed up in the
event log.
From: Simon Weaver
[mailto:Simon.Weaver AT iscl DOT net] Sent: Sun 12/28/2008 11:20
PM To: Anas Kayal;
Veritas-bu AT mailman.eng.auburn DOT edu Subject: RE: [Veritas-bu] Exchange
Store Backup
Hi
Have you
rebooted the client Server? If so, can you do this?
Any
error messages or warning in the System or importantly, the Application logs at
the time of the backup?
Simon
From:
veritas-bu-bounces AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu] On Behalf Of Anas
Kayal Sent: 28 December 2008 05:43 To:
Veritas-bu AT mailman.eng.auburn DOT edu Subject: [Veritas-bu] Exchange Store
Backup
Ive been running into backup issues with exchange 2003. I
have had a 2 policies for over 2 years now. One for Information store and one
for mailbox store. Each works separately at different time intervals. Starting
this week, I would get error “FTL - tar file write error (10054)”. When I looked
it up, it stated that there was most likely an network error. Nothing was
changed on my network level and all NIC’s are full operational.
I have no anti-virus installed, I removed and reinstalled
agent, I even teamed the NIC’s on exchange. Still I get the same error. The
error comes usually after a couple of minutes into the backup starts.
If anyone can give me some opinions please.
Thanks in advance,
Anas
This message (including any attachments) is intended only for the use of the
individual or entity to which it is addressed and may contain information that
is non-public, proprietary, privileged and/or confidential. If you are not the
intended recipient, you are hereby notified that any use, dissemination,
distribution, or copying of this communication is strictly prohibited. If you
have received this communication in error, kindly notify us immediately at
abuse AT up.org DOT qa and delete this message. Thank you.
This message (including any attachments) is intended only for the use of the
individual or entity to which it is addressed and may contain information that
is non-public, proprietary, privileged and/or confidential. If you are not the
intended recipient, you are hereby notified that any use, dissemination,
distribution, or copying of this communication is strictly prohibited. If you
have received this communication in error, kindly notify us immediately at
abuse AT up.org DOT qa and delete this message. Thank you.
This message (including any attachments) is intended only for the use of the
individual or entity to which it is addressed and may contain information that
is non-public, proprietary, privileged and/or confidential. If you are not the
intended recipient, you are hereby notified that any use, dissemination,
distribution, or copying of this communication is strictly prohibited. If you
have received this communication in error, kindly notify us immediately at
abuse AT up.org DOT qa and delete this message. Thank you.
This message (including any attachments) is intended only for the use of the
individual or entity to which it is addressed and may contain information that
is non-public, proprietary, privileged and/or confidential. If you are not the
intended recipient, you are hereby notified that any use, dissemination,
distribution, or copying of this communication is strictly prohibited. If you
have received this communication in error, kindly notify us immediately at
abuse AT up.org DOT qa and delete this message. Thank you.
This message (including any attachments) is intended only for the use of the
individual or entity to which it is addressed and may contain information that
is non-public, proprietary, privileged and/or confidential. If you are not the
intended recipient, you are hereby notified that any use, dissemination,
distribution, or copying of this communication is strictly prohibited. If you
have received this communication in error, kindly notify us immediately at
abuse AT up.org DOT qa and delete this message. Thank you.
|
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
|
<Prev in Thread] |
Current Thread |
[Next in Thread> |
- Re: [Veritas-bu] Exchange Store Backup, (continued)
- Message not available
- Re: [Veritas-bu] Exchange Store Backup, Simon Weaver
- Re: [Veritas-bu] Exchange Store Backup, Anas Kayal
- Message not available
- Re: [Veritas-bu] Exchange Store Backup, Simon Weaver
- Re: [Veritas-bu] Exchange Store Backup, Anas Kayal
- Message not available
- Re: [Veritas-bu] Exchange Store Backup, Simon Weaver
- [Veritas-bu] Searching Forum Archives, Randy Samora
- Re: [Veritas-bu] Searching Forum Archives, Nardello, John
- Re: [Veritas-bu] Searching Forum Archives, Jeff Lightner
- Re: [Veritas-bu] Searching Forum Archives, W. Curtis Preston
- Re: [Veritas-bu] Exchange Store Backup, Anas Kayal
- Re: [Veritas-bu] Exchange Store Backup,
Simon Weaver <=
|
|
|