We have not had any issues except at the very beginning, it was not
purging the log files.  I can't remember exactly what we did, but we
called support and they stepped us through fixing what wasn't working.
I almost want to say that we had to use NTBackup once or something -
can't remember though.  Since then, we have had zero issues.  We've even
modified the jobs a couple of times since then.  No problems.  Wish I
could be of more help. 


Ben Winzenz
Network Engineer
Gardner & White
(317) 581-1580 ext 418


-----Original Message-----
From: Ray Beckwith [mailto:[EMAIL PROTECTED] 
Posted At: Wednesday, August 27, 2003 12:11 PM
Posted To: Exchange (Swynk)
Conversation: Timeout Errors Backing up Exchange 2000 with Backup Exec 9
Subject: RE: Timeout Errors Backing up Exchange 2000 with Backup Exec 9


Have you had such success from day one? Were there issues in the
beginning and, if so, what solutions did you put in place?



                Thanks...Ray

Thought for the day:
A good rule of thumb is if you've made it to thirty-five and your job
still requires you to wear a name tag, you've made a serious vocational
error.
                --Dennis Miller 



-----Original Message-----
From: Ben Winzenz [mailto:[EMAIL PROTECTED]
Sent: Wednesday, August 27, 2003 10:08 AM
To: Exchange Discussions
Subject: RE: Timeout Errors Backing up Exchange 2000 with Backup Exec 9


We're using BE9.0 as well and back up a total of about 10 servers.  The
Exchange server is the last one on the list, and we have never had it
fail.  Backup rate is SWEET! As well.  Sitting pretty at about 850mb/min
with Exchange.  Love that SDLT tape drive! 


Ben Winzenz
Network Engineer
Gardner & White
(317) 581-1580 ext 418


-----Original Message-----
From: Andy David [mailto:[EMAIL PROTECTED] Posted At: Wednesday,
August 27, 2003 12:02 PM Posted To: Exchange (Swynk)
Conversation: Timeout Errors Backing up Exchange 2000 with Backup Exec 9
Subject: Re: Timeout Errors Backing up Exchange 2000 with Backup Exec 9


Yea, we went through all that as well.
I got tired of trying to explain it to my duck.
Creating the separate job was the only solution, silly as it sounds..

----- Original Message -----
From: "Ray Beckwith" <[EMAIL PROTECTED]>
To: "Exchange Discussions" <[EMAIL PROTECTED]>
Sent: Wednesday, August 27, 2003 12:35 PM
Subject: RE: Timeout Errors Backing up Exchange 2000 with Backup Exec 9


Tried that. The job just failed earlier. Unfortunately, one of the
changes
to BEX9 includes using NDMP for agent communications. A side affect is
that,
communications failures with one agent can cause the entire job to fail
from
that point. Example, Exchange server third out of 15, first 2 servers
backup
successfully, Exchange gets error, job throws up hands in confusion and
doesn't attempt to backup any other servers. 13 servers fail...



Thanks...Ray

Thought for the day:
A good rule of thumb is if you've made it to thirty-five and your job
still
requires you to wear a name tag, you've made a serious vocational error.
--Dennis Miller



-----Original Message-----
From: Roger Seielstad [mailto:[EMAIL PROTECTED]
Sent: Wednesday, August 27, 2003 9:28 AM
To: Exchange Discussions
Subject: RE: Timeout Errors Backing up Exchange 2000 with Backup Exec 9


Maybe just changing the order would work

--------------------------------------------------------------
Roger D. Seielstad - MTS MCSE MS-MVP
Sr. Systems Administrator
Inovis Inc.


> -----Original Message-----
> From: Ray Beckwith [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, August 27, 2003 11:44 AM
> To: Exchange Discussions
> Subject: RE: Timeout Errors Backing up Exchange 2000 with
> Backup Exec 9
>
>
> No problems backing up the store with NT Backup. In fact, no
> problems backing up the store alone with Backup Exec. Problem
> seems only to happen when backing up all (15 total) servers
> in one job.
>
> Last night we tried separating out the Exchange backup in a
> separate job and I'm still waiting for it to complete. Will
> update the list with results.
>
>
>
> Thanks...Ray
>
> Thought for the day:
> A good rule of thumb is if you've made it to thirty-five and
> your job still requires you to wear a name tag, you've made a
> serious vocational error.
> --Dennis Miller
>
>
>
> -----Original Message-----
> From: Roger Seielstad [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, August 27, 2003 4:10 AM
> To: Exchange Discussions
> Subject: RE: Timeout Errors Backing up Exchange 2000 with
> Backup Exec 9
>
>
> Other than Andy's suggestion of trying NTBackup, have you
> looked to see that
> the Backup Exec agent is running with sufficient rights?
>
> SP4 for Win2k changes some of the permissions levels to better match
> Win2k3's permissions model, and quite specifically it changes network
> permissions. Windows 2000 & .Net magazine had a web article
> about it not too
> long ago, which I stumbled across the other day.
> http://www.win2000mag.net/Articles/Index.cfm?ArticleID=39534
>
> From the article:
> "One end result is that some programs, plus services not
> under control of
> svchost.exe, might not behave as expected when they logon
> with an account
> that does not have the 'Impersonate a client after
> authentication' right. "
>
> I wonder if that's not the cause of the issue.
>
> --------------------------------------------------------------
> Roger D. Seielstad - MTS MCSE MS-MVP
> Sr. Systems Administrator
> Inovis Inc.
>
>
> > -----Original Message-----
> > From: Ray Beckwith [mailto:[EMAIL PROTECTED]
> > Sent: Tuesday, August 26, 2003 7:49 PM
> > To: Exchange Discussions
> > Subject: Timeout Errors Backing up Exchange 2000 with Backup Exec 9
> >
> >
> > Exchange 2000 Server - SP3 running on Windows Server (DC) 2000 - SP4
> >
> > Question:
> > Running BackupExec 9.0 Build 4454 (the latest) and have been
> > getting the following error almost exclusively during the
> > Exchange server portion of the backup.
> >
> > Final error code: a00084f8 HEX
> > Final error description: A timeout occurred waiting for data
> > from the agent during operation shutdown.
> >
> > We have been working with support for a couple months and
> > they keep pointing at network problems but aren't offering
> > much more help on what types of problems to look for. As far
> > as we can tell we are a standard network setup; Windows 2000
> > Active Directory, all up to date on service packs; one
> > Exchange server and one SQL server (separate machines); no
> > apparent network problems or bottlenecks in everyday operations.
> >
> > We've tried setting the ports explicitly to 100mb Full duplex
> > at the Exchange server, backup server and switch ports. We
> > tried stopping our ScanMail application also and verified
> > that none of the Exchange maintenance tasks were running at
> > the time of the backup.
> >
> > Is there anyone out there that might be able to offer any
> > more suggestions on how to troubleshoot these problems? We
> > are not getting reliable backups and are looking for whatever
> > help we can find.
> >
> > _________________________________________________________________
> > List posting FAQ:       http://www.swinc.com/resource/exch_faq.htm
> > Web Interface:
> > http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchange&t
> ext_mode=&lang=english
> To unsubscribe:         mailto:[EMAIL PROTECTED]
> Exchange List admin:    [EMAIL PROTECTED]
>
> _________________________________________________________________
> List posting FAQ:       http://www.swinc.com/resource/exch_faq.htm
> Web Interface:
> http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchange&t
ext_mode=&lang=english
To unsubscribe:         mailto:[EMAIL PROTECTED]
Exchange List admin:    [EMAIL PROTECTED]

_________________________________________________________________
List posting FAQ:       http://www.swinc.com/resource/exch_faq.htm
Web Interface:
http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchange&text_mode=&;
lang
=english
To unsubscribe:         mailto:[EMAIL PROTECTED]
Exchange List admin:    [EMAIL PROTECTED]

_________________________________________________________________
List posting FAQ:       http://www.swinc.com/resource/exch_faq.htm
Web Interface:
http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchange&text_mode=&;
lang=english
To unsubscribe:         mailto:[EMAIL PROTECTED]
Exchange List admin:    [EMAIL PROTECTED]

_________________________________________________________________
List posting FAQ:       http://www.swinc.com/resource/exch_faq.htm
Web Interface:
http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchange&text_mode=&;
lang=english
To unsubscribe:         mailto:[EMAIL PROTECTED]
Exchange List admin:    [EMAIL PROTECTED]


_________________________________________________________________
List posting FAQ:       http://www.swinc.com/resource/exch_faq.htm
Web Interface:
http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchange&text_mode=&;
lang=english
To unsubscribe:         mailto:[EMAIL PROTECTED]
Exchange List admin:    [EMAIL PROTECTED]



_________________________________________________________________
List posting FAQ:       http://www.swinc.com/resource/exch_faq.htm
Web Interface:
http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchange&text_mode=&;
lang=english
To unsubscribe:         mailto:[EMAIL PROTECTED]
Exchange List admin:    [EMAIL PROTECTED]

_________________________________________________________________
List posting FAQ:       http://www.swinc.com/resource/exch_faq.htm
Web Interface:
http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchange&text_mode=&;
lang=english
To unsubscribe:         mailto:[EMAIL PROTECTED]
Exchange List admin:    [EMAIL PROTECTED]



_________________________________________________________________
List posting FAQ:       http://www.swinc.com/resource/exch_faq.htm
Web Interface: 
http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchange&text_mode=&lang=english
To unsubscribe:         mailto:[EMAIL PROTECTED]
Exchange List admin:    [EMAIL PROTECTED]

Reply via email to