this post was submitted on 17 Jan 2026
72 points (98.6% liked)
Selfhosted
60210 readers
951 users here now
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil.
-
No spam.
-
Posts are to be related to self-hosting.
-
Don't duplicate the full text of your blog or readme if you're providing a link.
-
Submission headline should match the article title.
-
No trolling.
-
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
In addition to daily backups, once a month I image the drive. I wrote a simple script triggered by a cron job to image the drive to a NAS backup. The daily backups go to 3 different offsite storage facilities, and two go to separate NAS drives. All drive images are kept both local and off premise as well. So, for individual files, etc, I can restore them from the daily backups. If the wheels fall off, I can restore the whole drive from an image. Might be a bit over engineered but I've been caught a few times and so I just decided that won't happen again.
Interesting.
Yep, I agree there's 2 types of backups:
Out of curiosity, how are you doing the drive imaging?
I wrote a script that is fired by a cron job once a month:
sudo nano /usr/local/bin/backup_drive.shspoiler
Make the script executable:
sudo chmod +x /usr/local/bin/backup_drive.shCreate Cron:
sudo crontab -e0 3 1 * * /usr/local/bin/backup_drive.shVerify cron:
sudo crontab -lI'm sure it could be written differently or that there is a better way to do the imaging, but that is the extent of my notes, and it works for me. As with any code you find on the internet, it is wise to evaluate before dropping on a production server.
Ah, good old
ddWhen you have some spare time, take a look at
partclone- clonezilla uses it because it only backs up used blocks, not free space, so more efficient.Thanks for the tip. I'll definitely check it out