We have a SharePoint 2013 farm with two frontends, two application servers, a office web app server and the databases is located on a seperate SQL 2012 AO cluster.
The 2013 farm is supporting an ESDH application, witch uses a site for every record so the total amount of site collections exceeds 70.000
Unfortunally the high number of site collections affects the Veeam Backup Server performance heavely, and after about 14 days of backup the vbm file exceeds 1GB in size witch is causing a job Error: "Exception of type 'System.OutOfMemoryException' was thrown".
The Veeam Backup Enviroment is as follows:
We use Veeam Backup v8 (has planed to upgrade to v9 when update 1 is released)
Backup server is virtual and is Windows 2012 R2 - it has 64BG RAM and 6 vCPU
Backup server hosts the VBR and the VEM database (SQL 2014) and the SQL server has 32 GB RAM allocated.
Enterprise Manager is installed on seperate Windows 2012 R2 server
We have created a support (#01216471) but it wasn't possible to solve the issue. The workaround for now is to disable VSS and indexing on the servers, reset the job (Remove from backups) and rename the backup folder/vbm file on the repository (to keep history). Due to the workaround, item level restore must be handled by sql database backup.
All restore is delegated to System Administrators by using the Enterprise Manager portal. Due to the disabled indexing, this isn't posible for SharePoint server files.
Also we would like to use the SharePoint Explore to perform item level recovery, but that's isn't possible when VSS is disabled.
Will you plan a solution for this issue?