Restore Fails for Database with Consecutive Backslash Characters in File Path

Veeam Explorer for Microsoft SQL Server reports the error:

Inconsistent database metadata. See the log for details.

One or more database file paths contained multiple consecutive backslash characters when the SQL server was backed up.

Clarifying Issue

This issue cannot be discovered in the GUI of SQL Server Management Studio, because it splits the full file path onto folder path and filename.

To check that the database file paths contain multiple consecutive backslash characters, open SQL Server Management Studio and run the following query against the database reported by Veeam:

SELECT * FROM Sys.Database_files

The query should return a list of database files and their paths (check the "physical_name" column). Below you may see the example of the incorrect path:

D:\Database Files\\DatabaseExample.mdf

In the logs the issue appears with the following trace:

10 (5524) Access to directory granted
10 (5524) Getting file size: C:\VeeamFLR\SQL2008_90f828a2\Volume1\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\DATA\\TEST.mdf...
10 (5524) Error: The filename, directory name, or volume label syntax is incorrect

This issue could appear in the following cases:

• A script used for database creation contains a double backslash in the "Path" variable.
• The file path for the additional database files was entered with a doubled backslash.

Deploying Hotfix

NOTE: The hotfix is compatible only with Veeam Backup & Replication 10. Customers running earlier versions are advised to upgrade to version 10 first and then install the private fix.

In Veeam Backup & Replication 10, we implemented a mechanism that verifies database paths and automatically replaces a doubled backslash with a single backslash to avoid any issues during a restore.

There is a hotfix required to implement this mechanism for Veeam B&R 10.0.0.4461:

1. Download the hotfix.
2. Check the current version of Veeam Backup & Replication. It must be 10.0.0.4461.
3. Make sure that no jobs are running, close the console, and stop all Veeam services.
4. Unpack the archive to a TEMP folder
5. Replace the original files located in the folder below with the hotfix files:

• C:\Program Files\Veeam\Backup and Replication\Explorers\SQL\

DOWNLOAD HOTFIX