[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: snapshot strategy?

Taking a step back and in case you are hosted on a cloud - We are entirely on AWS and upload snapshots, and incremental files periodically, to S3 as part of the backup job. It gives us durability and the freedom to clean up from locale sooner than otherwise would require. Currently, we also are trying utilizing EBS snapshots, following Alain's lead in his TLP blog post, and results are promising so far in our env.


On Fri, Nov 2, 2018 at 10:51 PM Subroto Barua <sbarua116@xxxxxxxxx.invalid> wrote:

when taking snapshot, set tag like "uuidgen --time" and use this tag to clear out old snapshot.

On Friday, November 2, 2018, 9:28:03 AM PDT, Oleksandr Shulgin <oleksandr.shulgin@xxxxxxxxxx> wrote:

On Fri, Nov 2, 2018 at 5:15 PM Lou DeGenaro <lou.degenaro@xxxxxxxxx> wrote:
I'm looking to hear how others are coping with snapshots.

When taking a snapshot, previous snapshot files are not automatically deleted. You should remove old snapshots that are no longer needed.

The nodetool clearsnapshot command removes all existing snapshot files from the snapshot directory of each keyspace. You should make it part of your back-up process to clear old snapshots before taking a new one.

But if you delete first, then there is a window of time when no snapshot exists until the new one is created.  And with a single snapshot there is no recovery further back than it.

You can also delete specific snapshot, by passing its name to the clearsnapshot command.  For example, you could use snapshot date as part of the name.  This will also prevent removing snapshots which were taken for reasons other than backup, like the automatic snapshot due to running TRUNCATE or DROP commands, or any other snapshots which might have been created manually by the operators.