Veeam Backup & Replication is a modular solution that lets you build a scalable availability infrastructure for environments of different sizes and configurations. The Backup Server is the core component. Features & component requirements will affect your decision how you install the backup server e.g. one datacenter or multiple locations.
You may deploy the Veeam Backup & Replication server as either a physical or virtual server. It will run on any server with Windows Server 2012 R2 or higher installed (64-bit only). Install Veeam Backup & Replication and its components on dedicated machines. Backup infrastructure component roles can be co-installed. The following guidelines may help in deciding which deployment type is the best fit for your environment.
For most cases, virtual is the recommended deployment. As it provides high availability for the backup server component via features like vSphere High Availability, vSphere Fault Tolerance or Hyper-V Failover Clustering. It also provides great flexibility in sizing and scaling as the environment grows.
The VM can also be replicated to a secondary location such as a DR site. If the virtual machine itself should fail or in the event of a datacenter/infrastructure failure, the replicated VM can be powered on. Best practice in a two-site environment is to install the Backup server in the DR site, in the event of a disaster it is already available to start the recovery.
In small-medium environments (up to 500 VMs) it is common to see an all-in-one physical server running the Backup & Replication server, backup proxy and backup repository components. This is also referred to as an “Appliance Model” deployment.
An advantage of running the Veeam Backup & Replication server on a physical server is that it runs independently from the virtual platform. This might be an ideal situation when recovering the virtual platform from a disaster. Should the physical server itself fail, there are additional steps to take before reestablishing operations:
- Install and update the operating system on a new server
- Install Veeam Backup & Replication
- Restore the configuration backup
It is recommended to store the configuration backup, using a file copy job, in a location that is always available to this standby Backup & Replication server.
It is strongly recommended that no highly-transactional and business-critical software is deployed on the same machine as the Veeam backup server. This could be (but not limited to) software such as Active Directory, Exchange Server or other intensive production databases on the SQL server instance. If possible it would be preferable to have no other software at all running on the Veeam Backup Server.
It is recommended to follow antivirus exclusion guidelines as explained in Veeam KB 1999.
If it is not possible to connect to a remote SQL staging server for Veeam Explorers you can install Standard or Enterprise versions of SQL (depending on your licensing) locally for staging databases for item-level restores on the backup server. This installation can also be used to store the Veeam backup database if required as long as sufficient resources are assigned to the host machine, however do not run any instances in production from this installation that may affect the operation of the backups or restore processes. SQL express is included in the distribution but is limited to a 10GB database.
Other software such as Microsoft Outlook (64-bit) for mail export to PST files via Veeam Explorer for Exchange, or a PDF viewer for reading Veeam documentation are considered non-disruptive.
New Veeam releases and updates are installed on the Veeam Enterprise Manager and Veeam backup servers by the setup wizard or by using the unattended installation method (also referred to as “silent installation”). For detailed instructions check the latest release notes.
Note: Veeam Backup Enterprise Manager must be updated before updating Veeam backup servers.
After installing updates open the Veeam Backup & Replication management console. The Update screen will be displayed and will guide you through updating distributed components on other Veeam managed servers (like proxy and repository servers, vPower NFS servers, WAN accelerators and tape servers).
If you need to change the logging level or log file location refer to this Veeam Knowledge Base article.
It is recommended to not configure the logging level below 4, as it may complicate troubleshooting. Logging level 6 is very verbose, and should only be configured for short periods of time when requested by Veeam Support.