However, there's no reason this won't scale to terabytes of data. Or put another way, I only want to pay for what I need. out of several terabytes of data I wouldn't lose sleep over. I really only have ~90GB of data that I never want to lose - Family photos, videos, docs etc. I have been 'backing up' since then, but not until I read about 3-2-1 Backup Rule, did I realize I need to up my game. Of course, one of the drives failed, and I had no backups. At the time I ran 2 10k RPM WD Raptors in RAID 0 in the early 2000s - not thinking about doubling the risk of data loss.

I lost some videos I recorded of myself playing videos games a long time ago that I very much wish I still had for nostalgia. Not to mention, fire, flood, theft, and other disasters. For those reasons, multi-drive failure is a real possibility. Hard drives installed in a NAS run under the same conditions, workloads, and are often the same brand and bought at the same time. Motivation Raid redundancy is not a backup If you want to use another command line tool, much of the instructions I provide here should still be applicable.

I'll describe how to use restic to backup folders you care about on your Synology NAS to an external hard drive and S3 conformant cloud storage providers that are supported by restic and one supported by rclone. However, if you're stubborn like me and want to use the same CLI tool you use elsewhere, this post is for you. If you're wanting to backup your Synology NAS, you probably just want to use one of their off-the-shelf solutions in their Package Center.

Backblaze synology