Rob_Swift
18 years agoLevel 3
Backup Exec Bug with SQL Server causes backups to hang?
While trying to backup database "A" in a SQL Server 2005 environment (or SQL Server 2000), the Backup Exec process gets blocked by another SQL process and hangs until the other process completes. The problem is that for some unknown reason Backup Exec is running the following SQL in a different database (database "B"):
select dpages,name
from B..sysindexes
where indid<>0 and indid<>1 and indid<>255
Both database A and B are user databases (not master, msdb). As far as I can tell, Backup Exec runs this in EVERY SQL Server database before every backup is executed. In other words, if I have databases A, B, C, ...Z then Backup Exec would run the above query in each of the 26 databases before every backup is run. In our environment we have users that will be creating a new table (which indeed puts a lock on sysindexes as it tries to add a row with indid = 0) and this create is a long running procedure. This causes Backup Exec to be blocked in SQL Server because it cannot get the shared lock needed for the query above. Several times this has caused us to lose an entire night of backups.
select dpages,name
from B..sysindexes
where indid<>0 and indid<>1 and indid<>255
Both database A and B are user databases (not master, msdb). As far as I can tell, Backup Exec runs this in EVERY SQL Server database before every backup is executed. In other words, if I have databases A, B, C, ...Z then Backup Exec would run the above query in each of the 26 databases before every backup is run. In our environment we have users that will be creating a new table (which indeed puts a lock on sysindexes as it tries to add a row with indid = 0) and this create is a long running procedure. This causes Backup Exec to be blocked in SQL Server because it cannot get the shared lock needed for the query above. Several times this has caused us to lose an entire night of backups.
To me this is a bug in Backup Exec since there is no need for Backup Exec to query other user databases (i.e. database "B") when I asked it to backup database "A".
I posted essentially this same comment/question in the 10d forum a couple of months ago, and got no response. We have now upgraded to the latest 11d version and the problem still exists. Is there a way to change this behavior?
Thanks
Rob