You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cloudstack.apache.org by "cdfgallo (via GitHub)" <gi...@apache.org> on 2024/07/18 08:13:59 UTC
[D] Behaviour of recurring snapshot of multiple large volumes of the same VM [cloudstack]
GitHub user cdfgallo created a discussion: Behaviour of recurring snapshot of multiple large volumes of the same VM
<!--
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 -->
* Bug Report
##### COMPONENT NAME
<!--
Categorize the issue, e.g. API, VR, VPN, UI, etc.
-->
~~~
UI
~~~
##### CLOUDSTACK VERSION
<!--
New line separated list of affected versions, commit ID for issues on main branch.
-->
~~~
4.19.0.1
~~~
##### CONFIGURATION
<!--
Information about the configuration if relevant, e.g. basic network, advanced networking, etc. N/A otherwise
-->
##### OS / ENVIRONMENT
<!--
Information about the environment if relevant, N/A otherwise
-->
Master: CentOS7
Cluster: vSphere 7.0U3
##### SUMMARY
<!-- Explain the problem/feature briefly -->
Recurring weekly snapshots taken from data disks on one VMware instance are not shown in the UI.
We set the following snapshot policy for a data volume of an instance and we observe some strange behaviours
We also have a daily recurring snapshot on the root disk (about 30GB) of the VM which starts at 10:30 PM (GMT +1).
While the snapshot on the root disks take an incredible amount of time to end (many times more than 2 hours), the snapshot of the data disk failed with error: "There is other active snapshot tasks on the instance to which the volume is attached, please try again later".
After that we can see that the snapshot on the data disk is taken and is correctly present on the secondary storage, but we can't see it in the UI.
##### 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 -->
~~~
~~~
<!-- You can also paste gist.github.com links for larger files -->
##### EXPECTED RESULTS
<!-- What did you expect to happen when running the steps above? -->
~~~
If a snapshot fails on the prerequisites it should not be performed and if it's performed it should be present in the UI.
~~~
##### ACTUAL RESULTS
<!-- What actually happened? -->
<!-- Paste verbatim command output between quotes below -->
~~~
From the UI we see that the snapshot fails, but it's performed and not showed in the UI
~~~
GitHub link: https://github.com/apache/cloudstack/discussions/9414
----
This is an automatically sent email for users@cloudstack.apache.org.
To unsubscribe, please send an email to: users-unsubscribe@cloudstack.apache.org
Re: [D] Behaviour of recurring snapshot of multiple large volumes of the same VM [cloudstack]
Posted by "rajujith (via GitHub)" <gi...@apache.org>.
GitHub user rajujith added a comment to the discussion: Behaviour of recurring snapshot of multiple large volumes of the same VM
@cdfgallo Yes, you understand the process correctly. CloudStack implements full backup for Vmware volume snapshot backup to the secondary storage.
GitHub link: https://github.com/apache/cloudstack/discussions/9414#discussioncomment-10081631
----
This is an automatically sent email for users@cloudstack.apache.org.
To unsubscribe, please send an email to: users-unsubscribe@cloudstack.apache.org
Re: [D] Behaviour of recurring snapshot of multiple large volumes of the same VM [cloudstack]
Posted by "rajujith (via GitHub)" <gi...@apache.org>.
GitHub user rajujith added a comment to the discussion: Behaviour of recurring snapshot of multiple large volumes of the same VM
@cdfgallo could you update the time for the data volume snapshot schedule to 2 to 3 hours later than the ROOT volume?
GitHub link: https://github.com/apache/cloudstack/discussions/9414#discussioncomment-10081629
----
This is an automatically sent email for users@cloudstack.apache.org.
To unsubscribe, please send an email to: users-unsubscribe@cloudstack.apache.org
Re: [D] Behaviour of recurring snapshot of multiple large volumes of the same VM [cloudstack]
Posted by "cdfgallo (via GitHub)" <gi...@apache.org>.
GitHub user cdfgallo added a comment to the discussion: Behaviour of recurring snapshot of multiple large volumes of the same VM
> @cdfgallo Yes, you understand the process correctly. CloudStack implements full backup for Vmware volume snapshot backup to the secondary storage.
@rajujith Thank you! Wouldn't be easier to export it directly to the datastore mounted on the vCenter server instead of using the CS master node? The process would be at least, way faster than the actual.
GitHub link: https://github.com/apache/cloudstack/discussions/9414#discussioncomment-10081632
----
This is an automatically sent email for users@cloudstack.apache.org.
To unsubscribe, please send an email to: users-unsubscribe@cloudstack.apache.org
Re: [D] Behaviour of recurring snapshot of multiple large volumes of the same VM [cloudstack]
Posted by "cdfgallo (via GitHub)" <gi...@apache.org>.
GitHub user cdfgallo added a comment to the discussion: Behaviour of recurring snapshot of multiple large volumes of the same VM
Hi @rajujith yes, separating the two workloads we are albe to process this.
I see anyway that the template export is quite slow in cloudstack and analyzing a little bit I see that, after creating a full clone of the VM, a OVA it's exported to the NFS mountpoint on the master node. It's the correct behaviour or I have some wrong configuration?
GitHub link: https://github.com/apache/cloudstack/discussions/9414#discussioncomment-10081630
----
This is an automatically sent email for users@cloudstack.apache.org.
To unsubscribe, please send an email to: users-unsubscribe@cloudstack.apache.org