veeam (en) - B-blog.info
The longer you work with Veeam Backup & Replication, the lower and lower its interface work. Apparently, this is because Veeam stores in database information about all sessions of the interface. Once they become so numerous that queries to the database begin to slow down.
So we need:
- Set up Veeam to not to store all this unneeded information.
- Delete existing data from database.
- Truncate and shrink database.
After performing these steps, my Veeam client started to work much faster.
While restoring guest files of Windows systems in Veeam (LFR restore), you may get the following error:
No Disks have been mounted. Either disks of this type aren't supported or some error occured. See log file for details.
This error might be connected to the Symantec Backup Exec installed on the same server as Veeam Backup & Replication. Also interesting, that this error occures only for LFR restore, other types of restore are not affected.
There are two possible solutions for this issue.
Sometimes after correct installation of Veeam Powershell Snapin, attempt to load snap-in into Powershell console ends with error: Add-PSSnapin : The Windows PowerShell snap-in 'VeeamPSSnapIn' is not installed.
This problem occures because for some reason Snap-in is not got registered in Powershell. On Veeam official forums they offer many solutions like reinstalling Veeam or reboots-reinstalls of the Powershell module. In my case the following solution was found: