When you set up the rbd-mirror daemons with each others’ configs, and initiate mirroring of a volume, the destination will create the volume in the destination cluster and pull over data. Hopefully you’re creating unique volume names so there won’t be conflicts, but that said if the destination has a collision, it won’t be overwritten. > > Hi list, > > Thanks again for pointing me towards rbd-mirror! > > I've read documentation, old mailing list posts, blog posts and some > additional guides. Seems like the tool to help me through my data migration. > > Given one-way synchronisation and image-based (so, not pool based) > configuration, it's still unclear to me how the mirroring will cope with > an existing target pool, already consisting of (a lot of) images. > > Has someone done this already? It feels quite scary with doom scenario's > like "cleaning up" the target pool and such in mind... > > To sum up: my goal is to mirror clusterA/somepool with some specific > images to clusterB/someotherpool where already other images reside. The > mirrored images should be kept in sync and the other images should be > left alone completely. > > Cheers, > Kees > > -- > https://nefos.nl/contact > > Nefos IT bv > Ambachtsweg 25 (industrienummer 4217) > 5627 BZ Eindhoven > Nederland > > KvK 66494931 > > /Aanwezig op maandag, dinsdag, woensdag en vrijdag/ > _______________________________________________ > ceph-users mailing list -- ceph-users@xxxxxxx > To unsubscribe send an email to ceph-users-leave@xxxxxxx _______________________________________________ ceph-users mailing list -- ceph-users@xxxxxxx To unsubscribe send an email to ceph-users-leave@xxxxxxx
 |