Introduction to Veeam Backup for Windows Server 2019

Veeam Backup and Replication is an enterprise-grade data protection solution widely used in production environments running Windows Server 2019. It supports agentless backup of VMware vSphere and Microsoft Hyper-V virtual machines, as well as agent-based backup for physical servers and cloud workloads. Veeam’s proprietary Changed Block Tracking (CBT) technology enables fast, incremental backups after the first full backup, minimizing backup windows and storage requirements. The solution includes instant VM recovery, granular file-level recovery, and application-aware backup for SQL Server, Exchange, Active Directory, and other VSS-aware applications. This guide covers installing Veeam Backup and Replication, configuring backup jobs for Windows Server 2019, and performing recovery operations.

System Requirements for Veeam Backup Server

The Veeam Backup and Replication server requires a dedicated Windows Server machine. For small to medium deployments, Windows Server 2019 Standard or Datacenter works well as the backup server OS. The server needs a minimum of 4 CPU cores, 8 GB RAM (16 GB recommended for production), and sufficient disk space for the Veeam database and configuration store. SQL Server is used as the Veeam database backend — Veeam can install SQL Server Express automatically during setup, but for larger deployments use a dedicated SQL Server Standard or Enterprise instance.

The backup repository (where backup files are stored) should be on fast storage — NVMe or SAS-backed volumes are ideal for performance. Allocate at minimum 1.5x the total source data size for the repository, accounting for changed block incremental growth. Network connectivity between the backup server and protected VMs or agents should be at least 1 Gbps; 10 Gbps is recommended for large environments.

Installing Veeam Backup and Replication

Download the Veeam Backup and Replication ISO from the Veeam website (a free Community Edition license supports up to 10 workloads). Mount the ISO and run Setup.exe as Administrator. On the splash screen, click Install under Veeam Backup and Replication. Accept the license agreement and, if you have a license file (.lic), browse to it. Otherwise, proceed without a license for the free Community Edition.

The installer checks for missing prerequisites and offers to install them automatically: Microsoft .NET Framework 4.7.2, Microsoft SQL Server 2016 Express (if no SQL instance is detected), and Microsoft Visual C++ Redistributables. Allow the installer to install all prerequisites. On the Service Account page, configure the account under which Veeam services run — a dedicated service account with local administrator privileges on the backup server is best practice.

Accept the default installation paths or customize them, then click Install. The installation takes approximately 15–20 minutes. After completion, launch Veeam Backup and Replication Console from the Start menu.

Adding a Windows Server 2019 Physical Server as a Protected Workload

For physical Windows Server 2019 machines (not running as VMs), use the Veeam Agent for Microsoft Windows. From the Veeam Backup and Replication Console, navigate to Inventory > Physical Infrastructure. Right-click and select Add Protection Group. Name the group (for example, Physical-Windows-2019) and choose Protection Group Type as Individual computers.

Add the target servers by hostname or IP address. Specify a Windows account with local administrator rights on the target servers. Veeam will automatically push-install the Veeam Agent for Microsoft Windows to each server in the group. This requires WMI and file-sharing access (TCP 445) from the Veeam server to the targets, plus TCP 10006 for Veeam Agent communication.

Creating a Veeam Agent Backup Job for Windows Server 2019

After adding the protection group, create a backup job. In the Veeam console, navigate to Home > Backup Jobs > Agent. Right-click and select Add > Windows Computer. In the job wizard, name the job (for example, WS2019-Physical-Nightly) and select the protection group or individual computers to include.

On the Backup Mode page, select Entire Computer for a full server backup (recommended for bare metal recovery capability), or select Volume Level Backup and choose specific volumes, or File Level Backup for folder-based protection. For Windows Server 2019 machines hosting critical roles, Entire Computer mode is the best choice.

On the Storage page, select or create a backup repository. Configure the retention policy — a common setting is 14 restore points, meaning Veeam keeps the last 14 daily backup increments. Enable the Reverse Incremental or Forever Forward Incremental chain methods depending on your repository type; forever forward incremental is generally recommended for performance-optimized block storage.

Configuring Application-Aware Processing

Veeam’s application-aware processing uses the Volume Shadow Copy Service to quiesce applications before taking a backup snapshot, ensuring transactionally consistent backups. In the backup job wizard, on the Guest Processing page, enable Application-aware processing. Add credentials for the target server (local administrator account).

For SQL Server running on the Windows Server 2019 target, Veeam can truncate SQL Server transaction logs after each backup to prevent log disk exhaustion. In the Applications section, click Applications, select the SQL Server item, and choose Truncate Logs. For Active Directory domain controllers, Veeam automatically handles the AD-aware quiescing process to ensure consistent AD backups.

Scheduling and Running Backup Jobs

On the Schedule page of the job wizard, configure the backup schedule. Common configurations include daily at midnight (off-peak), or multiple times per day for high-change workloads. Enable the Retry failed backup job option with 3 retries at 10-minute intervals to handle transient network failures. Enable After this job > run the following job to chain backup jobs sequentially and avoid resource contention.

After finishing the wizard, the job appears in the Home view. Right-click the job and select Start to run it immediately. Monitor progress in the Veeam console’s Last 24 Hours view. A green checkmark indicates success; a yellow warning indicates completion with warnings (review the job log); red indicates failure.

Veeam also provides a PowerShell module for job management. To start a backup job via PowerShell:

Add-PSSnapin VeeamPSSnapIn
$job = Get-VBRJob -Name "WS2019-Physical-Nightly"
Start-VBRJob -Job $job

Instant Recovery and File-Level Restore

Veeam’s Instant Recovery feature can start a VM directly from a backup file in seconds, allowing you to bring a failed server back online before performing a full restore. For physical agent backups, Veeam supports Instant Physical Machine Recovery, which allows restoring to the original machine or different hardware.

For granular file-level recovery from an agent backup, right-click the backup in the Home view, select Restore Guest Files > Microsoft Windows. Veeam mounts the restore point as a virtual drive and opens the Veeam file browser. Navigate to the files you need, right-click, and select Restore to Original Location or Copy To for restoring to an alternate path. This process does not require rebooting the production server.

Configuring Backup Copy Jobs for Offsite Protection

To implement the 3-2-1 backup rule, configure a Backup Copy Job to replicate backup data to a secondary repository or offsite location. In the Veeam console, select Backup Copy under the Home tab. In the wizard, select the source backup job and the target repository (this can be a Veeam Cloud Connect service provider’s repository, a remote office backup server, or an Azure Blob storage repository configured as a Scale-Out Backup Repository tier).

Configure the copy interval (daily or more frequent), retention policy for the copy, and enable WAN acceleration if copying over a slow link. WAN acceleration uses deduplication and compression at the source before transmission, dramatically reducing bandwidth requirements for backup copy jobs over WAN connections.

Monitoring and Alerting with Veeam ONE

Veeam ONE is a companion monitoring and analytics product that integrates with Veeam Backup and Replication to provide dashboards, SLA compliance reporting, and proactive alerts. Install Veeam ONE on a separate server and point it at the Veeam Backup and Replication server’s SQL database. Veeam ONE can alert on backup job failures, missed backup windows, low repository space, and license expiration via email, SNMP, or webhook.

Even without Veeam ONE, the Veeam console itself supports email notifications. In Veeam Backup and Replication, navigate to Options > Notifications to configure SMTP settings and default notification preferences for job failures and warnings. Per-job notification overrides are also available in each job’s settings under the Advanced tab.