![]() ![]() In Microsoft SQL Server Management Studio right-click the database and select New Query.Īlter database VeeamBackup set recovery simpleīackup database VeeamBackup to disk = 'NUL' with init.This procedure is not mandatory, but will save 1-2 GB on system disk. Long process of data processing will start.In the window that appears enter how many days you want to keep.Right click - and select Execute Stored Procedure. ![]() Expand the database down to Stored Procedures and find DropStoppedOldJobSessions procedure: Programmability > Stored Procedures > DropStoppedOldJobSessions.Connect to Veeam SQL database with Microsoft SQL Server Management Studio.But you can use Services snap-in from Windows Administrative tools. From Powershell: Get-Service veeam* | Start-Service. As for me, you will not need more than 8-12 weeks. In the Session history retention section, specify the number of sessions to keep in the Veeam Backup & Replication database.In the Sessions section, specify the number of sessions to display in the Sessions list of the History view.Set up Veeam to not to store all this unneeded information.Īfter performing these steps, my Veeam client started to work much faster.Once they become so numerous that queries to the database begin to slow down. Apparently, this is because Veeam stores in database information about all sessions of the interface. The longer you work with Veeam Backup & Replication, the lower and lower its interface work. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |