VAO fails to deploy a VAO agent to a standalone Veeam Backup & Replication server

Challenge When VAO tries to deploy a VAO agent to a standalone Veeam Backup & Replication server, you get a generic error "Failed to communicate to agent", and all VAO attempts to communicate with the VAO agent fail. You can also see the following error in the VAO agent logs located in the log...

Veeam Availability Orchestrator v2 Patch 1 (build 1463)

Challenge This patch fixes the following issue found in VAO 2.0. The presence of backup job objects created by Veeam plug-in backup jobs cause VAO Restore Plans to fail locating valid restore points required for the restore process. The following example shows the issue found in the Readiness Che...

Migrating VAO 1.0 Deployment to Version 2.0

Challenge Upgrade of Veeam Availability Orchestrator to version 2.0 is not supported. However, you have an option to migrate your VAO 1.0 configuration to version 2.0 with minimal downtime. This KB article briefly describes architectural changes introduced in 2.0 version and provides step-by-step...

Re-IP rules do not work in Veeam Availability Orchestrator lab test

Challenge In rare cases, when you perform a failover, Re-IP rules are applying correctly, however, when you perform a lab test these rules would not be applied. Solution To resolve that: 1. Make sure that no plans are currently running 2. Open Veeam Availability Orchestrator UI Configuration VAO...

Veeam Availability Orchestrator stops collecting vCenter asset information

Challenge There is an issue with the embedded Veeam ONE component of Veeam Availability Orchestrator 1.0 release. The issue results in Veeam ONE not recognizing new VMware vCenter assets approximately 90 days after installation. Cause There is a synchronization issue between Veeam ONE Monitor and...