Veeam Backup Veem Update Version 9.2.1.33875

Views

Your rating
Rate update installation process

Risk factor
No ratings yet. Be the first to rate this update.

Smooth installs 0%

Minor issues 0%

Major issues 0%

Update Summary

Veeam Service Provider Console 9.2.1 (Version 9.2.1.33875) is a maintenance release with updated system requirements, upgrade guidance, and extensive known issues across integrations, billing, reporting, and REST API behavior.

Update Details

Security

Security note: use trusted security certificates only; updating a self-signed certificate requires manually re-accepting the connection on all management agents.
Disabling the PowerShell toggle while an active remote PowerShell session exists can freeze the console temporarily and repeatedly show a reconnect message; close sessions first.

Known Issues

Special characters are not supported in user login names.
Managed computer hostnames cannot exceed 15 characters.
Shift+Click multi-row selection is not supported.
Domain user login to the VSPC web site is not supported when a managed company has the same name as the user's domain.
Microsoft SQL Server with case-sensitive collation is not supported.
Veeam Backup & Replication servers using IPv6 are not supported by the backup portal.
Site administrators do not have access to hosted Veeam Backup for Microsoft 365 server data.
Operator roles cannot edit resources of managed Veeam Cloud Connect tenants.
Users with the Company Tenant role cannot access Reports in the web UI.
Veeam Intelligence is not available for the ConnectWise Manage plug-in and backup agent self-service recovery portal.
After upgrading to Veeam Service Provider Console 9.2, some company location region names with incorrect characters are not automatically corrected.
Agent deployment via third-party applications is removed from views after license revocation or uninstall until the management agent is reinstalled and the agent is registered again.
Changing the tenant name for a backup agent sending backups to a cloud repository can lose restore point information.
Backup jobs edited in the backup agent UI may discard excluded volumes configured in the VSPC web UI.
Backup jobs that fail before processing starts may remain shown as running until full data collection completes.
Custom variables in backup policies cannot be edited in the backup agent UI.
Backup job and settings reconfiguration can fail when the Windows UTF-8 beta language option is enabled.
Automatic installation of backup agents on x86 systems is not supported.
After installation, the VSPC server may need up to 10 minutes to download required Linux agent packages before portal-based installation works.
Backup agents on PowerPC hosts are not supported.
Agents managed by Veeam Backup & Replication synchronize data once a day; manage them with VSPC to avoid this limitation.
Upgrading Veeam Agent for Mac on macOS earlier than 11.0 fails only at the final step.
Support log download from remote backup servers may fail and require manual retrieval from the backup console.
Job scheduling column does not display data for Nutanix AHV jobs.
Remote installation of hotfixes and cumulative patches may fail on highly loaded Veeam Backup & Replication servers.
Download traffic for backup agents managed by Veeam Backup & Replication cannot be measured when jobs target object storage.
Application-aware processing options in the self-service portal require Veeam Backup & Replication 12.2 or later.
Guest file system indexing and malware detection in the self-service portal require Veeam Backup & Replication 12.1.2 or later.
NAS backup job Backup Size may include both restore points and short-term copies when archiving is enabled.
Automatic upgrade of remote Veeam Backup & Replication servers to 13.0.1 may require manual file-share upgrade in some mixed-version scenarios.
Antivirus SSL/TLS inspection may block gRPC and PowerShell communication between Veeam Backup & Replication and management agents.
Opening a PowerShell session from VSPC to a backup server does not work if the Management Agent service runs under a non-Local System account.
Veeam Backup & Replication 12.3 or earlier cannot be connected through the service-provider checkbox due to an untrusted digital signature.
Remote High Availability clusters require the service provider to be added on both nodes before cluster assembly.
Creating or editing backup copy jobs for Nutanix, Proxmox, Scale Computing HyperCore, or oVirt/KVM using the new proxied wizards in Veeam Backup & Replication 13.0.1 is not supported.
Redirect wizards may open slowly because of communication delays between the management agent and the server.
Opening a backup appliance UI on VSPC installed on Windows Server 2012 is not supported.
New public cloud backup appliance versions may run in compatibility mode until VSPC is updated.
Deleting backup restore points manually from a cloud repository causes incorrect quota reporting.
Deleting backups from a cloud repository is not supported for renamed tenants.
Restoring from backup or backup copy jobs using Veeam Cloud Connect as the target is not supported.
Cloud repositories are not available for selection in the new proxied job wizards due to visibility restrictions.
Cloud Connect log ZIP archives may not open with some tools such as WinZIP and may require 7-Zip.
After applying a cloud backup policy using Cloud Director tenants or sub-tenants, tenant credentials must be specified before using the job.
License keys cannot be remotely installed in Veeam ONE when services run under LocalSystem.
The Delete Alarm action in VSPC does not remove the alarm record from the managed Veeam ONE server.
Repeated Veeam ONE alarms may only show the most recent trigger in Active Alarms.
Personal sites cannot be selected in backup jobs created in the VSPC UI for Veeam Backup for Microsoft 365.
Jobs with newly created Microsoft 365 objects added in the server console cannot be edited immediately in VSPC.
RPO and SLA filters may show different object counts because personal sites and users are handled differently.
Scheduled backup time in the portal UI may differ from the actual start time under certain conditions.
Personal sites are not displayed in the SLA report and widget.
On-premises and hybrid Microsoft 365 organizations are not supported by the backup portal.
After reinstalling a management agent on a Veeam Backup for Microsoft 365 server, restore point counts may be incorrect until full synchronization is run.
A service provider cannot assign backup policies created by the managed client until the policy is copied first.
Migrating management agents between companies is not supported.
The management agent does not support connection through client proxy servers.
After management agent failover, custom credentials used for discovery and installation may need to be reapplied.
Management agents cannot be reassigned from a client company to the service provider company using Set Company.
Installing the Veeam Management Agent on macOS earlier than 11.0 fails at the final step.
After upgrading to VSPC 9.1, management agents on Oracle Linux 6 and RHEL 6 become inaccessible due to glibc requirements.
Active Directory discovery may take a long time for large domains.
Discovery of cloned machines with the same BIOS UUID may fail.
Discovery rules exclude computers running Veeam Cloud Connect.
Alarm timestamps may differ from actual event times.
The VM without backup alarm is not triggered for VMs in jobs with no successful sessions in the past period.
After reinstall, server migration, or database restore, alarm script execution is disabled until the configuration override is added back.
File to Tape jobs may temporarily report failed status when started twice.
Some newly collected jobs may show - as status until data collection completes.
Job and restore point information for backup agents managed by Veeam Backup & Replication is based on the agent time zone.
The unsupported license deployment alarm is not triggered for the VSPC server.
RPO and SLA widgets do not contain data for objects added to a job but never processed.
Session States does not display data about CDP policies.
Invalid protected data size may be displayed for backup agents on unsupported x86 OS versions.
After upgrading from v8.1 to v9, Session States widget counts may differ from exported CSV counts on the upgrade day.
Storage Vault Data on the Trends page does not break down usage by company for hosted Veeam Backup & Replication jobs.
Hardware plans with unlimited RAM are excluded from the quota usage dashboard.
Rejected computers are ignored in billing reports.
Billing reports stop tracking certain agent backups if the target changes from cloud to non-cloud repository.
Used Storage Quota reports may be incorrect when a GFS restore point is removed manually.
Data Transfer Out is not calculated for VM replicas from unmanaged backup servers.
Reseller subscription plans may not be preserved if a company is removed from the reseller.
Computers added to protection groups and never successfully run are treated as servers in invoices and billing data.
Widget totals may be incorrect when subscription plans use different currencies.
Download traffic is not measured for full health check operations triggered by backup agent jobs.
Download traffic is not measured for volume-level restores for a backup agent.
For correct billing, file shares should be registered individually instead of registering the file server itself.
Agents added individually to a hosted Veeam Backup & Replication server and targeting local folders or shares are always assigned to My Company in usage reports and invoices.
After upgrading to VSPC v9, free-of-charge resources are assigned to remote client locations in subscription plan settings.
The Round up for storage usage cost setting may revert after upgrade if it was the only changed setting.
When Veeam Cloud Connect is migrated to another server, reseller-managed companies and resources are removed from that reseller.
Reinstalling the management agent on the Veeam Cloud Connect server removes reseller references from managed companies.
Backup servers deleted during a reporting month are not tracked in usage reports and license usage statistics.
License usage from hosted locations is reported as remote locations usage in invoices.
Site administrators do not have access to the VSPC plugin library.
Localization changes in VSPC are not propagated to plug-ins such as ConnectWise Manage, File-Level Restore, and Veeam Intelligence.
Companies with Not Approved or Credit Hold states are not displayed in the ConnectWise Manage plug-in UI.
ConnectWise Manage tickets created from backup alarms contain missed RPO information as of threshold breach time.
Monitoring services in the backup portal subscription plan are not synchronized with ConnectWise Manage billing.
Upgrade is not supported when the configuration database and SQL Server instance have different collation settings.
After upgrade, custom settings in service and web UI config files are reset to defaults.
After upgrading to VSPC 9.2, the custom localization bundle is reset to English and must be updated with new keys and re-applied.
After upgrading to VSPC 9.2, the Protected Data page may show no drilldown data for file shares, file servers, or VM backup copy jobs until a full resync is run.
The REST API swagger page might not load in Mozilla Firefox under certain conditions.
REST API endpoints may fail when cloned managed servers are present until installation IDs are changed.

Hints

VSPC 9.2 supports automated in-place upgrade from version 9.1 and preserves product settings and configuration.
Before upgrading, close all active web UI sessions and back up the SQL Server configuration database.
VSPC cannot be installed on Windows Server Core.
Download the latest ISO from the Veeam Service Provider Console download page and run Setup.exe from the mounted ISO.
For large-scale distributed environments, follow the Deployment Guide sizing recommendations.
Remote network discovery requires firewall rules for SMB-In on TCP 445, WMI-In, Remote Scheduled Tasks Management, TCP 6180 for cloud gateways, and TCP 22 for Linux SSH.
After installing VSPC, Linux agent package downloads may take up to 10 minutes before portal-based installation is available.
For Oracle Linux 8 with UEK R7 and Oracle Linux 9 with UEK R8, see the referenced Veeam KB articles for agent installation guidance.
After upgrading to VSPC 9.2, run Data Collection > Full Resync on affected backup servers if Protected Data drilldown is empty.
To restore custom localization after upgrading to 9.2, update the bundle with the new localization keys and re-apply it.
For correct billing, register file shares individually in hosted Veeam Backup & Replication environments.