On Tue, Feb 26, 2019 at 7:49 PM Anthony D'Atri <adatri@xxxxxxxxxxxxxxxx> wrote: > > Hello again. > > I have a couple of questions about rbd-mirror that I'm hoping you can help me with. > > > 1) http://docs.ceph.com/docs/mimic/rbd/rbd-snapshot/ indicates that protecting is required for cloning. We somehow had the notion that this had been / will be done away with, but don't remember where we saw that. Thoughts? By default, if the cluster is configured to to require mimic or later clients, you no longer need to protect/unprotect snapshots prior to cloning [1]. The documentation still talks about protecting/unprotecting snapshots since the new clone v2 format isn't currently enabled by default in order to preserve backwards compatibility to older librbd/krbd clients. Once we no longer support upgrading from pre-Mimic releases, we can enable clone v2 by default and start deprecating snapshot protect/unprotect features. > 2) We're currently running 12.2.2 on our cluster nodes, with rbd-mirror running in a container built against 12.2.8. Should we expect images with clones / parents to successfully migrate with rbd-mirror? I've had a few rude awakenings here where I've flattened to remove the dependency, but in the general case would rather not have to sacrifice the underlying capacity. Yes, thinly provisioned cloned images have always been supported with RBD mirroring (Jewel release). You do, however, need to ensure that the parent image has mirroring enabled. > > > > Context: We aren't using rbd-mirror for DR, we're using it to move volumes between clusters for capacity management. > > Hope to see you at Cephalocon. > > > > > Anthony D'Atri > Storage Engineer > 425-343-5133 > adatri@xxxxxxxxxxxxxxxx > ________________________________ > We're Hiring! | @digitalocean | linkedin > [1] https://ceph.com/community/new-mimic-simplified-rbd-image-cloning/ -- Jason _______________________________________________ ceph-users mailing list ceph-users@xxxxxxxxxxxxxx http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
 |