I strongly recommend that you do not run Backup Exec System Recovery (BESR) along side ShadowProtect.
I also recommend that you run Backup Exec by itself, with no other backup products installed, and then perform some very rigorous tests so that you can see for yourself what Backup Exec does to your data. And, if you actually do these test, and you don't mind sharing your results, then please report the results here as I'm sure everyone will find them to be very interesting.
Here's the test I suggest you perform:
1) First set up a test Exchange Server on a clean Windows Server installation with no 3rd party apps installed. Test its database to ensure that it's not corrupt.
2)
Install one of the backup products you wish to test (Backup Exec, in this case). Configure it to
generate incremental backups of the volume that contains your Exchange
database every fifteen minutes
3) Next use LoadSim to place massive load on the Exchange server.
4)
Let it run for a few hours. Does the product even allow you to backup
Exchange like this without taking Exchange down altogether? It's an
important question and one with an interesting answer. Can your
business afford to take down its email server?
5) Stop LoadSim. Stop the backups. Stop Exchange.
6)
Before restoring Exchange, test it to see if the original database (not the backup) is still good
(not corrupt).
7) With each incremental, in turn, restore it, then test
the Exchange database for corruption. Was the Incremental that you
just restored basically useless (your Exchange database is corrupt
after the restore)?
NOTE:
If you are performing the above sequence of tests on the Small Business
Server edition of Windows Server 2003, then you must enable the
Exchange VSS writer (as it's disabled by default on SBS) prior to
running these tests. For more information see:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q838183
If you're running Server 2003 SP1 then you should also contact Microsoft and obtain and apply this VSS hotfix:
http://support.microsoft.com/kb/923628