Link

Veeam Backup Enterprise Manager

Deployment use cases

It is recommended to deploy Enterprise Manager if:

  • you are using encryption for backup or backup copy jobs. With enabled password loss protection. Enterprise Managers administrators will have the possibility to unlock backup files using a challenge/response mechanism effectively acting as a Public Key Infrastructure (PKI).

  • your organization has a Remote Office/Branch Office (ROBO) deployment. Sites administrators will have access to granular restore options via the web UI rather than providing access to a Backup & Replication console.

  • delegation capabilities must be used to elevate the 1st line support to perform in-place restores without administrative access.
  • you need to centrally manage licenses for multiple Veeam Backup & Replication servers.
  • you are planning extensive file restores from large file servers. You can enhance the user experience through 1-Click file restores with help of the file indexing engine.
  • you plan to use Veeam RESTful API to automate your data protection workloads.

If the environment includes a single instance of Backup & Replication you may not need to deploy Enterprise Manager, especially if you want to avoid additional SQL Server database activity and server resource consumption (which can be especially important if using SQL Server Express Edition).

Enterprise Manager server Placement

If possible, it is advised to install the Enterprise Manager server on the recovery site so it is directly available in case of disaster recovery.

Sizing Enterprise Manager server compute

The Veeam Enterprise Manager server will very rarely necessitate more than 8 cores and 16 GB of RAM.

Sizing Enterprise Manager Catalog

The Veeam Catalog Service is responsible for maintaining index data. When running on the backup server this catalog service will maintain index data for all jobs that run on that specific server as long as the backup data remains on disk. When running on the Enterprise Manager server the service will move index data from all managed backup servers into the Enterprise Manager local catalog deleting the files from the originating backup server catalog. So it should be sized appropriately to hold all data from all remote Veeam servers.

  • When using a Standard license, Enterprise Manager will only keep index data for restore points still in repositories.
  • For Enterprise and Enterprise Plus licenses, you can configure Enterprise Manager to keep indexes even longer, with the default being 3 months. This can significantly increase the amount of space required for the catalog.

Estimated used space of the final index file after compression is approximately 2 MB per 1,000,000 files for a single VM restore point on the Enterprise Manager server. The indexes are also stored in the backup files and temporary folders on the backup server.

Below is an example that summarizes the information above. The example is given per indexed VM containing 10,000,000 files.

10 million files * 2 MB per million files * 60 restore points per month * 3 months index retention = 3.5 GB

References