Backup doesn't write to file

[icemel]

Hi,

Does anyone know why a backup would not write to a backup device?

The backup is large, yes. A complete backup is about 130 GB.

The backup devices is defined to write to a mapped drive. This has worked fine in the past.

But for some reason, this month, when I start the backup - it just hangs... no error messages... the backup name appears in the directly (so it can find the location ok) - but it just doesn't write any data! Size remains at 0.

When I stopped the backup job, the file name disappears from the directory, meaning it never actually wrote anything.

Not sure how to troubleshoot this.

Thanks much

 

[SQLBill]

Have you looked for error messages in the SQL Server Error Logs? Are you running the backup as a job? If so, find the job in Enterprise Manager, right click on it and select VIEW JOB HISTORY. Then check the box for show job steps. Look through the history to see if there are any messages refering to the failure.

-SQLBill

Posting advice: FAQ481-4875

 

[icemel]

Hi SQLBill,

There is no history, because it never actually runs, and there are no error messages either.

 

[SQLBill]

Wow. Everytime I have a backup job fail, there's always an error message and history. Even if it only says that access was denied.

Have you tried running the job manually, by right clicking on the job and selecting Start Job? Have you tried running the script from Query Analyzer?

What permissions does the SQL Server Agent service have? Have the permissions changed?

-SQLBill

Posting advice: FAQ481-4875

 

[icemel]

Yes, it's kinda strange. Never had a problem like this before where the backup job just hangs forever, never writes one byte of data.

I think I might try running manually, although it seems to be some kind of other type of system error.

Like I said, the backup name appears in the directory once I start the backup but the size remains at 0. And if I stop the job, the file name just disappears... so it never really exited to begin with.

Same job ran fine last month.

Also, it's writing to a LOCAL drive, not a mapped drive as I said earlier. Space is not an issue. There's plenty.

 

[DrSql]

First of all try to run this from a Query Analyzer and see what happens..


RESTORE DATABASE MyDb
FROM Disk = '\\serverA\Mssql\Backup\Mydb.bak'
WITH STANDBY = 'C:\MSSQL\Log\undoMyDb.ldf', MOVE 'MyDb_Data' TO 'C:\MSSQL\Data\MyDb_data.mdf',
MOVE 'MyDb_log' TO 'C:\MSSQL\Log\MyDb_log.ldf'
GO
Try this


Dr.Sql
Good Luck.