Veeam Backup Veem Update Version 13.0.2.27

Veeam Recovery Orchestrator 13.0.2.27 is a cumulative patch for VRO 13 released with embedded Veeam Backup & Replication 13.0.2.29 and Veeam ONE 13.0.2.6723. It adds VSA HA cluster support, a new web UI, offline malware scanning, and security updates.

• Offline malware scanning now supports antivirus (Veeam Threat Hunter by default), YARA, and malware-flag checks on restore points.
• Azure compute account secret/certificate is no longer collected automatically; it must be entered in the VRO UI to enable features such as script injection.
• Security component updates: System.Security.Cryptography.XML upgraded to 9.0.16 and 8.0.3, uuid upgraded to 14.0.0, react-router-dom upgraded to 6.30.3, and AutoMapper removed.

• Cloud recovery location now shows all repositories correctly.
• NetApp storage plans now detect the age of snapshots and replicated volumes correctly.
• VM size calculation no longer reserves excessive space for replica failback, CDP failback, or restore.
• Re-IP rules are now applied during DataLab tests.
• Malware scan scheduling across time zones has been fixed.

• Support for orchestrating Veeam Software Appliance (VSA), including HA clusters.
• 100% new web UI with improved UX and workflows.
• New monthly audit report covering readiness checks, tests, executions, malware scans, and change logs.
• Offline malware scanning for recovery plans.
• Support for HPE Alletra MP (GreenLake B10000) storage systems.
• Azure compute account management moved into the VRO UI for additional Azure recovery features.
• Maximum parallel VM recovery processing limit increased from 50 to 999.
• VRO 13 ISO now deploys or upgrades the full all-in-one stack only; individual product/component deployment requires product-specific ISOs.

• With active virus scan, the first restore point may be scanned twice and can consume extra restore retries; increasing default retries to 4 or 5 is recommended.
• The Plan Verification widget 'In-use' counter does not populate in the new web UI.
• Non-admin users can deselect DataLab Admin Lab Groups when configuring a DataLab test.
• When adding a VSA HA cluster, the VRO agent must be deployed using the cluster name or IP, not a node name.
• Boolean parameters may not be passed correctly to custom scripts on VSA servers.
• Network resource access via API may be restricted on VSA due to sandbox security.
• DataLab tests on VSA Linux backups or replicas may fail with 'Cannot find default Windows MountServer' unless a Windows mount server is added.
• Multiple re-IP rules may not always apply the strictest rule.
• SCVMM connections can break older Veeam Backup servers if their on-host components are not upgraded to the same version first.
• CSV disk online/offline status cannot be retrieved for Hyper-V recovery locations.
• In-guest scripting is not yet supported for Hyper-V VM recovery plans.
• Heartbeat checks for Hyper-V restores may be unreliable in some cluster configurations.
• It is not recommended to exceed 10 VMs processed in parallel for Hyper-V recovery locations.
• Hyper-V VM hardware version incompatibilities are not reported during readiness checks and can cause restore failures.
• SQL authentication credentials entered during installation cannot be changed later; Windows Authentication is recommended.
• A plan may halt during storage failover and leave orphaned VMs that must be removed manually.

• Release build: 13.0.2.27; embedded Veeam Backup & Replication build: 13.0.2.29; embedded Veeam ONE build: 13.0.2.6723.
• ISO name: VeeamDataPlatformPremium_v13.0_20260527.iso.
• Customers on older versions should upgrade to build 7.2.1.290 first, then upgrade to VRO 13.
• The VRO ISO can no longer deploy or upgrade individual products; use the specific ISO for each product or component.
• To enable Proactive Support for Orchestrator, edit C:Files.json and set "License": { "ProactiveSupport": true }.
• After upgrading VRO 7.2 to v13 and then upgrading connected Veeam Backup servers to v13, a VRO agent may remain in Warning state; repairing the agent is the workaround.
• If a private fix or patch was applied to the embedded Veeam Backup server, upgrade via the VRO .msi installer directly.
• Each recovery plan must now require only a single Veeam Backup server to execute.
• Each restore plan must now contain only one backup type: vSphere VM backup, Hyper-V VM backup, or Veeam Agent backup.
• The Veeam Threat Center dashboard has been removed from VRO and remains available in Veeam ONE.

• Download page
  https://www.veeam.com/downloads.html

Product Information

Vendor: Veeam Backup

Product: Veem

Version: 13.0.2.27

Release date: May 27, 2026