Release Notes: v1.2

2021/06/04 - Added a local registry with built-in K10 v4.0.3 images. You can use --set global.airgapped.repository=localhost:5000 during K10 installation to directly call the local docker image repository.

Virtual appliance updated to v1.2, corresponding file in cloud drive: UbuntuK10-v1.2.ova

Release Notes: v1.1

2021/05/03 - Tested Stateful MySQL deployment, changed the built-in Demo application in the appliance to Helm-installed MySQL. This allows quick demo and testing of backup and restore for stateful applications through this vApp.

Since Veeam Agent for Linux 4.0 (VAL) launched alongside VBR v10 earlier this year, this increasingly powerful backup agent has seen widespread adoption across various scenarios—cloud and on-premises, virtual and physical—there’s always a use case for VAL. However, we’ve found that newcomers to VAL often struggle with the agent installation process. Even with fully automated push installations, many users encounter various installation issues. This has created an awkward situation for Veeam backup software, which is renowned for its excellent user experience, making the “It just works!” slogan difficult to confidently claim.

Week 01

2020‑09‑07 – Add vCenter

2020‑09‑08 – Add VMware Windows Proxy

2020‑09‑09 – Add VMware Linux Proxy

2020‑09‑10 – Add File Proxy for NAS backups

2020‑09‑11 – Add a Windows direct-attached disk as a repository

Veeam prides itself on simplicity, yet the growing feature set can overwhelm newcomers. To help, I launched a WeChat mini-program that posts a short GIF every workday—each around ten seconds—to teach one Veeam trick at a time.

Scan the new QR code to follow:

WeChat compresses images heavily, so if you’d like the high-resolution versions, visit my blog.

When Veeam released V10 it added a brand-new capability tucked away behind PowerShell cmdlets and a rather intimidating name: Data Integration API. Many admins saw the term and assumed they’d need to write code, so they never looked deeper.

What It Actually Does

In reality, the feature is straightforward. It uses Windows’ iSCSI services to publish Veeam backup data as iSCSI disks. Think of it as a new data-lab use case: any image-level backup can be presented to a Windows or Linux host over iSCSI—no VMware or Hyper-V required. Supported sources include:

Hardening a Veeam deployment starts with a least-privilege vSphere account. As VBR adds features, the list of required rights keeps growing—check the full fine-grained permission matrix. Manually clicking through every checkbox is tedious, so here’s a slick PowerCLI script I recently found that builds the role automatically.

Prerequisite: install VMware PowerCLI. VMware’s official blog post explains the process in detail; below is the short version.

1. Install PowerShell Core 7. It’s required for PowerCLI and works on Windows, macOS, and Linux. On Windows, just run the MSI installer.