5 ms·
Could someone provide link(s) on how regular snapshots of databases can be taken like this? (Googling didn't help much, maybe I'm googling for the wrong keyword
by halukakin 4y ago
Could someone provide link(s) on how regular snapshots of databases can be taken like this? (Googling didn't help much, maybe I'm googling for the wrong keywords.) For me, backing up the database is a few-hour-long process. Restoring it for a developer again is a few hours process. I read about snapshots before but haven't realized they could be this effective.
- ClumsyPilot 4y agocan't most COW dilesystems like BTRFS or ZFS take a snapshot at a point in time instantly?
- abdulocracy 4y agoLVM does the same but at the block level. https://wiki.archlinux.org/title/Create_root_filesystem_snapshots_with_LVM https://wiki.archlinux.org/title/Create_root_filesystem_snap...
- rrdharan 4y agoIt’s the lack of clarity on how they manage access control for what should be regulated data that surprises me, more than the technology achievement.
- StayTrue 4y agoArticle says data is anonymized before dev use. Pretty standard practice.
- nick__m 4y agofor mariadb : 0) make sure the the database data volume is on lvm or zfs in a sql prompt: 1) BACKUP STAGE START; BACKUP STAGE BLOCK_COMMIT; 2) \! the shell command to take the snapshot 3) BACKUP STAGE END; you can now mount your snapshot, copy it offsite and delete it. The restore procedure is left as an exercise!
- halukakin 4y agoVery helpful. Thank you!
- mauvehaus 4y agoBecause it isn't a backup. They put the database into a quiescent state on disk, take a file system snapshot, let the dbms resume working, and send the snapshot data via rsync. This requires the cooperation of the dbms software to get the on-disk data quiesced. Then your snapshot has to go fast enough that the dbms doesn't end up with too many spinning plates before you let it start writing normally.
- halukakin 4y agoGot it. Thank you!