Best way to back-up riak
Jason J. W. Williams
jasonjwwilliams at gmail.com
Tue Jul 27 12:36:57 EDT 2010
Honestly the holding back of replication from Riak OS is the only real downside to the product. Reminds me of the old adage there's those that will never pay for OS software...and those that can't afford not to (because of things like Sox).
Sent via iPhone
Is your e-mail Premiere?
On Jul 27, 2010, at 8:03, Justin Sheehy <justin at basho.com> wrote:
> On Wed, Jul 21, 2010 at 2:01 PM, Alan McConnell <alanmc at swingvine.com> wrote:
>> I'm curious about this as well. Say I have a ten node cluster. Could I
>> just schedule a midnight copy of each bitcask data directory every night,
>> then restore to another ten node cluster by dropping one of each data
>> directories on each new node? How close does the timing needs to be? What
>> if the data directory snapshots were taken seconds or minutes apart?
> While Basho does provide a product including features that make
> whole-datacenter failure much less of a problem (by fully replicating
> to a cluster in another location) I will answer assuming you have only
> a single cluster.
> The timing doesn't have to be perfectly synchronized, but you should
> try to make it as close as is practical just so that you have a good
> way to judge what is contained in a given backup. If a storage (put)
> operation occurs in an interval between single-node backups, it will
> be present in the restored cluster when requested (and repopulated via
> read-repair) as long as it was in at least one of the nodes.
More information about the riak-users