July 22, 2003 at 11:22 am
I had five DB on one SQL Server 7.0 fail this morning with an error that I am having trouble with. Each DB is set to do a complete backup to their respective dump device and verify that it was a successful backup.
The error is as follows:
Read on 'CCA_Bat' failed, status = 87. See the SQL Server error log for more details. [SQLSTATE 42000] (Error 3203) Backup or restore operation terminating abnormally. [SQLSTATE 42000] (Error 3013) Associated statement is not prepared [SQLSTATE HY007] (Error 0) The backup set is valid. [SQLSTATE 01000] (Message 3262). The step failed.
Later this morning I re-ran the failed backups manually, and everything worked fine.
If anyone has experienced this issue, I would greatly appreciate hearing what you found out about the issue and what you did to fix it.
July 22, 2003 at 3:18 pm
The SQL backups maybe conflicted with a tape backup running around that time and locking the files/directory?
(just a wild guess though)
Cheers,
- Mark
July 23, 2003 at 8:04 am
Do you have any other jobs running against the database at the same time?
July 23, 2003 at 8:39 am
mccork,
The tape backups finished at 10:30 pm. The database dumps start at 12:05 am.
This job has been running successfully for the past 4 months, and now it is failing for the reason in my previous post.
Nothing has changed on the server that I know of. My boss who is the only other person who has access to this server does not know of any changes either.
In fact, the same databases failed again today for the same reason.
July 23, 2003 at 2:46 pm
What is "CCA_Bat"? The backup file or device? Is it overwritten or appended to? Is there enough space in the drive? Does the failure occur for every db? Anything written to the error log, or have you already posted all the associated errorlog entries?
Cheers,
- Mark
July 23, 2003 at 10:26 pm
If the backup device is a disk backup device, check your system administrator that the o/s backup including such directory where your device sits is not backed up at the same time.
Try reschedualing the backup to another time.
July 25, 2003 at 8:47 am
Thanks everyone for your advice. The issue turn out to be some software from CA called ETrust (anti-virus software) that did an automatic update of its software on the night before my backups ran. When we turned off the ETrust services so that ETrust was off, the backups were successful. We have filed a trouble ticket with the ETrust support line to find out why this is happening and how to fix it.
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply