User Tools

Site Tools



Ahsay Backup Software

Backup Set Types

Supported Storage

Features in OBM / ACB

Features in CBS

Brand and Customize



Performance Testing

FAQs and Known Issues

Can't Find What You Need?


ISSUE: No database file found (MS SQL database backup)

Article ID: 5318
Reviewed: 13/03/2018

Product Version:
AhsayOBM: or above
OS: Windows

Problem Description

When performing a MS SQL database backup (ODBC backup mode), the following error message is received in the backup report:

No. Type Timestamp Log
* ... ... ...
* info ... No full file found for in-file delta backup files. Path="SQL_hostname\...\db_name.bak".
* erro YYYY/MM/DD hh:mm:ss No database file found for "SQL_hostname\...\db_name"
* ... ... ...


The message suggests that the database file of the corresponding database cannot be found in the backup destination, possible cause may be:

  • Data corruption in the backup destination
    Corrupted file (data blocks of the database file) deleted by the data integrity check.

  • Backup issue during a previous backup job
    Database file was not properly uploaded to the backup destination during a previous backup.


To resolve the issue, refer to the following steps:

  • Data corruption:

    Check if there is hardware or I/O issue with the corresponding backup destination.

    • Windows
      For backup destination that are located on a Windows computer, check in the Event Viewer to confirm if there is any error.  If a disk error is found, perform a check disk on the affected partition by entering the following command in command prompt.

      chkdsk /f
    • Linux
      For backup destination that are located on a Linux computer, confirm if there is any error found:

      cat /var/log/messages
      If a disk error is found, perform a check disk on the affected partition by enter the following commands with the partition un-mount.

    • Network volume
      For backup destination on a network volume, ensure that a stable connection can be established between the backup client and destination for the duration of a backup.

  • Backup issue during a previous backup job:

    Check on the previous backup reports for any error, or contact Ahsay support representatives for further assistance.
For both cases, perform a Data Integrity Check for the affected backup set (Instruction), then perform a Full database backup afterward.

The same error will still be displayed during the next Full database backup job, the problem will be resolved after the database file is uploaded properly. Do not interrupt the database backup job when an error is displayed.


sql, odbc, require, required, miss, missed, missing

public/5318_no_database_file_found.txt · Last modified: 2018/03/21 13:48 by edward.chan