Skip to main content

[V12] Veeam Backup Config restore failed ! Workaround

  • February 20, 2026
  • 3 comments
  • 19 views

Stabz
Forum|alt.badge.img+8

Veeam Backup Configuration Restore – MS SQL Error & Workaround

Context

During a Veeam Backup & Replication configuration restore on a new server, I encountered an error. “XML Parsing: document parsing required too much memory”

  • Source server: MS SQL Standard Edition
  • Destination server: MS SQL Standard Edition (same version)

What I tried

  1. Same MS SQL Standard Edition → Same error
  2. Migrated to MS SQL Express Edition → Same error
  3. Switched to PostgreSQL → It worked!

This confirmed that the issue was related to MS SQL.

Veeam Support Recommendations

Veeam Support provided two options:

Option 1: Restore without session history or backup/replica catalog

Restore the configuration backup without the session history or backup/replica catalog.

⚠️ In my case, this did not resolve the issue.

Option 2: Change the SQL bulk write method to row-based writing

If the SQL Server is dedicated to Veeam and does not host any other production database, you can change the way SQL writes its data by switching from "bulk" to "rows" via the following registry key:

HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Backup and Replication\ConfBackup

Add the following value:

DatabaseWriter (REG_DWORD) = 0

Steps:

  1. Add the registry key mentioned above
  2. Restart the Veeam Backup & Replication service
  3. Restart the SQL Server service
  4. Retry the configuration restore

Takeaway

If you are stuck with MS SQL during a configuration restore, consider:

  • Switching to PostgreSQL as a quick workaround
  • Or applying the registry fix provided by Veeam Support if you want to stay on MS SQL

 

Cheers

3 comments

Link State
Forum|alt.badge.img+11
  • Veeam Legend
  • February 20, 2026

thank you for sharing workaround. 😎


coolsport00
Forum|alt.badge.img+21
  • Veeam Legend
  • February 20, 2026

Another ‘good to know’ post Philippe. Thank you!


Chris.Childerhose
Forum|alt.badge.img+21
  • Veeam Legend, Veeam Vanguard
  • February 20, 2026

Interesting workaround for this one.  Thanks for the share.