Hi Michael,
Does this mean, that mean, that we have some kind of transaction logs where we will be able to "walk to" a specific time to restore a specific state?
the rbd journal records all changes to the primary rbd image which are asynchronously applied to the remote image. There is no way to jump to a specific point in time using the journal entries, they are deleted as soon as the replay has been acked. To actually walk back to a point in time there are rbd snapshots. They allow you to roll back an image to a specific snapshot. Regards, Eugen Zitat von Ml Ml <mliebherr99@googlemail.com>:
Hello List,
when reading: https://docs.ceph.com/docs/master/rbd/rbd-mirroring/ it says: (...)Journal-based: This mode uses the RBD journaling image feature to ensure point-in-time, crash-consistent replication between clusters(...)
Does this mean, that mean, that we have some kind of transaction logs where we will be able to "walk to" a specific time to restore a specific state?
Like: https://blog.sleeplessbeastie.eu/2016/02/29/how-to-perform-postgresql-point-...
Thanks, Michael _______________________________________________ ceph-users mailing list -- ceph-users@ceph.io To unsubscribe send an email to ceph-users-leave@ceph.io