We have a busy SQL 2005 database server which is used for reporting. If a report happens to run during the backup process it will cause SQL sever to become unresponsive until the backup is cancelled.
The issue is obviously the server becomming completely swamped with both SQL server and BE agent running at the same time, but is their anyway to soften the footprint the Agent makes on the SQL backup?
There is no way to limit the resources used during backup. When you backup a SQL database using the BE SQL agent, what BE does is to call the SQL engine to dump the database. In your case, the SQL engine is both processing the database for the report and dumping it at the same time.