From: Jason Dillaman <dillaman@redhat.com>
To: changtao381 <changtao381@163.com>
Cc: ceph-devel@vger.kernel.org
Subject: Re: About rbd journal
Date: Tue, 8 Dec 2015 22:58:08 -0500 (EST) [thread overview]
Message-ID: <2147390578.31102155.1449633488780.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <0e3101d1322f$22a53880$67efa980$@com>
The in-development RBD journaling feature is designed to be utilized with a future RBD mirroring daemon to perform continuous and point-in-time consistent replication of RBD images to another Ceph cluster (specifically with disaster recovery situations in-mind).
Until this feature is available and stable, periodic RBD incremental diff exports are probably the best backup alternative.
--
Jason Dillaman
----- Original Message -----
> From: "changtao381" <changtao381@163.com>
> To: dillaman@redhat.com
> Cc: ceph-devel@vger.kernel.org
> Sent: Tuesday, December 8, 2015 10:10:17 PM
> Subject: About rbd journal
>
> HI,
>
> There is requirement from customers that need to continuous backup rbd image
> to backup device or another ceph cluster.
>
> As far as I know , rbd journal can be used to record all the rbd mutations
> to journal which is stored in rados objects in the same ceph cluster
>
> Is it has interface to push rbd journal to another storage device or
> another ceph cluster ? Or is is has dev plan?
>
> Or anyone has other good way to do backup ? Thanks very much!
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
prev parent reply other threads:[~2015-12-09 3:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-09 3:10 About rbd journal changtao381
2015-12-09 3:58 ` Jason Dillaman [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2147390578.31102155.1449633488780.JavaMail.zimbra@redhat.com \
--to=dillaman@redhat.com \
--cc=ceph-devel@vger.kernel.org \
--cc=changtao381@163.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.