Veeam Backup Veem Update Version 13.1.2.25; embedded Veeam Backup & Replication 13.1.2.57; embedd

Veeam Recovery Orchestrator 13.1.2.25 is available for download with cumulative fixes, security-related dependency updates, and expanded recovery-plan parallel processing. The release includes embedded Veeam Backup & Replication 13.1.2.57 and Veeam ONE 13.1.0.7940.

• Updated security-related dependencies in Release 13.1.2: axios 1.20, dompurify 3.4.13, BouncyCastle.Cryptography 2.7.0, and PowerShell SDK versions 7.4.20 and 7.6.6.
• Updated System.Security.Cryptography.XML to versions 9.0.16 and 8.0.3 in previous 13.1 updates.
• Removed AutoMapper and System.Security.Cryptography.X509Certificates; updated uuid to 14.0.0 and react-router-dom to 6.30.3.

• Fixed incomplete repository display for cloud recovery locations.
• Fixed failures to determine the age of snapshots and replicated volumes in NetApp storage plans.
• Corrected excessive space reservations for replica failback, CDP failback, and restore operations.
• Fixed Re-IP rules not being applied during DataLab tests.
• Fixed malware scan scheduling issues across time zones.

• Raised the recovery-plan parallel VM recovery limit from 50 to 999.
• Added upgrade validation requiring each plan to use a single Veeam Backup & Replication server and each Restore plan to contain only one backup type.
• Added configuration checks to the upgrade wizard.

• The Veeam Updater plugin is included but inactive at release. Its UI may show a missing-certificate warning and a message that no Veeam Recovery Orchestrator installation was found; the latter is expected until the repository contains VRO downloads.
• With active virus scanning and one restore point selected, the first restore point may be scanned twice after a virus is detected. Increase Restore VM retries from 3 to 4 or 5 as a mitigation.
• The Web UI may not populate the Plan Verification widget's In-use counter. Non-administrator users may also deselect DataLab Admin Lab Groups when configuring a DataLab test.
• For VSA HA clusters, deploy the VRO agent using the cluster name or IP address, not an individual node name. Boolean custom-script parameters are not passed correctly, network access may be restricted by the VSA sandbox, and Linux DataLab tests may require a Windows mount server.
• When multiple Re-IP rules exist, a less-strict rule may be applied instead of the strictest rule.
• Hyper-V recovery may have incomplete cluster-network discovery, cannot determine CSV disk state, lacks some in-guest scripting plan-step compatibility, and may produce unreliable heartbeat checks under certain cluster conditions.
• Do not exceed the default limit of 10 VMs processed in parallel for Hyper-V cluster recovery because PowerShell command queuing may cause timeouts.
• Hyper-V VM hardware incompatibilities may not be reported during readiness checks and can cause restore failure.
• A storage-failover plan may halt after incomplete Register VM steps and leave orphaned VMs in the recovery location; remove those VMs manually.
• SQL authentication credentials configured during installation cannot be changed. Changing the SQL account password can prevent Orchestrator from connecting to its database.
• Recovery plans containing in-guest scripts may fail when the source machine remains online because the backup server attempts to deliver the script to the source machine.

• The release is distributed as the Veeam Data Platform Premium ISO, VeeamDataPlatformPremium_v13.1_20261026.iso, for all-in-one deployments or upgrades.
• Customers on older versions must first upgrade to build 13.0.2.27 and then upgrade to VRO 13.1.
• The 13.1 ISO cannot deploy or upgrade individual products. Use the product-specific ISO for individual product or component upgrades.
• Connected Veeam Backup & Replication servers should be upgraded to 13.1 before using new 13.1 Orchestrator functionality. Existing Veeam backup servers must match the embedded backup server version before creating SCVMM connections.
• Supported host operating systems are 64-bit Windows Server 2016, 2019, 2022, and 2025. Windows Server Core and Domain Controller installations are not supported.
• The setup and service accounts require local Administrator permissions; service accounts also require Log on as a service. Orchestrator UI accounts require Allow log on locally.
• Veeam Threat Center has been removed from the VRO UI but remains available in Veeam ONE.
• The Proactive Support setup option does not enable the feature for Orchestrator; it must be enabled through the documented configuration file setting.
• The maximum practical recovery parallelism remains dependent on platform, storage, network, and other environmental performance factors.

• Veeam product downloads
  https://www.veeam.com/downloads.html
• Veeam Recovery Orchestrator 13.1 What's New
  https://www.veeam.com/veeam_orchestrator_13_1_whats_new_wn.pdf

Product Information

Vendor: Veeam Backup

Product: Veem

Product type: Other

Platform: Windows

Version: 13.1.2.25; embedded Veeam Backup & Replication 13.1.2.57; embedd

Vendor information published: Oct 27, 2026

Original release notes: View on vendor site

Published on updatealert.io: Oct 30, 2026

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