Search

Switched the script to .backup, restore test came back with everything. Thanks.

cp on a live WAL database can give you a file with the WAL half-applied. Use sqlite3 readings.db ".backup /mnt/backup/readings.db" or the VACUUM INTO command. Both produce a consistent snapshot.

My backup script just does cp readings.db /mnt/backup/. The app is in WAL mode and writes every few seconds. Restoring from one of these backups gave me a database that was missing the last hour or so. Is cp the wrong tool here?

I said nothing.

got most of it back with photorec, filenames are gone though. using -n from now on. dont say anything lintroller

-n first. Always. With --delete, every time.

Because you told it to make /mnt/usb an exact copy of photos/. --delete removes everything in the destination that isn't in the source. You want /mnt/usb/photos/ as the destination. Getting it back: unmount it now and stop writing to it. ph…

ran rsync -a --delete photos/ /mnt/usb/ and now only the photos are there. other folders gone. why?? can i get it back

/etc, /home, a package list. In a tarball, on another machine, with a date in the name. It's not complicated. People just want it to be.

Add the list of docker images with their tags. Latest moves.

Volumes, /etc, compose files, and the crontabs. I forgot crontabs once. Restore test twice a year, in a VM.

I keep going back and forth. Right now: the docker volumes, /etc, and a list of installed packages. Not the OS. Not the media, that's replaceable. Curious what other people include and how often they test a restore.