06.10.2024 Problem:
The client reported that data storage space was being exhausted because the incremental backups were being saved in the same location as the data storage. This issue forced the client to delete incremental backups to free up space for new data. The client requested a consultation on how to configure incremental backups to be created in a different storage location than the default data storage location.
Process:
According to the client’s description of the issue, the expert confirmed that there was no built-in solution available for changing the backup location within the Cassandra configuration file. The expert thoroughly reviewed the available options and verified that the default configuration did not support redirecting incremental backups to a different storage location. As a result, it was clear that adjusting the backup directory through the existing settings was not feasible.
Solution:
Custom script: A script was proposed to move snapshots to a new location, but it posed risks and was not a reliable solution;
Expand storage: The most effective and safest solution was to increase the data disk space. This could be done through cloud services like Amazon EBS by enlarging disks from the Hosting UI and using resize tools to adjust the storage capacity.
Conclusion:
The recommended solution was to increase the available space on the data disks rather than trying to create a custom script. Adding more space to the data disks is a more reliable and less risky approach compared to developing and implementing a custom backup script, which could be complex and prone to errors. Expanding the data disks will ensure that there is ample storage capacity for both data and incremental backups, preventing the need to delete backups to free up space and reducing the risk of running into storage-related issues in the future. This solution also simplifies maintenance and avoids potential complications associated with custom scripting.