Post reply

Failure on backup device - Operating system error 64

  • November 23, 2010 at 1:59 am

    #388286

    Hi,

    My company delivers software to other companies. We take care of the databases and their backups.

    Not the hardware or where they put their backups.

    In one company we keep getting the following error:

    BackupDiskFile::RequestDurableMedia: failure on backup device 'sharename’. Operating system error 64 (error not found).

    BACKUP failed to complete the command BACKUP DATABASE …. Check the backup application log for detailed messages.

    There are 8 databases of which the backup is always successful. Sometime number 9 gives this error.

    Even after changing the order of backups, it is always the same db.

    The funny thing is that the backup is on the share and if I perform a ‘RESTORE FILELISTONLY’ it is successful.

    There is no logical sequence. Sometimes we get the error every day; sometimes the errors are two weeks apart.

    It even happens during the weekends when there is practically no network load.

    Placing the backup on a local drive is not an option for that company.

    I hope you can help.

    Thanks

    Lindsay

  • November 23, 2010 at 2:07 am

    #1254234

    Lindsay

    Go to a command prompt and type net helpmsg 64. This will tell you what the error message means. Looks like your network is somewhat flaky.

    John

  • November 23, 2010 at 2:14 am

    #1254240

    John, thanks for the quick reply.

    I thought it might be something along those lines.

    But I don’t understand is why it is always on the same db?

    I've change the backup sequence many times. Sometimes this db is taken first, second, third,...

    But it always fails on the same db. And the backup is successful.

    So why do I get that error?

    Lindsay

  • November 23, 2010 at 3:44 am

    #1254288

    Lindsay

    Is the database in question significantly larger than the others? Have you done a RESTORE VERIFYONLY on the backup file? Is this done as part of the backup job (if not, it should be)?

    John

  • November 23, 2010 at 4:07 am

    #1254314

    John,

    The database is not that big (3,5 GB). There are other, bigger db's (10 GB) and they don't give errors.

    I've just performed a RESTORE VERIFYONLY, the result was: The backup set on file 1 is valid.

    This is not part of the backupprocedure.

    Lindsay

  • February 1, 2011 at 12:54 am

    #1280781

    Hi, we found the solution to out problem.

    It turns out our .trn backup files where corrupt.

    By adjusting our maintance plan ( the one that makes the trn backups ) we no longer have this problem.

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

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