Hi Anthony, A one-way mirror suits fine in my case (the old cluster will be dismantled in mean time) so I guess a single rbd-mirror daemon should suffice. The pool consists of OpenStack Cinder volumes containing a UUID (i.e. volume-ca69183a-9601-11ea-8e82-63973ea94e82 and such). The change of conflicts is near to zero. My main concern is pulling images into a non-empty pool. It would be (very) bad if rbd-mirror tries to be smart and removes images that don't exist in the source pool. Regards and thanks again, Kees On 14-05-2020 17:41, Anthony D'Atri wrote:
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.