![]() WARNING: This blog post is an experimental journal, the results are not yet in. Then there’s the cost (albeit minimal for both Arq, one time, and AWS’s S3, monthly) - when you may already have access to a free NAS volume at no additional cost. ![]() Conversely, the time to recover individual files may be slow but acceptable - but waiting days to recover all or many of your files from the cloud is unacceptable, even though it’s a fact of life. What I do not like about backing up to the cloud is the time it takes to back up, especially at the outset and whenever you do some major re-org on your disk. Off site means that I’m less likely to lose my backup in the same incident whereby I lose my primary set of data (e.g. What I most liked about it was that the backup was off site and that it kept versions over time much like Time Machine does. So let’s run with that risk here and experiment with using an unsupported NAS volume.įirst my back story: I previously backed up to the cloud using Haystack Software’s Arq to Amazon Web Services (AWS) Simple Site Storage (S3). ![]() So by now you may be aware that Apple only supports Time Machine on internal, directly connected or volumes shared wirelessly via AirPort, right? Why not regular Network Attached Storage (NAS) volumes? Because they’re unsupported at this time. ![]()
0 Comments
Leave a Reply. |