SQL 2000 Backup error | SQL Server Performance Forums

SQL Server Performance Forum – Threads Archive

SQL 2000 Backup error

Hi, Can someone help me with this , I get this error every 2nd day!!! And on more than One server! I have a backup script that uses a cursor to go through the databases and back them up
with the normal Backup Database Statement. And it is set to overwrite everyday. This is the error that I get!
Job Step Error: [SQLSTATE 01000] (Message 3014) Cannot open backup device ‘F:DatabasesBackupFANS’. Device error or device off-line. See the SQL Server error log for more details. [SQLSTATE 42000] (Error 3201) BACKUP DATABASE is terminating abnormally. [SQLSTATE 42000] (Error 3013). The step failed. SQL Logs : BackupDiskFile::CreateMedia: Backup device ‘F:DatabasesBackupFANS’ failed to create. Operating system error = 32(The process cannot access the file because it is being used by another process.).
Check whether any existing issues of free space on F: drive. Satya SKJ
Moderator
http://www.SQL-Server-Performance.Com/forum
This posting is provided “AS IS” with no rights for the sake of knowledge sharing.
Hi, I have checked the free space , and there is plenty!
Make sure that no other process like external file backup tools are accessing the file you are trying to backup to.
Do you have anti virus software installed on SQL server?]
Also check what other jobs are running parallely when this happens. Satya SKJ
Moderator
http://www.SQL-Server-Performance.Com/forum
This posting is provided “AS IS” with no rights for the sake of knowledge sharing.
Hi,
There is no other jobs that run at the same time , but there is a Virus app on the Box. Is there a way for me to log what system resources is locking the files?
I think PERFMON counters for PROCESS during that time and I’m not sure about one utility available fromhttp://www.sysinternals.com website, may check it. Satya SKJ
Moderator
http://www.SQL-Server-Performance.Com/forum
This posting is provided “AS IS” with no rights for the sake of knowledge sharing.
You should check your windows event logs to see if there is any more information about what may be tying up that location. Jason
Hi , I will monitor this and let you know.
Thanks…
]]>