Before You Begin

Before you install Veeam Backup & Replication, check the following prerequisites:

  • A machine on which you plan to install Veeam Backup & Replication must meet the system requirements. For more information, see System Requirements.
  • A user account that you plan to use for installation must have sufficient permissions. For more information, see Permissions.
  • Backup infrastructure components communicate with each other over specific ports. These ports must be open. For more information, see Ports.
  • You must remove Veeam Backup & Replication components of versions that are not supported by the upgrade procedure from the target machine. You may also need to remove earlier versions of other Veeam products and components.
  • Before deploying Veeam Backup & Replication, define where the Veeam Backup & Replication server will be located. Depending on what kind of protection are you planning to use, the Veeam Backup & Replication server should be located on the source site or the Disaster Recovery site.
  • When replication or CDP is used: If you plan to use replication or Continuous Data Protection (CDP), the Veeam Backup & Replication server should be deployed in the disaster recovery site. In this case, if the production host crashes, Veeam Backup & Replication will automatically fail over to the replica without any manual operations. The source backup infrastructure still can be managed with the same Veeam Backup & Replication server with the help of backup proxies deployed in the source site.
  • When only backup features are used: If you plan to use Veeam Backup & Replication for backup jobs only, the backup server should be placed in the production site.

Configuration Database

Before deploying Veeam Backup & Replication, decide which database engine and version you need to use:

  • If you do not prepare a database engine in advance, Veeam Backup & Replication will automatically install PostgreSQL 15.1 locally on the backup server.
  • Decide if you need the database engine installed on the same server as Veeam Backup & Replication or on a remote server. Veeam Backup & Replication requires a database engine deployed either locally on the backup server or remotely.

It is recommended to run the database engine instance locally to eliminate latency issues. However, in some scenarios a remote instance can be the better choice:

  • High Availability. SQL Clustering and Always On Availability Group on external SQL Servers can be used for high availability of the configuration database. To learn about the configuration details, see this Veeam KB article.
  • Licensing. Some enterprises have dedicated virtual clusters for SQL Servers due to licensing constraints. In such cases, you can place the Veeam configuration database on an existing instance to lower the total cost of ownership.
  • If you prefer to use an Express Edition of Microsoft SQL Server as your database engine, note that its usage is limited by 10 GB of configuration database. The Express Edition is enough for evaluation purposes and not very large environments (<500 VMs). If your infrastructure is large (more than 500 VMs), you may consider to install a Microsoft SQL Server in advance.
  • If Microsoft SQL Server is installed by the previous product version, Veeam Backup & Replication will connect to the existing configuration database, upgrade it (if necessary) and use it for work.

Related Topics

Infrastructure Planning