![]() I worry about proprietary tar balls, but maybe these tools are mature enough not to worry. Is there a good thought process, or decision tree to use in order to pick the right option? Then there are tools that look more like rsync where I write a script. The Goodsync/Duplicati types that are "applications" that take a hash, build an index, do clever things and send bits to their own "repository". I started looking at the B2 client options. Today, I consider my NAS like another USB drive. I also move directories around and add/change disks from time to time. I use multiple machines, so I don't think Backblaze personal makes sense. I want better offsite, so I've started to do the research. Those USB drives are nice as I can pull a file or even open my Lightroom catalog directly if I needed to (sync issues aside). When I remember, I take one to the house and bring the other back to the office. I also robocopy to the USB drive I have in the office. I robocopy my working folders to a dedicated drive I affectionately call "backups". Today, I "backup" my current pictures and videos with a robocopy script. I may add more machines in the future, but for now, it is essentially one. ![]() I will want periodic checks to validate I can restore. I want a cloud archive that I hopefully don't need to access. Today, offsite is a pair of external USB drives I rotate and sync. ![]() I'm working on the 3-2-1 strategy, and need a better offsite. My goal is to backup my local media editing machine (95% photography, some videos and a few personal files). Or, maybe the question is, what is the best type of tool to backup to B2. I'm looking for advice on the best way to manage a B2 archive. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |