gg4126 opened a new issue, #6604:
URL: https://github.com/apache/cloudstack/issues/6604
<!--
Verify first that your issue/request is not already reported on GitHub.
Also test if the latest release and main branch are affected too.
Always add information AFTER of these HTML comments, but no need to delete
the comments.
-->
##### ISSUE TYPE
<!-- Pick one below and delete the rest -->
* Improvement Request
##### COMPONENT NAME
<!--
Categorize the issue, e.g. API, VR, VPN, UI, etc.
-->
~~~
API, UI
~~~
##### CLOUDSTACK VERSION
<!--
New line separated list of affected versions, commit ID for issues on main
branch.
-->
~~~
CloudStack 4.17.0.1
~~~
##### CONFIGURATION
<!--
Information about the configuration if relevant, e.g. basic network,
advanced networking, etc. N/A otherwise
-->
advanced networking
##### OS / ENVIRONMENT
<!--
Information about the environment if relevant, N/A otherwise
-->
RHEL 7.9
##### SUMMARY
<!-- Explain the problem/feature briefly -->
The VM Snapshots and VM “Backup & Recovery” are two different things;
Currently CloudStack supports the VM backup & recovery by means of third party
Veeam Plugin which requires paid subscription. We noticed that when we destroy
(without Expunging) VMs, it is also deleting the associated VM Snapshots, in
fact we wanted to use these VM snapshots as our recovery points. So, Is it
possible to retain the VM snapshots even when the VMs are getting destroyed so
that we can pick and choose the desired VM snapshot to recover the VM.
##### STEPS TO REPRODUCE
<!--
For bugs, show exactly how to reproduce the problem, using a minimal
test-case. Use Screenshots if accurate.
For new features, show how the feature would be used.
-->
<!-- Paste example playbooks or commands between quotes below -->
~~~
step1: Navigate to the desired instances under compute tab, and click "Take
VM Snapshot" w/ Snapshot memory & Quiesce VM Enabled
step2: Navigate to Instances, pick the VM and destroy it (without choosing
Expunge).
step3: After the VM is destroyed, you will notice that the associated VM
Snapshots under Storage tab are also deleted.
~~~
<!-- You can also paste gist.github.com links for larger files -->
##### EXPECTED RESULTS
<!-- What did you expect to happen when running the steps above? -->
~~~
Destroying VMs should NOT delete the associated VM Snapshots coz these
snapshots can be used to recreate the VM using the desired VM snapshot from of
these backed-up VM snapshots.
~~~
##### ACTUAL RESULTS
<!-- What actually happened? -->
<!-- Paste verbatim command output between quotes below -->
~~~
Destroying VMs also deleting the associated VM Snapshots - the whole chain
parent and children VM snapshots
~~~
--
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]
