Bug 1262095

Summary:	[RFE] Aysnc RBD Mirroring
Product:	[Red Hat Storage] Red Hat Ceph Storage	Reporter:	Sean Cohen <scohen>
Component:	RBD	Assignee:	Jason Dillaman <jdillama>
Status:	CLOSED ERRATA	QA Contact:	Hemanth Kumar <hyelloji>
Severity:	medium	Docs Contact:	Bara Ancincova <bancinco>
Priority:	unspecified
Version:	1.3.1	CC:	ceph-eng-bugs, flucifre, hnallurv, icolle, jdillama, jdurgin, kdreyer, vumrao
Target Milestone:	rc	Keywords:	FutureFeature
Target Release:	2.0
Hardware:	Unspecified
OS:	Unspecified
URL:	https://wiki.ceph.com/Planning/Blueprints/Infernalis/RBD_Async_Mirroring
Whiteboard:
Fixed In Version:	ceph v10.2.0	Doc Type:	Enhancement
Doc Text:	.Block Device mirroring is now supported The RADOS Block Device (RBD) mirroring feature has been added to the Red Hat Ceph Storage 2. RBD mirroring is a process of replicating Ceph Block Device images between two peer Ceph Storage Clusters. The mirroring is asynchronous, crash-consistent, and serves primarily for disaster recovery. To learn more about RBD mirroring, see the https://access.redhat.com/documentation/en/red-hat-ceph-storage/2/single/block-device-guide/#block_device_mirroring[Block Device Mirroring] chapter in the https://access.redhat.com/documentation/en/red-hat-ceph-storage/2/single/block-device-guide/[Block Device] guide for Red Hat Ceph Storage 2.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-08-23 19:26:36 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1201698, 1283413, 1322504

Description Sean Cohen 2015-09-10 19:31:47 UTC

Overview
=======
Currently, to support disaster recovery for RBD, we advise that customers export/import each RBD as an image for copying between two distinct clusters. This is cumbersome with large numbers, requires a dedicated host to manage the files and can be slow for the initial copy. 
Async RBD Mirroring will allow each RBD to be streamed in realtime to a secondary cluster and be point in time consistent. This feature is roughly equivalent to NetApp's SnapMirror in purpose.

User Stories:
==========
* As an administrator, I select a pool's RBD contents to be asynchronously mirrored to a pool in a second RADOS cluster.
* As an administrator, I select an individual RBD to be asynchronously mirrored to a pool in a second RADOS cluster.
* As an administrator, I can see which pools or RBDs are successfully being mirrored to a secondary cluster.
* As an administrator, I am warned when a pool or RBD is not being successfully mirrored to a secondary cluster.
* As an administrator, I can pause mirroring for a pool or RBD.

Comment 6 Ken Dreyer (Red Hat) 2015-12-11 18:41:59 UTC

There will be a new daemon "rbd-mirror" that runs on a separate server, similar to how we isolate RGW on its own node(s). It is essentially a client to the cluster, so same constraints as RGW.

Comment 10 Jason Dillaman 2016-05-02 19:53:17 UTC

Looks good to me -- only minor comment is perhaps mention that it is asynchronous and crash consistent mirroring?

Comment 13 errata-xmlrpc 2016-08-23 19:26:36 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2016:1755