Groups | Blog | Home
all groups > sql server (alternate) > april 2004 >

sql server (alternate) : SQL backup job - failed



tpthai NO[at]SPAM pepco.com
4/7/2004 8:27:32 AM
Hi,
Appreciated anyone who can help us with our problem. Our backup job
for ROUTT database has been failing for the last 4 days. It was
working fine for almost a year now. The only thing happened few days
before the problem started is the addition of more memory to the
server because we've been getting the low virtual memory error. There
are two databases in this server so we have two backup jobs everyday.
The other backup job runs with no problem. Can someone give us any
suggestion please. Listed below is the sql log.

Thanks,
Teresa


ROUTT Database Backup Log
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 945: [Microsoft][ODBC
SQL Server Driver][SQL Server]Database 'ROUTT' cannot be opened due to
inaccessible files or insufficient memory or disk space. See the SQL
Server errorlog for details.

ROUTT Transaction Log Database Backup Log
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 945: [Microsoft][ODBC
SQL Server Driver][SQL Server]Database 'ROUTT' cannot be opened due to
inaccessible files or insufficient memory or disk space. See the SQL
Server errorlog for details.


SQL Sever ErrorLog

2004-04-02 21:16:05.65 spid54 udopen: Operating system error 32(The
process cannot access the file because it is being used by another
process.) during the creation/opening of physical device
D:\MSSQL\MSSQL\Data\ROUTT_Data.MDF.
2004-04-02 21:16:05.65 spid54 FCB::Open failed: Could not open
device D:\MSSQL\MSSQL\Data\ROUTT_Data.MDF for virtual device number
(VDN) 1.

2004-04-05 21:31:06.90 spid57 udopen: Operating system error 32(The
process cannot access the file because it is being used by another
process.) during the creation/opening of physical device
D:\MSSQL\MSSQL\Data\ROUTT_Data.MDF.
2004-04-05 21:31:06.90 spid57 FCB::Open failed: Could not open
device D:\MSSQL\MSSQL\Data\ROUTT_Data.MDF for virtual device number
(VDN) 1.

2004-04-06 00:30:10.89 backup BACKUP failed to complete the command
BACKUP LOG [ROUTT] TO DISK =
N'D:\MSSQL\MSSQL\BACKUP\ROUTT_tlog_200404060030.TRN' WITH INIT ,
NOUNLOAD , NOSKIP , STATS = 10, NOFORMAT

2004-04-06 00:45:01.12 backup BACKUP failed to complete the command
BACKUP DATABASE [ROUTT] TO DISK =
N'D:\MSSQL\MSSQL\BACKUP\ROUTT_db_200404060045.BAK' WITH INIT ,
louisducnguyen NO[at]SPAM hotmail.com
4/7/2004 2:48:55 PM
Leythos
4/8/2004 4:58:54 AM
In article <7fedd9b2.0404070727.6ebb971e@posting.google.com>,
tpthai@pepco.com says...
[quoted text, click to view]

Maybe a BIG transaction log and an increase in the DB size? How much
disk space do you have free on the drive you are doing the backups to?


--
--
spamfree999@rrohio.com
jpmcginty NO[at]SPAM talk21.com
4/8/2004 6:34:08 AM
[quoted text, click to view]

I would test that you do a manual backup. This will remove any
problems that you may have regards to scheduling the job. Assuming
that you have enough disk space I'd set up a performance monitor trace
to check the SQL memory and other parameters to check what is going
on.

tpthai NO[at]SPAM pepco.com
4/14/2004 4:29:50 PM
[quoted text, click to view]

Hi,
Thank you very much for helping us out. It turned out that the
application is still link to the database when the backup ran.

Thanks,
AddThis Social Bookmark Button