![]() Backblaze was designed as a backup solution, it's intended to be a 1:1 copy of your user data, and if your data set changes we change it on our end as well, with a 30-day history for accidental deletes. I think once I switch away from Aperture over to Photos, which presumably has a rock solid backup to iCloud photos, then simply doing a quarterly backup or so with CarbonCop圜loner + Arq to AWS + DataBackup to USB key will have my OS X backups covered. Really feel like I'm living in the future. And both crashplan/backblaze "everything for $5" come with massive caveats (like deleting backups of Hard Drives that haven't been plugged in for 6 months - I've got Arq Backups of Hard Drives that I haven't plugged in for a couple years, safe and sound) - and I've never had an AWS backup bill in excess of $3.00, ARQ does a wicked good job of keeping your backups on a tight budget.Īlso - awesome win for ARQ - when I moved to Singapore, I simply added a AWS Singapore S3 Bucket and wowza - fast backups on my gigabit ($49/month) link from MyRepublic. Yes, I have Crashplan (for the last couple years, backblaze for the three years before that) - but the constant chewing up of CPU cycles gets annoying after a while. I have mentioned this to Support.Arq, (For backups to AWS - though obviously supports every cloud back end under the sun) and "Data Backup" by ProSoft engineering (For backups to USB) are my goto backup tools for day-day ensuring all my work documents are kept up to date. The only issue I have is that the restore tab shows the two by their folder name, not their path name - so confusing if they have the same folder name. I will next start adding a network folder to my backup set - that will be like your situation with your NAS.Įdit: Yes, it nicely dedups between a local folder and a network share so long as they are in the same backup set. I am yet to migrate to Arq7 and I am doing my testing/discovery of Arq7 on my MacBook. I liked one top level folder per backup set (for clarity in naming) - I need to get used to the change. But with Arq7 these need to be reorganised into a single backup set with multiple top level folders. ![]() With Arq5, you need a distinct backup set for each top level folder or disk drive. So not as bad as I first said - sorry about that - I was confusing myself as I think you realised.ĭeduplication in Arq5 is across all backup sets for a destination (for a single computer). And a set can contain multiple top level folders. )ĭeduplication in Arq7 is across a backup set. I think I need to undo some of what I said. See my reply to 3dbruce below - it is not as bad as this!! To me this is dumbing down and is a move in the wrong direction - compare with Duplicacy which deduplicates across all computers sending to a destination. Same applies to adding top level folders on a disk volume. Then the annoyance is that whenever you plug in an external drive (or do any changes to partitions, volumes, etc.) that drive will get backed up unless you remember to exclude it. Support's solution is to backup everything (just like Backblaze) in a single backup set and add exclusions for what you don't want. Move content from one folder tree to another and Arq 7 needs to resend all the data to your destination. Which is not very good for those of us that have even a few top level folders specified. ![]() Arq7 only deduplicates within a backup set. Arq5 deduplicates across all backup sets (folder trees) for a Mac. My big disappointment is with deduplication. But there are annoyances an disappointments. It is an enormous improvement over Arq 6. Arq 7 does indeed seem solid from my limited testing.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |