Generally, to process indexing data, you may use Veeam Backup Enterprise Manager that can process indexing data by itself, without Veeam Backup Search installed. In this case (if you have a relatively small number of backups) no content index will be generated — this will allow you to save on disk space for storing index content. However, if you are planning to use the file search feature for a large number of VM backups in your backup infrastructure (>100 indexed VMs) or for running sophisticated queries, you can configure a Veeam Backup Search server and add it to Veeam Backup Enterprise Manager.
Before you set up indexing options for your backup jobs, consider the following:
•Though use of the backup content index streamlines the search process, the content index itself can require significant space on disk.
•If you choose to implement search without content index (that is, no Veeam Backup Search installed), you will save on disk space, but this method can result in a slower search process.
•The capacity of a search server is limited and depends on the type of search server you plan to use. If you have a large number of backup servers and/or require storing index documents for a long period of time, you may want to deploy a number of search servers. In this case, the query processing and indexing load will be automatically spread across all deployed search servers.
•To coordinate proper indexing activities, Veeam Backup & Replication deploys an executable file inside a VM. This small executable file is used only during indexing procedure and is removed immediately after the processing is finished, producing minimal impact on VM performance and stability. However, if you need to avoid any extra load on some of your VMs, you can exclude them from indexing.
•By default, Veeam does not index Windows system and temp folders to reduce the index size.