GitHub user la-wu added a comment to the discussion: CloudStack-KVM integration for Veeam B&R
@nickaccuweb it took a bit longer then expected to deploy 4.23.0 GA But I finally installed it and manged to test the Veeam Integration. Short version: the behavior is the same as with the RC3 I tested before. I made sure to use a compute offering with HA disabled to be sure that the VM is not HA enabled. Nevertheless I had to use Stop Instance after the initial deployment. I checked Management Server Logs and found no HA restart event no entry with: "HA on VM instance". I checked the User Data of the worker and there you can see the last command for the preparation is: shutdown -h now So the VM enters halt state but Cloudstack/KVM is not converting this to stopped. When manually stopping the VM, Veeam initiates a fresh start and continues to prepare the worker. So all this is not Cloudstack HA related. One additional thing I noticed. After the initial restart Veeam tries to connect to the VM via its IP. But veeam seems to request the actual IP from cloudstack and does not try to connect with the configured IP during worker creation process. So if cloudstack aquires a different IP then defined as static IP it won`t work. You would need to assign the correct static IP also in cloudstack. All of this is not a big deal if you know it. As it only happens during initial deployment. Once successfully deployed the worker has no issues. Just to anwser the last question: all needed ports are open between Veeam server, Cloudstack and KVM hosts. GitHub link: https://github.com/apache/cloudstack/discussions/12869#discussioncomment-18501809 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
