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
Simon,
Actually I have rebooted
several times and nothing significant showed up in the event
log.
Anas
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
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.
|