All Topics
All Topics
Technology
Technology
Design
Design
Programming
Programming
Science
Science
News
News
Gaming
Gaming
Entertainment
Entertainment
Business
Business
Finance
Finance
Sports
Sports
Health
Health
Food
Food
Travel
Travel
Art
Art
Music
Music
Books
Books
Education
Education
Politics
Politics
Personal
Personal
No algorithm. No AI slop. No ads. Just RSS. Pro-human. Indie writers. Real journalism. Open web. Chronological. Hand toasted.

Transitioning from Database Dump Files to Restic for More Efficient Backups

By

todsacerdoti

7mo ago· 8 min readen

Summary

The article discusses transitioning from traditional database backup methods using intermediary dump files (like mysqldump) to a more efficient approach using restic backup software. It explains the security and efficiency issues with the old method, including file overwrite vulnerabilities and storage inefficiencies, and details how restic allows direct backup of database files without intermediate steps, improving both security and performance.

Key quotes

· 4 pulled
What I used to do in order to back up some MariaDB databases for example was to have a script something like this called regularly
!!! Insecure file overwrite problem here if attacker can create their own /srv/backup/mariadb/all.sql.gz.new file. Should use secure temp file instead
The old way involves creating intermediary dump files which are then backed up, creating unnecessary storage overhead and potential security issues
Restic allows backing up database files directly without the intermediate dump step, improving both security and efficiency
Snippet from the RSS feed
Some notes on converting my database backups away from intermediary dump files

You might also wanna read