Veeam v13: Web UI vs Console

Veeam v13 ships with two main management interfaces and a third that is specific to the Linux Software Appliance. Most people deploying v13 for the first time do not fully understand what each one can and cannot do until they are in production trying to do something and discovering they are in the wrong tool. This article lays out the boundaries so you know before you need to.

The Web UI is a browser-based interface that runs on the VBR server. You reach it at https://<vbr-server-hostname> on port 443. It works from any browser on any machine. It supports SAML SSO. This is the interface Veeam is actively building out and expanding with each release, and it handles day-to-day operational work well. The overview dashboard it ships with is better than anything the old Windows console ever offered for at-a-glance environment status - the Resiliency Overview score in particular is worth paying attention to.

The Console is the Windows thick client. It runs only on Windows and connects to the VBR server over the network. It is where everything lives: every configuration option, every job type, every advanced setting, every edge case. In v13 it got a dark mode redesign but its functional scope is the same as before. You can download the console installer directly from the Web UI login page - there is a link at the bottom of that page.

Host Management is a third interface that exists only on the Linux Software Appliance. It runs at https://<appliance-hostname>:10443. It manages the appliance OS itself - network settings, hostname changes, NTP, OS updates, user accounts, SSH access, and Security Officer-gated actions like enabling HA or data collection for Veeam ONE. It is not a backup management interface. If you are on Windows VBR, you do not have this.

The Web UI is available at https://<vbr-server-hostname> from any browser immediately after VBR is installed. No additional setup is required. VBR users with appropriate permissions can log in using their VBR credentials or via SAML SSO if configured.

The Console must be installed separately on a Windows machine. The installer is available on the VBR installation media, or you can download it directly from the Web UI login screen. Install it on a dedicated Windows management machine or jump server rather than on individual workstations. Once installed, open it and enter the VBR server hostname or IP to connect.

Host Management at port 10443 is accessible immediately after the Linux Software Appliance is deployed. Log in with the Host Administrator or Security Officer account. These are separate user accounts from the VBR application accounts used for the Web UI and Console.

The Overview dashboard shows an aggregate view of your environment including a Resiliency Overview score, job status summary, recent activity, and protected workload counts. For a quick check on environment health, this is more useful than the old console's Home view.

Job monitoring and control works well from the Web UI. You can start, stop, retry, and disable VMware vSphere and Hyper-V backup jobs. You can create and edit these jobs. You can view session logs and job statistics.

Restores for VMware and Hyper-V VMs are available: Instant VM Recovery, file-level recovery (restore to original location), and disk restore. This covers the most common restore scenarios your ops team will handle day to day.

License management is fully available in the Web UI: install, view, revoke, remove, and update licenses all work from the browser.

General settings - email notifications, patch management for Linux infrastructure components, and infrastructure scanning - are accessible. The Install Missing Updates option from the Web UI installs updates on Linux-based infrastructure components (Veeam Infrastructure Appliances), but not on the Linux Software Appliance itself. To update the backup server, use the Veeam Updater through Host Management.

These are not temporary limitations or roadmap items - they are the documented current state from the official Web UI Limitations page.

Configuration backup. Cannot be set up, scheduled, or restored from the Web UI. This is the most operationally significant gap in the list. Configuration backup is how you recover a VBR server from a failure. If you build your entire environment through the browser and never touch the console, your configuration backup is not set up. I have watched this catch people out. Open the console on day one and configure it before anything else.

Backup jobs for other platforms. The Web UI supports creating and editing backup jobs for VMware vSphere and Hyper-V. Agent-based backup jobs, NAS backup jobs, tape jobs, and object storage backup jobs are not available in the Web UI. For those workloads you need the console.

Replication jobs. You can view, start, and stop replication jobs from the Web UI, but you cannot create or edit them. Creating or editing a replication job requires the console.

Scale-Out Backup Repositories. SOBRs are read-only in the Web UI. You cannot create, edit, or add extents to them from the browser.

Repository settings. You cannot modify repository settings in the Web UI. Viewing repository status is available, but any configuration changes require the console.

Advanced job settings. Any advanced settings accessible via the Advanced button in a job wizard in the console are not accessible in the Web UI. This includes scheduling overrides, health check settings, storage integration settings, and similar per-job configuration.

Secondary destinations. The Web UI job wizard does not support configuring a secondary destination for a backup job. Use the console to set that up, or create a separate backup copy job.

Transaction log backup configuration. Not available in the Web UI. Configure this from the console.

Cross-platform restores. Restoring from one hypervisor platform to another (for example Hyper-V backup to vSphere) is not available in the Web UI.

File-level restore to another location. The Web UI supports file-level recovery only to the original location. Restoring guest OS files to a different location or a different machine requires the console, or you can use Veeam Backup Enterprise Manager for this.

HA cluster management. Creating, editing, or managing a High Availability cluster cannot be done from the Web UI. The Windows console is required for all HA cluster operations.

* Web UI updates Linux-based Infrastructure Appliances only. To update the Linux Software Appliance (backup server itself), use Veeam Updater through Host Management at port 10443.

The split that works in production: build and configure everything through the console, then run day-to-day operations from the Web UI.

Use the console for initial deployment and any structural changes - repositories, proxies, SOBRs, credentials, replication jobs, agent jobs, tape, advanced job settings. The first thing you do on day one, before you do anything else, is configure the configuration backup from the console. Get the full environment built and working through the console first.

After that, use the Web UI for everything routine. Checking job status, responding to failures, running VMware and Hyper-V restores, reviewing the dashboard, starting or stopping jobs, managing licenses. Your ops team can work entirely from a browser without needing the console or a Windows machine. That is a clean operational separation that scales well when more people need read and run access to backup without needing full console access.

Keep the console installed on a Windows jump server with controlled RDP access, not on individual workstations. Treat it the same way you treat vCenter or a management console for any other critical infrastructure - a controlled path for people who have a specific reason to make configuration changes, not something open to everyone.