Views
35

Your rating
Rate update installation process

Log in to rate this update.
Login

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

Smooth installs 0%
Minor issues 0%
Major issues 0%

AI enhanced content

Update Summary

Veeam Recovery Orchestrator 13.1.0.483 is a cumulative patch for the 13.1 release. It resolves several recovery, Re-IP, malware scan, and cloud storage issues, and includes security library updates.

Update Details

Security

  • Security updates include upgrades to System.Security.Cryptography.XML (9.0.16 and 8.0.3), uuid 14.0.0, and react-router-dom 6.30.3, plus removal of AutoMapper.

Bug Fixes

  • Cloud recovery location now shows all repositories.
  • Fixed failure to determine snapshot age and replicated volume age in NetApp storage plans.
  • Corrected VM size calculation that reserved too much space for replica failback, CDP failback, or restore.
  • Re-IP rules are now applied during DataLab tests.
  • Fixed malware scan scheduling issues across time zones.

New Features

  • The maximum parallel VM recovery value in a recovery plan has been increased from 50 to 999.
  • The setup wizard now enforces that each plan uses only a single Veeam Backup server.
  • Restore plans must now contain only one backup type: vSphere VM, Hyper-V VM, or Veeam Agent backups.
  • The Veeam Threat Center dashboard has been removed from VRO and remains available in Veeam ONE.

Known Issues

  • With active virus scan enabled, the first restore point may be scanned twice during plan execution under specific conditions; increasing Restore VM retries to 4 or 5 is recommended.
  • In the new Web UI, the Plan Verification widget 'In-use' counter does not populate.
  • Non-administrator users can deselect DataLab Admin Lab Groups when configuring a DataLab test.
  • When adding a VSA HA cluster, the VRO agent must be deployed to the cluster name or IP address, not a node name.
  • Boolean parameters may not be passed correctly to custom scripts on VSA servers.
  • Network access through API may be restricted by VSA sandbox security features.
  • DataLab tests for Linux VM backups or replicas on VSA may fail with 'Cannot find default Windows MountServer' unless a Windows mount server is added.
  • When multiple Re-IP rules are configured, the strictest rule is not always applied.
  • SCVMM connections created in Orchestrator can break older Veeam Backup servers unless they are upgraded to the same version first.
  • Orchestrator may fail to collect all cluster networks for mapping rules if hosts do not respond or are excluded from monitoring.
  • CSV disk online/offline state is not detected in Hyper-V recovery locations.
  • Some plan steps are not compatible with Hyper-V restores because in-guest scripting is not yet supported.
  • Hyper-V heartbeat checks may be unreliable in aggressively optimized or large clusters.
  • It is not recommended to exceed 10 parallel VMs when recovering to a Hyper-V cluster.
  • Orchestrator cannot detect Hyper-V VM hardware version incompatibilities during readiness checks.
  • SQL authentication credentials set during installation cannot be changed later; use Windows Authentication if possible.
  • A plan may halt after Register VM steps and leave orphaned VMs in the recovery location.

Hints

  • The VRO ISO is intended to deploy or upgrade an all-in-one server with Veeam Backup, Veeam ONE, and Veeam Recovery Orchestrator; it can no longer deploy or upgrade individual products.
  • Customers on older versions should upgrade to 13.0.2.27 first, then upgrade to VRO 13.1.
  • The download becomes available from 2026-07-30.
  • If Proactive Support is needed for Orchestrator, it must be enabled in C:Files.json by setting ProactiveSupport to true.
  • After upgrading VRO and connected Veeam Backup servers to 13.1, the VRO agent may remain in Warning state and may need repair.
  • If a private fix or patch was applied to the embedded Veeam Backup server, upgrade may require launching the VRO .msi installer directly.
  • For SCVMM connections, upgrade existing Veeam Backup servers to the same version as the embedded server before creating the connection in Orchestrator.
  • The maximum supported parallel processing value depends on platform, storage, network, and environmental performance.
  • The embedded Veeam Backup & Replication build is 13.1.0.411 and the embedded Veeam ONE build is 13.1.0.7034.

Links

Product Information

Vendor: Veeam Backup

Product: Veem

Product type: Other

Platform: Windows

Version: 13.1.0.483

Vendor release date: Jul 29, 2026

Original release notes: View on vendor site

Published on updatealert.io: Jul 31, 2026

Description: Backup and recovery software for virtual, physical, and cloud workloads.