cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Glen Baars <>
Subject Snapshots only on Primary Storage feature
Date Thu, 17 May 2018 14:46:12 GMT
Hello Devs,

I have been thinking about a feature request and want to see what people think about the use

We use KVM + Ceph RBD as storage.

Currently, when a client takes a snapshot, Cloudstack takes a Ceph snapshot and then uses
qemu-img to export to secondary storage. This creates a full backup of the server. Clients
want to use this as a daily snapshot and it isn't feasible due to the space requirements.

We would like create the snapshot only on primary storage. It is replicated offsite and fault
tolerant. I can see that the download snapshot and create template features may be an issue.

I have seen the below features in the recent releases and wondered if this was the direction
that the development was going.
Separation of volume snapshot creation on primary storage and backing operation on secondary
Bypass secondary storage template copy/transfer for KVM.
Kind regards,
Glen Baars
BackOnline Manager

T  1300 733 328 / +61 8 6102 3276
NZ +64 9280 3561<>

 []  Facebook<>
 [] LinkedIn<>

Watch a short video about what we do!<>
This e-mail may contain confidential and/or privileged information.If you are not the intended
recipient (or have received this e-mail in error) please notify the sender immediately and
destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material
in this e-mail is strictly forbidden.

This e-mail is intended solely for the benefit of the addressee(s) and any other named recipient.
It is confidential and may contain legally privileged or confidential information. If you
are not the recipient, any use, distribution, disclosure or copying of this e-mail is prohibited.
The confidentiality and legal privilege attached to this communication is not waived or lost
by reason of the mistaken transmission or delivery to you. If you have received this e-mail
in error, please notify us immediately.

  • Unnamed multipart/related (inline, None, 0 bytes)
View raw message