abh1sar commented on issue #12405: URL: https://github.com/apache/cloudstack/issues/12405#issuecomment-3759778249
From my understanding, Veeam also performs hot-attach at the hypervisor layer via vcenter as part of the restore workflow. In that model, the external backup provider handles both volume creation and attachment. Same model is followed by NAS plugin/ If we extend this expectation to other external backup providers, we can say that the provider handling the restore is also responsible for ensuring the restored volume is attached to the VM at the KVM level. I’m not very familiar with the Networker plugin to say if it can follow a similar model or needs CloudStack to perform the attach step after restore. If we had to handle it from Cloudstack side, I would think we would need to send AttachCommand to KVM after restore, although this needs proper scoping and validation with Networker. I’ll defer to someone more familiar with the Networker plugin to clarify the intended ownership of the attach operation in this workflow. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
