Question : Exchange services need to be restarted after full backup exec job

I'm running exchange 2003 sp2 on a ms server 2003 r2 sp2.  i've increased the xchange mail store size to 70 gb in the registry. i'm running a nightly full backup -one job- of the entire server (local disks, system state,  + info store) via backup exec 12, going to a B2D folder; the backup exec exchange agent is being used.  I am not using NTbackup whatsoever

The backup jobs complete successfully, but every OTHER morning I have to restart the exchange services in order for all outlook clients to be able to re-connect to server (on our blackberries, when the service needs to be restarted, we get a "message could not be stored" error when sending).  A simple restart of the info store service immediately fixes the problem.

My exchange store is around 23 gb (i have verified the store limit is 70 gb in the registry), so I'm guessing the problem has to do with the accumulation of the logs?  In backup exec, the info store backup options are set to full - db and logs (flush committed logs) and it appears to truncate the committed logs every night.  

Any ideas on what I'm missing?  Is it necessary to separate the info store to a different nightly job?  I was under the impression that if i run a full backup job each night, that i could run the entire server under on job

Answer : Exchange services need to be restarted after full backup exec job

Check this Article for registry limit setting and it is case sensitive.
http://support.microsoft.com/kb/912375

Only once you edit the registry and restart IS and the 1216 event would say that the Limit of the DB is according to the registry then we say its done ...   -:)