t;> resiliency and not harming the source cluster mostly I would say.
>> Then how fast you write to the backup storage system will probably be
>> more often limited by what you can read from the source cluster.
>> The backups have to be taken from running nodes, thus it's ea
overload the disk (reads), network (export backup data to final
> destination), and even CPU (as/if the machine handles the transfer).
>
> What are the best practices while designing backup storage system for big
>> Cassandra cluster?
>
>
> What is nice to have (not to say m
(as/if the machine handles the transfer).
What are the best practices while designing backup storage system for big
> Cassandra cluster?
What is nice to have (not to say mandatory) is a system of incremental
backups. You should not take the data from the nodes every time, or you'll
either h
on SAN help us in this regard?
Apart from using SSD disk, what are the alternative approach to make my
backup process fast?
What are the best practices while designing backup storage system for big
Cassandra cluster?
Regards
Manish
