vesetr.blogg.se - Synology drive vs cloud station

A means of copying that system-level backup to cloud storage for offsite safe-keeping.

This might be an image-level or file-level backup, though ideally it would have image-level restore capability (see below). That is, any given morning I might leave the house, if my laptop were stolen from the car, I wouldn’t lose any data. A means of regular system-level backup from each machine to the NAS, such that a complete recovery would be possible from the NAS copy.This should include version history, so deleted or modified files can be rolled back in time.

This should have the ability to turn off individual files or folder trees, as to keep some heavy-weight data off of machines that won’t need it.

A Dropbox-like shared folder, synced between all my machines, with the main files I use day to day.

I’ve got a few different goals I’d like to achieve with my home IT setup: Interestingly, this means there are two officially-supported and almost equally-easy ways to install Plex on your Synology NAS. With Docker, the entire Hub full of containerized applications is ready to install on your NAS. With the more powerful units like the “plus” series my DS1019+ hails from, you also get virtual machine capability and, in particular, native Docker support. Synology DSM offers an immense array of software tools to handle nearly anything: out of the box, you get Photo Station/Video Station/Music Station for media serving, “Media Server” for making that content available via DLNA, Synology Drive as basically a feature-by-feature clone of Google Drive, including both backup and “synced folder” functionality… And that’s without even touching third-party packages. I’ve chosen to build my data management and backup scheme around a Synology NAS, specifically a DS1019+. Some lives on one laptop, some on another machine. Some “primary” data lives on removable drives.

In particular, the simple 3-2-1 case above doesn’t work because “production” data, or the “primary copy” isn’t all in one spot. My case is a bit trickier – I have a bunch of different machines, LOTS of data, some big chunks that need to get shifted around kind of frequently (big virtual machines I shelve and retrieve for infrequent jobs), and so on. 3-2-1 provides near-perfect data threat coverage, which is why it’s the gold standard. Or so that when you delete a file while you’re on vacation, you can grab it from the cloud backup. One remote backup so that if your house gets robbed or burns down, your data is still safe in the offsite backup. So when your laptop gets stolen from the car, you’ve still got everything on your desk. Why these 3 copies? Two different copies so when you delete a file accidentally, you can quickly go find the backup. 3 copies of the data (Laptop, back up USB disk, and IDrive), 2 different physical media (laptop and USB disk, though also IDrive), and 1 off-site copy (IDrive). Hint: is an excellent deal, and supports client-side encryption to keep everything private. Then, on top of that, install your cloud backup provider of choice to regularly take things off-site. Maybe every time you sit down at your desk, you plug this in, and Time Machine (Mac) or File History (Windows) takes care of it. In the simplest “one laptop” case, this is straightforward: have one backup regularly scheduled to a USB hard drive. In particular, it’s critical to adopt a 3-2-1 backup strategy: 3 copies of your data, 2 different physical copies, with at least 1 off-site copy. Keeping everything backed up and synced in a way that’s sufficiently hands-off and automatic to be reliable, as well as easy to recover from in the event of data loss, is not a simple task. Data handling and backup can be hard, and everything below is my work-in-progress notes and effort towards achieving a system that works for me.īeing self-employed in technology, I’ve got quite an array of devices, machines, and systems to support even just in my household.