%% generate tags start %% #software-engineering %% generate tags end %% #software-engineering/database  Problem: - Terso database incident resulted in data leak and loss. - Incorrect backup identifier configuration caused 0.07% of databases on the free tier to share a backup storage bucket. Solution: - The issue was noticed and fixed within a few hours. - A rerun of the migration with correct parameters was performed. - Databases were recreated using the backups from December 1st. Learning: - Terso acknowledged the incident, expressed embarrassment, and committed to preventing future data leaks and losses. - Internal processes will be improved to ensure correct backups and data isolation. - Deployment methods will be enhanced to prevent backup ID-related issues. - Better mechanisms for notifying security incidents will be implemented. - Terso aims to regain trust from the community and provide better features for data isolation.