https://login.veeam.com/en/oauth?client_id=nXojRrypJ8&redirect_uri=https%3A%2F%2Fwww.veeam.com%2Fservices%2Fauthentication%2Fredirect_url&response_type=code&scope=profile&state=eyJmaW5hbFJlZGlyZWN0TG9jYXRpb24iOiJodHRwczovL3d3dy52ZWVhbS5jb20va2IzMDQ5IiwiaGFzaCI6IjVlN2RjZjY4LTQyOTctNDhmZC04ZjY0LTYzNzZjMmU4MTM5MCJ9
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.
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:
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!
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
Knowledge base content request
