1-800-691-1991 | 9am - 8pm ET
EN

Publishing Microsoft SQL Databases: Insufficient Free Space on the Mount Server

KB ID: 3049
Product: Veeam Backup & Replication
Version: 9.5 Update 4
Published: 2019-11-13
Last Modified: 2020-08-13

Challenge

When publishing a Microsoft SQL database via Veeam Explorer for Microsoft SQL Server, the C drive (C:\) on the mount server is running out of space.

Cause

Veeam Explorer for Microsoft SQL Server saves cache to the C:\Windows\SysWOW64\config\systemprofile\AppData\Local directory folder located on the mount server. Such cache is used to keep changes that you might have made to the published database.

User-added image

Solution

Change the following registry key on the mount server:

Key path: HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Backup and Replication
Key: WriteCacheDirectory
Key type: REG_SZ

Consider the following:
  • Make sure the Key path exists.
  • The WriteCacheDirectory key must be specified without backslash ("\").
KB ID: 3049
Product: Veeam Backup & Replication
Version: 9.5 Update 4
Published: 2019-11-13
Last Modified: 2020-08-13

Couldn't find what you were looking for?

Below you can submit an idea for a new knowledge base article.
Report a typo on this page:

Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!

Spelling error in text

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Your report was sent to the responsible team. Our representative will contact you by email you provided.
We're working on it please try again later
Knowledge base content request
By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Policy.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

ty icon

Thank you!

We have received your request and our team will reach out to you shortly.

OK

error icon

Oops! Something went wrong.

Please go back try again later.