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=eyJmaW5hbFJlZGlyZWN0TG9jYXRpb24iOiJodHRwczovL3d3dy52ZWVhbS5jb20va2IyMjEwIiwiaGFzaCI6IjhlMDY3NDFjLTE3MGYtNGFjYS05NzFlLWU5OTI1N2ZjODE0YSJ9
1-800-691-1991 | 9am - 8pm ET
EN

Understanding the influence of different database recovery models on Veeam ONE operation

Challenge

Transaction log files for the Veeam ONE database grow too large or take up all available space on disk.

Cause

If you use the Full or Bulk-Logged recovery model for the Veeam ONE database, and collect a large amount of data from the virtual environment and backup infrastructure, database transaction log files can quickly grow in size.

Solution

Starting with version 9.5, Veeam ONE forcibly sets the recovery model to Simple when the database is created during installation. This type of recovery model prevents uncontrolled growth of database files. 
However, for some configurations, such as SQL Server Always-On Availability Groups, the recovery model cannot be set to Simple. To reduce the amount of collected and stored data, you may consider changing Veeam ONE data collection mode. For details, see KB2179.
 

More information

If you have any questions, contact Veeam Support.
KB ID:
2210
Product:
Veeam ONE
Version:
9.x, 10.x
Published:
2016-12-28
Last Modified:
2020-08-13
Please rate how helpful this article was to you:
5 out of 5 based on 1 ratings
Thank you for helping us improve!
An error occurred during voting. Please try again later.

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

Knowledge base content request
By submitting, you agree that your personal data will be managed by Veeam in accordance with the Privacy Policy.

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.