Learn Veeam - Skill Pre-Requisites & Environment Setup

#Introduction

Welcome to the Learn Veeam series! This series will take you through mastering Veeam Backup & Replication / Veeam Data Platform v13 — an enterprise data protection solution for VMware, Hyper-V, Proxmox VE, Nutanix AHV, physical servers, cloud, and SaaS. There are 23 episodes arranged in six phases, from conceptual foundations to production readiness.

Before you run your first New-VBRJob, there are basic skills and software & hardware requirements you must have in place. Why are these prerequisites important? Because Veeam works at the intersection of three worlds: the Windows operating system (where the VBR server runs), the hypervisor (the source of the VMs you protect), and storage (where backups are stored). Without understanding all three, you will struggle to diagnose why a job fails, a restore is slow, or a repository is full.

Episode 0 is your roadmap: we will confirm your skills are met, prepare the lab components, and verify the environment for the first time. Once this episode is complete, you can follow the entire series comfortably.

#Essential Skills You Must Have

#Windows Server Administration

Veeam Backup & Replication is a Windows application: the VBR server must run on Windows Server, and other components (proxy, repo) also run on Windows or Linux. You must be comfortable with Windows Server: managing services (services.msc), the firewall (Windows Defender Firewall), and PowerShell — because nearly all Veeam automation uses PowerShell:

Get-Service -Name "Veeam*" | Format-Table -AutoSize

#Hypervisor Concepts

Veeam protects VMs that live on a hypervisor, not raw files on disk. Understand the basic concepts of each platform:

• VMware vSphere/ESXi: VMs are stored as VMDKs; Veeam communicates through the vSphere API.
• Microsoft Hyper-V: VMs use VHDX; integration via WMI/SCVMM.
• Proxmox VE: KVM-based VMs with raw/qcow2 images — natively supported since Veeam v13.

Understanding what VM snapshots, guest OS, and virtual disks are will make the proxy and guest processing concepts (episodes 2 and 5) much easier to grasp.

#Storage Concepts

Backup is all about storage. You must understand the difference between block storage (SAN, iSCSI), file storage (NAS, SMB/NFS), and object storage (S3-compatible). Concepts such as deduplication, compression, and retention will also be used continuously starting in episode 6.

#Software and Hardware to Prepare

#Veeam Backup & Replication v13

VBR v13 is installed on Windows Server 2019/2022 (or Windows 10/11 for a small lab) with SQL Server — you can use the built-in SQL Express for a lab. Download the installer from the official Veeam site, then make sure the server has adequate CPU, RAM, and disk (at least 4 vCPU, 8 GB RAM, 50 GB free disk):

Get-ComputerInfo -Property "WindowsVersion","OsName" | Format-List

#Hypervisor Host

Prepare at least one hypervisor host to serve as the workload source:

• VMware ESXi 7/8 — via vCenter or a standalone ESXi host.
• Microsoft Hyper-V — on Windows Server.
• Proxmox VE 8/9 — natively supported by VBR v13.

The VMs you protect also need a Veeam Guest Agent or at least guest access for application-aware processing (episodes 5 and 10).

#Repository (Backup Storage)

Backups need a home. For a lab, the repository can be:

• Local Windows or Linux disk — the simplest option.
• NAS via SMB/NFS — a practical way to practice off-host repositories.
• S3 object storage — for example MinIO in the lab, or an AWS S3 bucket — to practice capacity tier (episode 18).

#License: Trial / Community / NFR

Veeam is a commercial product licensed per workload/instance. For learning, you have several options:

• Trial License (60 days) — for VBR and other products.
• NFR (Not for Resale) License — free for labs, training, and testing; obtained through the Veeam Tech Hub / community program.
• Veeam Universal License (VUL) — the modern per-instance/workload licensing model we will discuss in episodes 16 and 17.

Install the license from the VBR console: Help → Manage License, or via PowerShell:

$license = Read-Host "Path ke file .lic"
Set-VBRLicense -LicenseFilePath $license
Get-VBRLicense | Format-List

#Verifying the Environment

Before moving on to episode 1, make sure all prerequisites are met:

• Windows Server is running, PowerShell is active, and the Veeam* services are visible.
• The hypervisor (ESXi / Hyper-V / Proxmox) is reachable over the network.
• The repository (local disk / NAS / S3) has free space.
• The trial/NFR license is installed and validated.

#Prerequisite Summary

A recap of what you prepared in episode 0:

• Skills: Windows Server administration, hypervisor concepts, and storage.
• Software: VBR v13 on Windows Server with SQL; Veeam Agent for physical servers (episode 5).
• Hardware: a hypervisor host (ESXi 7/8, Hyper-V, or Proxmox VE 8/9) and a repository (disk/NAS/S3 object storage).
• License: an installed and validated trial or NFR license.

If anything is still missing, stop and complete it before continuing. The 22-episode journey ahead will go much more smoothly with this solid foundation.

#Closing

Key takeaways:

• VBR v13 is a Windows application — master Windows Server administration and PowerShell.
• Veeam protects workloads on hypervisors (ESXi/Hyper-V/Proxmox) — understand the basic concepts of each platform.
• Storage determines the backup architecture: block, file, or object storage.
• Prepare VBR v13, a hypervisor, a repository, and a trial/NFR license before you begin.
• Verify the environment with PowerShell and a checklist before moving on.

In the next episode, episode 1, we will cover the history, background, and why you need Veeam — from its founding in 2006, the Availability philosophy, the Broadcom acquisition in 2025, to the v13 release (November 2025) that marked the era of the Veeam Data Platform. Make sure your lab is ready, because the Learn Veeam journey has only just begun!