Backup SQL database generates error

  • Hi

    I have a server running Microsoft SQL 14 on window server 2012. At december 06 it stopped to take backups every night.

    I got following error message:

    The operating system returned the error '1(Incorrect function.)' while attempting 'ReadFile' on 'C:\Program Files\Microsoft SQL Server\MSSQL12.OPUS\MSSQL\DATA\OPUSDATA\a488f2a0-564d-44ce-8e57-7d5425d5b798\c55b8372-9595-4dce-9b68-16f5f5466a44\00016be8-000001a9-0005

    I have checked if the file in the error message exist and there no such file. I have also run CHECK DB and got a message the that there is no problem with data or have any consistence problem.

    I have also created  stored procesude for searching the entire database including systemdatabases without finding anything.

    Is there any here who know what it could be?

    I added the error message as attachment

     

     

     

     

     

     

     

     

     

    Attachments:
    You must be logged in to view attached files.
  • I found the folder, it was hidden but there is a permission problem with folder and files within it. It is not accessible, I forced to open folder with files with administrator account.

  • Native SQL backups? Do you really have a data path of "C:\Program Files\Microsoft SQL Server\MSSQL12.OPUS\MSSQL\DATA\OPUSDATA\a488f2a0-564d-44ce-8e57-7d5425d5b798\c55b8372-9595-4dce-9b68-16f5f5466a44\00016be8-000001a9-0005"? (The guid directory names seem odd to me, but may be deliberate).

    Does that directory contain mdf/ndf files?

  • Worse than that, it sounds like you're doing backups on the same server that you're backing up.  That's a serious mistake because if the server crashes, not only have you lost the databases, but you've lost the backups, as well.

    You should also check and see if your C: Drive on the server is full.

    --Jeff Moden


    RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
    First step towards the paradigm shift of writing Set Based code:
    ________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

    Change is inevitable... Change for the better is not.


    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)

  • The path does not contain any mdf/ndfs files and the backups are not native. The database gets created first time when installing the software.

  • I create the backup files on this server but backing up is made directly after that to another server. If it crash, I will only lose, less then one hours job. It is ok for the business.

  • The folder OPUSDATA have mdf and ndf files, those are not corrupted. Business have not reported any problems. The backup problems started after the disk was full. Another technician deleted files in the windows temp directory.

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

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