OPERATIONAL DEFECT DATABASE
...
...
The transaction log file (.ldf) for the Veeam ONE configuration database (VeeamONE) consumes an unexpectedly large amount of disk space.
This occurs when the Recovery Model of the VeeamONE configuration database is set to Full or Bulk-Logged. Note: By deafult, Veeam ONE expects and configures its configuration database to use Simple recovery model, and as such, does not automatically truncate the transaction logs for its database.
Consider the following: The Veeam ONE configuration database is highly transactional as it frequently collects new data from the environment, this in turn causes the transaction logs to grow. The Veeam ONE configuration database (VeeamONE) should be configured to use the Simple recovery model. If the configuration database must be set to the Full recovery model because the database has been added to a SQL Server Always-On Availability Group, the transaction logs must be truncated by the user.
The growth of the transaction logs (.ldf) is impact by the Data Collection Mode used by Veeam ONE. For more information about the different Data Collection Modes, please review:Veeam ONE Deployment Guide > Data Collection Mode For more information about Data Collection Mode metrics, please review:Veeam ONE Deployment Guide > Appendix B. Data Collection Modes For information about changing the Data Collection Mode after Veeam ONE is installed, please review:Veeam ONE Monitoring Guide > Appendix A. Veeam ONE Settings Utility > Scalability > Data Collection Mode
Veeam Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.
