I do this on 3 different customers NT 4 SBS servers and on my own SBS server.
The stopex makes the exchange server services stop and then the backup runs. I checked the logs for the backup program (it does not matter which backup program you use)and found how long it took. Then the startex starts all the services again after the backup should have completed to be ready for the users the next morning.
Commands to stop the Exchange Server at night
at 23:00 /EVERY:M,T,W,Th,F "c:\stopex.bat"
Command to start the Exhange Server each morning
at 7:00 /every:T,W,Th,F,S "c:\startex.bat"
Notice I use the at command to schedule the jobs to happen before and after the backup.
This is the startex.bat file
net start "Microsoft Exchange Event Service" > C:\strtexch.log
net start "Microsoft Exchange Internet Mail Service" >> C:\strtexch.log
net start "Microsoft Exchange Information Store" >> C:\strtexch.log
net start "Microsoft Exchange Message Transfer Agent" >> C:\strtexch.log
net start "Microsoft Exchange Directory" >> C:\strtexch.log
net start "Microsoft Exchange System Attendant" >> C:\strtexch.log
This is the stopex.bat file
net stop "Microsoft Exchange Event Service" > C:\strtexch.log
net stop "Microsoft Exchange Internet Mail Service" >> C:\strtexch.log
net stop "Microsoft Exchange Information Store" >> C:\strtexch.log
net stop "Microsoft Exchange Message Transfer Agent" >> C:\strtexch.log
net stop "Microsoft Exchange Directory" >> C:\strtexch.log
net stop "Microsoft Exchange System Attendant" >> C:\strtexch.log
The strtexch.log just shows if there are any errors starting or stopping the services.