Once Veeam ONE database reaches the maximum allowed size, Veeam ONE will not be able to continue data collection thus affecting data accuracy and alarms generation.
If you choose to host the Veeam ONE database on Microsoft SQL Server Express, be informed there is a 10 GB database size limitation for this edition. For details, see Editions and Supported Features for SQL Server.
Database migration (permanent solution)
The best way to resolve the issue would be to move Veeam ONE database to a Standard or Enterprise edition of MS SQL Server. The procedure for configuring Veeam ONE to use a new SQL Server connection is described in the following KB article: http://www.veeam.com/kb1599
Purging old data (temporary workaround)
You can also address the issue by purging old performance data as described below.
You can delete past performance data via a custom SQL script that should be run against Veeam ONE database. Follow these steps to reduce the database size:
- make sure to properly backup Veeam ONE database;
- be aware that this change will touch all of Veeam ONE components: for example in Veeam ONE Reporter you will not be able to build reports that rely on the data that you delete with the script presented below;
- keep in mind that all graphs in Veeam ONE Monitor that rely on the deleted data that will be unavailable;
- unless specifically instructed by Veeam Support, do not modify the SQL statement and do not execute it against other database tables. If the aforementioned workaround does not help to reduce the database size, please contact Veeam Support for further assistance.
CHECKPOINT DECLARE @dt DATETIME SET @dt = CONVERT(DATETIME, '2018-01-25 00:00:00.001' ,120) WHILE EXISTS (SELECT * FROM [monitor].[perfsamplelow] WITH(NOLOCK) WHERE [timestamp] < @dt) BEGIN BEGIN TRAN DELETE TOP (50000) FROM [monitor].[perfsamplelow] WHERE [timestamp] < @dt COMMIT TRAN CHECKPOINT END DBCC shrinkfile (N'VeeamOne', 1)
2017-01-25 00:00:00.001 - the point in time before which the historical performance data will be purged. Change the date accordingly.
4. Execute the statement against Veeam ONE database.
NOTE: this operation can cause significant workload on the database and growth of the database transaction log. Make sure you do not have mission-critical databases on this server.
5. Start Veeam ONE Monitor and Reporter services on the Veeam ONE server.
Reducing further database growth rate
Before applying any of the approaches described below, you will need to migrate the DB to a standard or enterprise installation of MS SQL Server or purge the old data.
Changing the scalability mode from Typical to Advanced
In the Advanced mode, the data collections are less frequent and include fewer performance metrics, which helps to slow down the database growth. You can learn more about the Advanced scalability mode from our deployment guide.
Modifying the Retention policy
You can modify the historical data retention period by adjusting the settings in Veeam ONE Settings utility > Retention Policy Period section.
Please be aware that we’re making changes which will restrict access to product updates for users without an active contract.