![]() Synology Cloud Station – mind(!) – is IMHO one of the best tools that Synology did so far (besides DSM itself).I can confirm, it works flawlessly, but is no more than a bit of a playground if one intends to have some files available publicly – for whatever reason (I use it to easily mirror and share my collection of papers with others without granting them access to my NAS). Synology “Cloud Sync” (see screen shot above) isn’t really backup: It’s a way of replicating files and folders from your NAS to some public cloud file service like GoogleDrive or Dropbox.No option, if elasticity and flexibility aren't key that much. Symform offers an interesting concept: In turn to contribution to a peer-to-peer network one gets ever more free cloud storage for backup still I was more keen on finding an alternative without ongoing effort and costīTW: Overall CAPEX for the new NAS was around EUR 800,- (or less than 2 years of AWS Glacier storage costs for not even the full capacity of the new NAS).Still quite a bit when already running 2 disc stations anyway which both are far from being over-consumed – yet. However, Glacier costs for an estimate of 3 TB would be $36 in Frankfurt and $21 in the US. Of all the public cloud backup clients ( ElephantDrive, HiDrive, Symform and Glacier) AWS Glacier seemed the most attractive as I’m constantly working within AWS anyway and I wasn’t keen on diving into extended analysis of the others.Time Backup is a Synology owned solution that offers incremental/differential backup I recently heard of incompatibilities with certain disc stations and/or harddiscs, hence this wasn’t my first option (whoever has experiences with this, please leave a comment thanx).The above screenshot shows available backup packages that can be installed on any Synology disc station: First things first: Options Synology Backup related Packages Which of the data is actively accessed but not changed (I do have quite a few archive folder trees stored on my NAS which I infrequently need)Ĭonclusion: For some of the data incremental geo-backup suffices fully other data needs to be replicated to the respective other location but kept read-only for some data I wanted to have readable replications on both locations.Which of the data is really needed actively and where?.How much upstream/downstream can I get for which amount of data to be synced? (ease of thought for me: both locations are identical in that respect, so it boiled down to data volume considerations).Is one of the 2 passively taking backup data only or are both actively offering services? (in my case: the latter, as one of the 2 would be the projects’ storage residing in the office and the other would be storage for media mainly – but not only – used at home).Besides that, a few additional constraints come into account when setting it up for geo-redundancy: ![]() Of course, it’s not 27 options – as in the headline – but it’s a fair lot of possibilities to move data between to essentially identical NASs for the benefit of data resilience. My new one is now a DS416 (same configuration I just upgraded discs in a way that both NASs now run 2 2TB and 2 3TB discs – mainly disc lifetime considerations were leading to this, and the fact that I didn’t wanna throw away still-good harddiscs (if you’re interested in the upgrade process, just post a quick comment and I’ll come back to that gladly – but with Synology that’s pretty straight forward).īored already and not keen on learning all the nitty-gritty details: You can jump to the end, if you really need to □ More than 1 backup My current NAS used to be a Synology DS411 (4 2TB discs, Synology Hybrid Raid – SHR – which essentially is RAID5). I wanted a home media streaming solution close by my hifi.In addition to that, I store quite a lot of important projects data meanwhile (in different public clouds, of course, but also on my office NAS) at one point I needed a second location to further secure this data.I store quite a bit of music (imagery and audio all-the-same) storing that solely in the cloud is (a) expensive and (b) slow when streamed (Austrian downstream is not yet really that fast).Why would a convinced “pro-cloudian” invest into a geo-redundant backup and restore solution for private (cloud) storage? The reasons for this were fairly simple:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |