Hello,
I’m running Veeam Backup & Replication 13.1.1.18 with the Community Edition (free, no paid license and no active maintenance contract). I’m trying to add a Veeam Infrastructure Appliance (VIA) as a Hardened Repository, installed from the latest ISO available, and I’m stuck.
Setup
- VBR 13.1.1.18, Community Edition
- VIA installed from the most recent ISO
- Versions shown on the VIA:
- Veeam Deployment Service: 13.1.1.18
- Veeam Updater: 13.1.202.0
- Veeam Host Management Console: 13.1.1.9
Problem 1: Add Linux Server wizard fails at the “Apply” step
After accepting the server certificate, the wizard gets through “Starting infrastructure item update process”, “Resolving server certificate” and “Configuring the identity service connection information”. It then fails with:
Software updates require an active maintenance contract.
Failed to save Linux server: Software updates require an active maintenance contract.
Problem 2: SSH elevation fails when using single-use credentials
When I retry using single-use credentials for the veeamadmin account, I get:
Unable to create elevated SSH connection: sudo failed and failover to su has failed (CSshShellStreamRebex).
Testing manually over SSH confirms veeamadmin is not in the sudoers file (sudo whoami → “veeamadmin is not in the sudoers file”). I assume this is by design on the hardened appliance, so I haven’t modified it.
Questions
- Is it a known limitation that the Community Edition cannot add or manage a VIA, because the wizard requires software updates (and therefore a maintenance contract)?
- If not, what is the correct way to add a VIA-based Hardened Repository to VBR with the Community Edition?
- Is it normal for the Host Management Console to be at 13.1.1.9 on a VIA deployed from the 13.1.1.18 ISO, or does this mismatch trigger the update that gets blocked?
- Can the VIA be updated from its own side (Veeam Updater / Host Management Console) so that the wizard has nothing left to update?
- If the VIA is not supported with the Community Edition, is a standard Linux (BYO) server configured as a Hardened Repository fully supported and free of this restriction?
I can provide logs and screenshots if needed. Thanks in advance for any help.
