Veeam Service Provider Console 9.3 Release Notes

This document provides last-minute information about Veeam Service Provider Console version 9.3, including system requirements and installation, as well as relevant information on technical support, documentation, online resources, and so on.

The release version of Veeam Service Provider Console 9.3 is available starting from July 30th, 2026.

System Requirements

For the most up-to-date system requirements and compatibility information, see Veeam Service Provider Console Deployment Guide, section System Requirements.

Sizing and Deployment Recommendations

Check the Deployment Guide document for achieving maximum performance of Veeam Service Provider Console in large-scale distributed environments.

The recommended deployment configuration can be equally used for POC deployments and deployments in production.

Installing Veeam Service Provider Console

To install Veeam Service Provider Console server and Web UI:

1. Download the latest version of Veeam Service Provider Console ISO from https://www.veeam.com/service-provider-availability-console.html.
2. Mount the product ISO and use autorun or run the Setup.exe file.

Follow the installation procedure as described in Veeam Service Provider Console Deployment Guide.

Uninstalling Veeam Service Provider Console

1. From the Start menu, select Control Panel > Add or Remove Programs.
2. In the programs list, select Veeam Service Provider Console and its components and click the Remove button.

For details on the uninstallation procedure, see Veeam Service Provider Console Deployment Guide, section Uninstalling Veeam Service Provider Console.

Upgrading Veeam Service Provider Console

Veeam Service Provider Console version 9.3 supports automated in-place upgrade from versions 9.1 and 9.2 that preserves all product settings and configuration.

Upgrade checklist:

1. Make sure all active Veeam Service Provider Console web UI sessions are closed before starting the update procedure.
2. Perform a backup of the SQL Server configuration database used by Veeam Service Provider Console, so that you can quickly go back to the previous version in case of issues with the update.

For a step-by-step update procedure, see Veeam Service Provider Console Deployment Guide, section Updating Veeam Service Provider Console.

Known Issues in Veeam Service Provider Console

General

• Special characters are not supported in user login names.
• Hostname of managed computers cannot exceed 15 characters.
• Logging in to the VSPC web site with domain user credentials is not supported when there is a managed company with the same name as the user’s domain.
• Microsoft SQL Server with case-sensitive collation is not supported.
• Veeam Backup & Replication servers using IP v6 are not supported by the backup portal.

Security

• When updating a self-signed security certificate for the Veeam Service Provider Console server, you must manually re-accept the connection on all management agents. To resolve this, use trusted security certificates only.
• If the PowerShell toggle is disabled while a user has an active PowerShell session to a remote backup server, the console temporarily freezes and then displays the “Failed to connect to the remote backup server. Trying to reconnect…” message repeatedly. To avoid this, close all active PowerShell sessions before disabling the PowerShell toggle.

Single Sign-On (SSO)

• Users that have the “;” character in the location name cannot be authenticated to the backup portal.

Role-based Access Control (RBAC)

• Site administrators do not have access to hosted Veeam Backup for Microsoft 365 servers data which includes protected data and managed jobs.
• Users with the Company Tenant role do not have access to the Reports section in the Veeam Service Provider Console web UI and therefore cannot generate reports.

Veeam Intelligence (AI)

• Veeam Intelligence is not available for the ConnectWise Manage plug-in and backup agent self-service recovery portal.

Veeam Agent for Microsoft Windows Integration

• Agent deployed using 3rd party applications is removed from all views after revoking the agent’s license key or uninstalling the agent. To start managing this agent again, re-install the management agent on the remote computer and register it in the backup portal.
• After enabling or disabling the usage of wake-up timers in the backup agent settings, the target computer must be restarted to apply these changes.
• Changing the tenant name under which a backup agent sends backups to a cloud repository or destination target leads to losing information about available restore points stored in the repository.
• If you configure a backup job with excluded volumes using the VSPC web UI and then edit this job using backup agent UI (running in the Full Admin Access mode), the excluded volumes selection will be discarded. To resolve that, re-apply the backup policy in the VSPC web UI or run backup agents in the Read-only UI mode.
• Backup jobs that fail without any attempt to process the data (at the beginning of the processing cycle) are displayed in the running state in the VSPC UI until full data collection is performed for a backup agent.
• Custom variables configured in the backup policies cannot be edited using the backup agent UI. To work around this, use backup policy edit options in the backup portal UI instead.
• Backup job and settings reconfiguration fail when “Beta: Use Unicode UTF-8 for worldwide language support” option is enabled on the remote computer.

Veeam Agent for Linux Integration

• After installation, the VSPC server needs up to 10 minutes to download all required agent packages. During this time, backup agent installation using the backup portal is not possible.
• Cloud backup policies will be automatically re-applied to managed agents when the failover to available gateways option is enabled in the company properties.
• Backup agents running on hosts with PowerPC processors are not supported.

Veeam Agent for Mac Integration

• Agents that are managed by Veeam Backup & Replication servers synchronize data once a day. To resolve this, manage these backup agents with Veeam Service Provider Console.
• Upgrading the Veeam Agent for Mac on computers running macOS versions earlier than 11.0 fails without indicating that the operating system version is unsupported.

Veeam Backup & Replication Integration

• Support logs download operation from remote backup servers might fail with the following error message: “Failed to download log files. Please log in to the backup console and retrieve the required logs manually”. To resolve this, upgrade the PowerShell framework to the most recent version. If this does not help, contact the Veeam Customer Technical Support team.
• Job scheduling column does not display any data for Nutanix AHV jobs.
• Remote installation of hotfixes and cumulative patches might fail on highly loaded Veeam Backup & Replication servers. To resolve that, grant more resources to the backup server or install the required files manually.
• Download traffic for backup agents managed by the Veeam Backup & Replication server cannot be measured when agent jobs are targeted to an object storage repository.
• Minor warning messages for installation, upgrade, and patching tasks for a Veeam Backup & Replication server do not affect the overall status of the main task and are only shown in the main task details.
• If newly created tags or workloads from a hosted backup server are not visible when creating a backup job, go to Configuration > Plugin library > Veeam Backup & Replication plugin > Backup Servers tab and initiate the data collection task for the backup server with missing info.
• For NAS backup jobs with archiving enabled, the Backup Size value may include both restore points and their short-term copies.
• For Linux-based Veeam Backup & Replication servers, time-related columns are not displayed for CDP policies under the Virtual Machines tab in the Backup Jobs section.
• Antivirus software with SSL/TLS traffic inspection (for example, ESET with SSL/TLS protection enabled) may block gRPC and PowerShell communication between the Veeam Backup & Replication server and management agents, causing multiple operations to become unavailable. For more information, see KB1999.
• Opening a PowerShell session from the Veeam Service Provider Console to a backup server does not work if the Management Agent service is running under an account other than Local System.
• Veeam Backup & Replication version 12.3 or earlier cannot be connected to Veeam Service Provider Console using the “allow this installation to be managed by the service provider” checkbox in the Add Service Provider wizard due to an untrusted digital signature. To work around this, install the company management agent manually from the VSPC web UI.
• When connecting a remote High Availability cluster to Veeam Service Provider Console, the service provider must be added on both cluster nodes before assembling the cluster in Veeam Backup & Replication. If the service provider is added on one node only, the cluster will display the “Missing secondary node” status in Veeam Service Provider Console. To resolve this, disassemble the cluster, add the service provider on both nodes, and reassemble the cluster.
• In some cases, communication delays between the management agent and the server may cause redirect wizards to open slowly. To work around this issue, refresh the page and try again after several minutes.
• Under certain conditions, the “Backup High Availability Cluster State” alarm trigger can be delayed by a couple of hours.
• Instant Restore and Restore Entire VM actions for VMs can only be performed to the original platform.
• Object storage backup copy jobs cannot be edited in the Veeam Service Provider Console.

Veeam Backup for Public Cloud Integration

• New versions of public cloud backup appliances work in compatibility mode without exposing data about new protected workloads and other new features. To resolve this, wait for the Veeam Service Provider Console update.

Veeam Cloud Connect Integration

• Deleting backup restore points manually from a cloud repository leads to incorrect quota reporting. There is no workaround to this until the next update of Veeam Backup & Replication.
• Deleting backups from a cloud repository is not supported for renamed tenants. Backups that belonged to a tenant before the renaming are not deleted. To resolve this, delete these backup files manually.
• Restoring from backup or backup copy jobs that use Veeam Cloud Connect as the target is not supported due to current Veeam Backup & Replication limitations.
• Due to repository visibility restrictions in Veeam Cloud Connect, cloud repositories are not available for selection when creating or editing backup jobs using the new proxied job wizards.
• When downloading logs from a Cloud Connect server, Veeam Service Provider Console may create a ZIP archive that cannot be opened with certain archive tools such as WinZIP. The archive can be extracted using 7-ZIP.

VMware Cloud Director Integration

• After applying a cloud backup policy using Cloud Director tenants or sub-tenants, the user must specify tenant or sub-tenant credentials to start using a job.

Veeam ONE Integration

• License key cannot be remotely installed using the VSPC UI when Veeam ONE services are running under the LocalSystem account. To resolve this, use any other account to run Veeam ONE services.
• The “Delete Alarm” action on the Active Alarms tab in the Veeam Service Provider Console does not remove the alarm record in the managed Veeam ONE server. This action only removes (hides) the alarm event in the Console UI.
• If a Veeam ONE alarm is triggered multiple times within a short time period, only the most recent trigger is displayed in the Active Alarms tab of the Veeam Service Provider Console UI, while the information about the previous resolve events is lost.

Veeam Backup for Microsoft 365 Integration

• Idividual personal sites cannot be selected in backup jobs created using the Veeam Service Provider Console UI. To resolve this, configure backup jobs using the Veeam Backup for Microsoft 365 server console.
• Cannot edit a backup job with objects newly created in Microsoft 365 and explicitly added to a job using the Veeam Backup for Microsoft 365 server console. To resolve this, wait for 24 hours and retry the operation.
• Number of objects can be different when selecting RPO and SLA filters on the RPO & SLA tab. This happens because the SLA filter treats personal sites and users as a single unit, while the RPO filter splits those objects into separate entities.
• Under a certain condition, the scheduled time for a backup job in the backup portal UI can be different from an actual start of a backup job.
• Personal sites of users are not displayed in the SLA report and the SLA widget.
• After reinstalling a management agent on the Veeam Backup for Microsoft 365 server, an incorrect number of restore points may be displayed in the Console UI. Run the full synchronization action for the managed backup server to resolve it.

Backup Agent Policies

• A service provider cannot assign backup policies created by the managed client. To resolve that, the service provider must first copy this backup policy.

Management Agent

• The management agent does not support connection through client proxy servers.
• If a master management agent uses custom user credentials to discover remote computers and to install Veeam Agent for Microsoft Windows, then after management agent failover operation (switching to the new management agent), custom credentials must be reapplied to the new master management agent.
• Management agents cannot be reassigned using the Set Company action from the client’s company to the service provider company (“My Company”). As a workaround, reinstall the management agent and pre-select the required company in the agent installation package options.
• When installing the Veeam Management Agent on macOS versions earlier than 11.0, the installation process proceeds through all steps of the wizard and fails only at the final step due to the unsupported OS version.

Discovery Rules

• Microsoft Active Directory discovery process may take a considerable time for domains with a large number of objects.
• The Discovery of cloned machines with the same Bios UUID may fail. It is recommended to change Bios UUIDs for cloned machines before running discovery.
• Discovery rules exclude computers running Veeam Cloud Connect from the discovery results.

Alarms and Notifications

• Due to data collection engine scheduling, time stamps for triggered alarms might differ from the time of actual events.
• “VM without backup” alarm is not triggered for VMs contained in jobs that do not have any successful job sessions for the past period.

Monitoring and Reporting

• When you start a File to Tape job twice, the job state will be reported as failed until the first job run is complete. Some jobs collected from the managed Veeam Backup & Replication servers for the first time might show “-” as their job status. To resolve that, rerun the jobs and wait until the new data collection is complete.
• Information about jobs and restore points for backup agents managed by Veeam Backup & Replication is based on the agent time zone.
• “Unsupported license deployment. Shared license key usage” alarm is not triggered for the VSPC server. To stay compliant with licensing rules, use unique keys for every server.
• RPO & SLA widgets do not contain any data for objects that were added to a job but were never processed (have no restore points created).
• Session States tab does not display any data about CDP policies.
• Invalid protected Data size is displayed for backup agents running on unsupported OS versions (x86 ISA).
• The Storage Vault Data widget on the Trends page does not break down storage vault usage by company for jobs running on hosted Veeam Backup & Replication servers. All usage is displayed under the service provider company (My Company) instead of the assigned managed company.

Billing

• Hardware plans with unlimited RAM resources are excluded from the quota usage dashboard.
• Rejected computers are ignored in the billing reports.
• Billing reports stop tracking backups created by Veeam Agent for Microsoft Windows pointed to the cloud repository if the target for the backup job is changed from a cloud repository to a non-cloud repository.
• Used Storage Quota reports incorrect data when GFS restore point is removed manually.
• Data Transfer Out metric is not calculated for VM replicas from backup servers that are not managed in Veeam Service Provider Console.
• A subscription plan created by a reseller will not be preserved in the managed company configuration if this company is removed from the reseller. To resolve this, please assign a new subscription plan to the company manually.
• Computers that were added to protection groups in Veeam Backup & Replication and never had successful job runs are treated as servers in invoices and billing data.
• Total sums on the widgets will display incorrect values if subscription plans with different currencies are used within the same VSPC server.
• Download traffic (data transfer out counter) is not measured for full health check operations triggered by Veeam backup agent jobs.
• Download traffic (data transfer out counter) is not measured when running volume-level restores for a Veeam backup agent.
• For the correct billing on used licenses by each tenant, it is recommended to register file shares individually instead of the file server itself in the hosted Veeam Backup & Replication server.
• In a hosted Veeam Backup & Replication infrastructure, agents that are added to the backup server individually (not via protection group) and that have backup jobs targeted to a local folder or a share will always be assigned to the service provider company (My Company) in usage reports and invoices.

Reseller Role

• When Veeam Cloud Connect is migrated to another server, all companies and resources hosted on that server and managed by a reseller will be removed from that reseller. To resolve this, please re-add these companies to the reseller manually.
• When management agent is reinstalled on the Veeam Cloud Connect server, all companies managed by a reseller will lose their references to the managing account. To resolve that, reassign all managed companies to resellers using the VSPC UI.

Licensing and Usage Reporting

• Backup servers deleted during a reporting month are not tracked in the usage reports and license usage statistics. To resolve that, calculate usage for these servers manually.
• License usage from hosted locations is reported as remote locations usage in the invoice.
• Installing a license key from VCSP Pulse on a dedicated backup server assigned to a company is not possible when using the Reseller role. As a workaround, install the required license key manually.

Plugin Library

• Localization changes applied in Veeam Service Provider Console are not propagated to plug-ins such as ConnectWise Manage, File-Level Restore, and Veeam Intelligence. Plug-in interfaces remain untranslated.

ConnectWise Manage Plugin

• Companies with the “Not Approved” or “Credit Hold” states are not displayed in the plugin UI.
• ConnectWise Manage tickets created based on the “Computer without backup” and “VM without backup” alarms contain the missed RPO information as of the time when the alarm threshold was breached. To see the actual data of the missed RPO event, please use the VSPC web UI.
• The default data synchronization interval between Veeam Service Provider Console and plugin for ConnectWise Manage is 5 minutes. This affects all configuration settings, including SMTP server configuration. To change this interval, please contact the Veeam Customer Technical Support team.
• Monitoring services that are part of the backup portal subscription plan are not synchronized with ConnectWise Manage billing system.

Upgrade

• Upgrade is not supported when the Veeam Service Provider Console configuration database and the SQL Server Instance hosting its database have different collation settings.
• After the upgrade, custom settings from service and web UI config files (Veeam.MBP.Service.exe.config; Veeam.Portal.ConnectionHub.exe.config; Web.config) are reset to default values.
• After upgrading to Veeam Service Provider Console 9.3, a custom localization bundle is reset to the default English language. The custom bundle is preserved in the list and merged with the new manifest file. To restore the custom localization, download the bundle, update it with the new localization keys introduced in version 9.3, and re-apply it.

REST API

• Under certain conditions, the REST API swagger page might not load when using the Mozilla Firefox browser.
• Triggering REST API endpoints may fail when cloned managed servers (for example, Veeam Backup & Replication) are present in the infrastructure. To resolve this, change installation IDs of cloned servers using the Discovery tab in the Veeam Server Provider Console.

Licensing

To start using Veeam Service Provider Console, you must obtain a Veeam Universal License (VUL).

• For VCSP users, generate the required license keys using the VCSP Pulse portal.
• For Enterprise users, obtain a Veeam Universal License through your Veeam sales representative.

To deploy Veeam Service Provider Console, use any unused VUL key generated using the VCSP Pulse portal.

Technical Documentation References

If you have any questions about Veeam Service Provider Console, you may use the following resources:

• Product web page: https://www.veeam.com/service-provider-availability-console.html
• User guides: https://www.veeam.com/documentation-guides-datasheets.html
• Veeam Cloud & Service Provider (VCSP) private community forum (registration is required): https://forums.veeam.com/veeam-cloud-service-providers-forum-f34

Technical Support

We offer email and phone technical support for customers on maintenance and during the official evaluation period. For a better experience, please provide the following when contacting our technical support:

• Version information for the product and all infrastructure components.
• Error message and/or accurate description of the problem you are having.
• Log files.

To submit your support ticket or obtain additional information, please visit www.veeam.com/support.html.

Contacting Veeam Software

At Veeam Software we pay close attention to comments from our customers. It is important to us not only to quickly help you with your technical support issues — we make it our mission to listen to your input, and to build our products with your suggestions in mind.

Should you have a Customer Support issue or question, please feel free to contact us. We have qualified technical and customer support staff available 24 hours a day, 7 days a week who will help you with any inquiry that you may have.

Customer Support

For the most up to date information about our support practices, business hours and contact details, please visit www.veeam.com/support.html. You can also use this page to submit a support ticket and download the support policy guide.

Company Contacts

For the most up to date information about company contacts and office locations, please visit www.veeam.com/contacts.