RE: Exch2k SP3 broke my server!

  • From: "david" <apba08@xxxxxxxxxxxxx>
  • To: "'[ExchangeList]'" <exchangelist@xxxxxxxxxxxxx>
  • Date: Fri, 7 Mar 2003 20:25:58 -0000



I don't know whether or not my experience will help. I work at two
schools one running NT4 Server and Exchange Server 5.5 with one back-up
system, the other running two, Win 2K servers Exchange Server 2K and
both backing up.


I have found back up to be unreliable at both locations and all servers,
in that sometimes it works and sometimes it doesn't - seemingly at


What I have found is that if the back-up batch files are not perfectly
correct then back-up will not close down. Other mistakes that have the
same effect are forgetting to put a tape in the drive before the back-up
is scheduled or (and haven't we all done it:-)) forgetting to set the
tab on the tape to "unlocked"!  Any subsequent scheduled back-ups
obviously won't run either. Looking at task manger it is clear to see
that back up is still running. What's more is that it won't close using
the normal "end task" process. In fact, the only way I can get it to
close is to re-boot the server!


Another example of the type of problem that leaves back-up open is that
I had the closing inverted commas on the wrong side of the \ in a path I
wanted to back up.


So use task manager to see if back-up is running all the time.




ADvid S.


-----Original Message-----
From: Chris Nielsen [mailto:cnielsen@xxxxxxxxxxxxxxx] 
Sent: 06 March 2003 22:41
To: [ExchangeList]
Subject: [exchangelist] Exch2k SP3 broke my server!

My main Exchange server here won't let me schedule any backups with
ntbackup anymore.


I had set it up a while ago to backup the System State on a rotating
schedule, and those backups were working fine for weeks. One of the last
steps finalizing my Exchange setup was to install Service Pack 3. That
went ok, so I decided Exchange was in good working order and proceeded
to set up some incremental and normal Exchange backups on a good
schedule. The backups would not stick! I thought it might just be the
weird way ntbackup interfaces to Exchange to back it up, but Exchange
was on this machine when I set up the System State backups and they
worked fine. I tried to schedule new file backups, really simple ones
like a single folder, nothing to do with Exchange. They would not stick


A friend of mine told me it seemed like he'd seen this before and that
deleting all scheduled backup jobs and starting over did the trick for
him. So I deleted my existing System State backups and tried from
scratch. Still nothing! So now I'm stuck with no System State backups on
top of it. argh.


Anybody has seen this before or have any clues? Time to call MS?




Chris Nielsen

Systems Administrator

New Dawn Technologies


List Archives:
Exchange Newsletters:
Exchange FAQ:
ISA Server Resource Site:
Windows Security Resource Site:
Windows 2000/NT Fax Solutions:
You are currently subscribed to this Discussion List as:
To unsubscribe send a blank email to

Other related posts: