On Mon, Sep 26, 2016 at 10:13 AM, Matthew Von-Maszewski
wrote:
> Neither.
>
> The leveldb instance creates a snapshot of the current files and generates a
> working MANIFEST to go with them. That means the snapshot is in “ready to
> run” condition. This is based upon hard links for the .sst tabl
Neither.
The leveldb instance creates a snapshot of the current files and generates a
working MANIFEST to go with them. That means the snapshot is in “ready to run”
condition. This is based upon hard links for the .sst table files.
The user can then choose to copy that snapshot elsewhere, poi
there a backup tool that uses this yet? or is this meant more to be used
with snapshots provided through xfs/zfs?
On Monday, September 26, 2016, Matthew Von-Maszewski
wrote:
> Here are notes on the new hot backup:
>
> https://github.com/basho/leveldb/wiki/mv-hot-backup
>
> This sound like what y
Here are notes on the new hot backup:
https://github.com/basho/leveldb/wiki/mv-hot-backup
This sound like what you need?
Matthew
Sent from my iPad
> On Sep 26, 2016, at 5:39 AM, Niels Christian Sorensen
> wrote:
>
> Hi,
>
> We use Riak-kv Enterprise Edition as base for Riak CS to store fil
Hi,
We use Riak-kv Enterprise Edition as base for Riak CS to store files in.
Each customer has a separate bucket in the cluster(s) and all data is
stored multi site in 3 copies. Thus the "i lost a node" situation is
fully covered.
I need however, a solution for providing customers with a "si
