RE: Exchange 2000 Offline Backups

  • From: "Linda Wilson" <lwilson@xxxxxxxxxxx>
  • To: "[ExchangeList]" <exchangelist@xxxxxxxxxxxxx>
  • Date: Wed, 11 Dec 2002 10:05:12 -0800

My experience with Backup Exec and batch files is it doesn't work... our 
workaround has been to run the batch files on the Exchange server using 
Scheduled tasks...  one to stop the services prior to the backup job and the 
other to start again after the backup has completed...

-----Original Message-----
From: Cox, Christopher [Allen & Heath UK] [mailto:Chris.Cox@xxxxxxxxxxxxxxx]
Sent: Wednesday, December 11, 2002 8:36 AM
To: [ExchangeList]
Subject: [exchangelist] Exchange 2000 Offline Backups

I don't know whether you have come across this one but it has totally perplexed 
me and I can't find anything on the web to suggest what is happening.

I have been reading various papers on Exchange 2000 disaster recovery. And the 
common suggestion is that it is good to have an offline exchange server in the 
background that can be used to recover lost users data or in the event of a 
disaster rebuild your site.

However, to achieve this, you need to have an offline backup of your server, 
databases, log files, system state etc. 

Veritas Backup Exec allows you to do this by including an "execute before 
backup starts" and an "execute after backup completes" batch file when you run 
a job. They suggest on their tech support site to use the following script 
which we have copied and used:


NET STOP pop3svc /yes

NET STOP imap4svc /yes

NET STOP MSExchangeES /yes

NET STOP MSExchangeMTA /yes

NET STOP MSExchangeIS /yes

NET STOP MSExchangeSA /yes

NET STOP MSExchangeSA /yes

This shuts down all the services before the backup starts. A similar batch file 
starts the services following completion of the backup.

The only problem is that it does not appear to work.

If you execute the batch file from windows by double clicking it's icon in 
explorer (when logged on with the backup exec service account) the batch file 
works fine and all the services are properly shut down.

However, when run from the backup software, although the log file shows that 
the batch file has been run, the services are not shut down and the .edb and 
.stm files are not backed up (says skipping open files).

This seems bizarre. We used to use a script with Exchange 5.5 every once in a 
while and I know that that worked.

My thoughts are that maybe the Windows 2000 security patches (lockdown.exe and 
urlscan.exe) are preventing command line access to the backup exec program. 
Could this be so and have you seen anything similar?

Happy Chrismas and all the best.

Chris Cox   BEng, DiplEng

Information Technology Manager

Allen & Heath Limited,Kernick Industrial Estate,Penryn

Cornwall. UK TR10 9LU

Tel +44 (0)870 7556250, Fax +44(0)1326 370139

Direct: +44(0)870 7556270 Mobile +44(0)781 555 1962

EMail  <mailto:chris.cox@xxxxxxxxxxxxxxx> chris.cox@xxxxxxxxxxxxxxx Web  

This Email and any files transmitted with it are confidential and intended 
solely for the use of the individual to whom or the entity to which they are 
addressed. If you have received this email in error please notify the sender 
immediately. Please note that any views or opinions presented in this email are 
those of the author and do not necessarily represent those of Allen & Heath 
Limited. The recipient should check this email and any attachments for the 
presence of viruses. Allen & Heath Limited accepts no liability for any damage 
caused by any virus transmitted via this email. 
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 $subst('Email.Unsub') 

Other related posts: