SadiJr commented on pull request #5457: URL: https://github.com/apache/cloudstack/pull/5457#issuecomment-1035002094
@DaanHoogland No, when the Backup Offering is unassigned, the current implementation deletes the backups. Why the integration was done this way, I don't know. It does not make sense to us, but this is how it was implemented (this integration was not developed by us). That is why we are trying to prevent users from deleting VMs that have backup offerings assigned. The initial intention of this PR was to prevent the destruction of a VM that had backups, as this would cause inconsistency in Veeam, where it would constantly be trying to make new backups of a VM that no longer exists. And, that is all we are trying to achieve, since, by the current code, we could not remove the backup job without removing the backups. Again, why this is as is, I have no idea. We are just trying to make this integration work, and currently, we are fixing these unexpected/odd/weird workflows. What do you think? Should we return to the initial idea? And just block the deletion of the VM, until we have a solution to de-assign the VM from a backup offering without removing the backups? -- 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]
