Possible solution for you.
I also backup sql and use backupexec.
If you are using the sql agent as I first started doing (thinking it was the right thing to do), Stop using it.
After some research I found that the way I was backing up sql was all sorts of bad.
The best way to back up sql (regardless of platform) is to use the backup utility in sql.
Here is my backup plan for our sql db's.
Every day at 11 pm, sql does a full backup of the db to a separate drive/volume. The backups are configured to keep a backup for 2 days, then delete anything older. The bu normally takes 3 hours. The time will vary.
Now also set your sql server to backup the transaction logs. A good time frame for this is every ten minutes. Againsend it to the same volume as the db bu.
At 4 am Backup exec runs an Incremental (very important, the incremntal picks up the new bu instead of all of them. You do not need the trans logs. They are of no use at that point.
The logic here is: you do not want any external entities being intrusive to your db. Sql I have found is very sensitive to this and the last thing you want is a corrupt db. It is also easier to restore the db from a sql bu then from a backuexec restore, and faster since it is from disk!!!
The last thing you want is a corrupt sql db.
Yes I wasted the cash on the sql agent not knowing any better. If something happens to the bu exec job, at least I know that the sql db is being backed up.
Just some knowldge from someone who's been in your shoes.
