Re: Asking this in dev as there are many fixes for volumes/snapshots on 4.15.2 and 4.16.0

2021-09-22 Thread Harikrishna Patnala
is issue and update it. Thanks for letting us know. Regards, Harikrishna From: Kristaps Cudars Sent: Friday, September 17, 2021 2:40 PM To: dev@cloudstack.apache.org Subject: Asking this in dev as there are many fixes for volumes/snapshots on 4.15.2 and 4.16.0 4

Re: Asking this in dev as there are many fixes for volumes/snapshots on 4.15.2 and 4.16.0

2021-09-22 Thread nux
I can't replicate this on 4.16/KVM. Scheduled volume(!) snapshot functionality only backs up the respective volume, as expected. Regards On 2021-09-21 16:59, Riepl, Gregor (SWISS TXT) wrote: When you create reoccurring volume snapshot task, instead of transferring only that volume all volumes

Re: Asking this in dev as there are many fixes for volumes/snapshots on 4.15.2 and 4.16.0

2021-09-21 Thread Riepl, Gregor (SWISS TXT)
When you create reoccurring volume snapshot task, instead of transferring only that volume all volumes that are associated with VM are transferred to secondary storage. That doesn't sound right. Are you sure you're really creating a recurring volume snapshot and not a VM snapshot? I believe the

Asking this in dev as there are many fixes for volumes/snapshots on 4.15.2 and 4.16.0

2021-09-17 Thread Kristaps Cudars
4.15.1/Vmware When you create reoccurring volume snapshot task, instead of transferring only that volume all volumes that are associated with VM are transferred to secondary storage. Way how we find this is that we have some VM with 8~TB disks that should not be backed up and our secondary sto