You are probably too careful, although this is not always bad, but there are a number of considerations. A good template is to have several snapshots (for example, weekly snapshots returning to a certain period) and all backups during this period of time so that you can restore known states. For example, if for some reason your last snapshot is not working for some reason, if you still have the previous snapshot + all sstables since then, you can use it.
You can delete all backups created after snapshot as an act of taking snapshots of snapshots and hard links to all sstables in the snapshot directory. Just make sure your snapshots actually happen and end (this is a pretty solid process with hard links) before getting rid of old snapshots and deleting backups.
You should also check your recovery process, as this will give you a good idea of โโwhat you need. You should be able to recover from the last snapshot + sstables saved since that time. It would be nice to start a new cluster and try to recover data from your snapshots + backups, or perhaps try this process in a test environment.
I would like to point out this article: 'Cassandra and Backups' as a good cassandra backup and restore run.
Andy tolbert
source share