BACKUP DATABASE is terminating abnormally.

Question

BACKUP DATABASE is terminating abnormally.

Willian.Funes

Ten Centuries

Points: 1203
More actions
April 20, 2010 at 5:57 pm

#156888

Hi All,
I have a problem when I try to make a backup database into file or backup device. Im using a backup task in Maintenance Plan that write in a backup device located in partition F: (Curiously today at morning works fine) and when I changed the destination to a file, the backup show me a message like that:
10 percent processed.
20 percent processed.
Msg 3202, Level 16, State 2, Line 1
Write on "F:\BACKUP\DATABASE_backup_201004201735.bak" failed: 1117(error not found)
Msg 3013, Level 16, State 1, Line 1
BACKUP DATABASE is terminating abnormally.
PD: When I returned the last state in maintenance plan to write in a backup device, it show me the same message.
The server log show me this message:
BACKUP failed to complete the command BACKUP DATABASE DATABASE. Check the backup application log for detailed messages.
BackupMedium::ReportIoError: write failure on backup device 'F:\BACKUP\DATABASE_backup_201004201735.bak'. Operating system error 1117(error not found).
The folder permissions are Ok and also the free space in partition.
I will appreciate any comments,
WFunes

Viewing 7 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic. Login to reply

Glenn Dorling SSCertifiable Points: 7790 More actions · Answer 1

A 1117 error is an IO_Device error (http://support.tabs3.com/main/R10307.htm is where I go for my OS error codes).

The error message is referring to this being a Write error, so I'd be checking the integrity of the target drive/device.

However, I'd also do a CHECKDB to be on the safe side, in case it's a read error from a database block (although the fact that it works sometimes implies it's a target issue rather than a source issue, as the specific "sectors" it's writing to on the target may vary but the source blocks are always the same).

Steve Jones - SSC Editor SSC Guru Points: 734552 More actions · Answer 2

Steve Jones - SSC Editor

SSC Guru

Points: 734552

April 20, 2010 at 9:44 pm

#1155080

Is f: a local drive?

Willian.Funes Ten Centuries Points: 1203 More actions · Answer 3

yes, is a local drive.

¿do you think is something related with database?

I'm using the same instruction for make a backup into a backup device for another database and works fine.

I just have two database that use the same backup device and show me the same error..

Could help me DBCC database?

Thank's

Willian.Funes Ten Centuries Points: 1203 More actions · Answer 4

I'm making the backup of 6 databases using a backup device or simple file (local partition) and I get the same error just with 2 databases. To discard problems with this 2 database Can I run DBCC database when users are connected? or must be at night. (It's a production database) in fact the most important for the company.

Thanks a lot.

Glenn Dorling SSCertifiable Points: 7790 More actions · Answer 5

I've had false positives (or is it negatives?) from CHECKDB when I've run it in parallel with user activity, so I'd strongly recommend running it out-of-hours. Out-of-hours will also give you scope to immediately address whatever issues are found, instead of waiting until the user go home.

Have you (and can you) tried doing the backup of one of those 2 databases to a different drive? That will help identify whether it's eg. bad sectors on the F: drive or issues within the database.

Willian.Funes Ten Centuries Points: 1203 More actions · Answer 6

I did in different partition and it's work Ok.

Now I'm checking de S.O.

Thank's a lot.

WFunes