No full backup file present or Database Migration service could not access the file

Nilesh Patel 111 Reputation points
2022-02-08T13:00:27.36+00:00

172247-backup-error.png

I am migrating my on-premise SQL server to Azure SQL MI using Azure DMS. I have provided the full database backup to my SMB network share path. I have successfully created Azure Database Migration Project under Azure Database migration Service, during the last phase of the project I am getting validation error.

Error detail: No valid full backup found for database 'DBNAME'. Either there was no full backup file present or Database Migration service could not access the file.

I don't know where I made mistake can anyone please guide me on this.

Thanks,
Nilesh

Azure Database Migration service

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. GeethaThatipatri-MSFT 29,007 Reputation points Microsoft Employee
    2022-02-10T19:31:46.45+00:00

    Hi, @Nilesh Patel I did some research and found the below configuration settings for SMB share, prerequisites, and known issues if it might help you to fix the issue.

    1. Configure Migration settings.
    2. Prerequisites
    3. SMB file share connectivity
      there is a full backup for source SQL DB on the shared file system (SMB Share)
      The credentials used to copy the backup file to or from the file share to the target system should have read/write permission to access the file share.

    Verify you can do restore header only RESTORE HEADERONLY FROM DISK = N'\<SMB file share path>\full.bak'
    Note:- the time of restore headeronly shouldn't be long (less than 10minutes) and the output should match the selected source database name with the DatabaseName in RESTORE HEADERONLY.

    In case The RESTORE HEADERONLY query is taking over 10 mins. the workaround is to use the compressed option and stripe backup into 8/10 files for the backup.

    Regards
    Geetha