No, the distinction in the application I cannot mention is only an idiosyncratic difference of terminology from other applications under discussion in this thread. If you are deleting files off your backup, it's not a very good backup and you can never be 100% sure it has full integrity unless you do a full scan against a known list of files from when you started backing up. Files can be deleted from the source, because you have them backed up, so they can be recovered. The mirror is one-way: files are added to the backup, but never deleted. When mirroring for the purposes of backup, the source generally can change but the backup only adds: never deletes. A good backup should be a large initial transfer, and then incremental additions for the changes. So if your source drive goes toast during the operation, you now lost your backup and all your files. Formatting the backup drive before performing the operation sounds like a A Really Bad Idea because your backup is. Other suggestions welcome, especially if the above notes change anything.Ĭlick to expand.This is a weird idiosyncratic thing that only your software seems to follow, the rest of the world is ok not making a distinction between a "backup" and a "duplicate". I am okay with the two-step process you describe and running the duplication from the Windows 10 machine is what I have in I'll look into the suggestions so far of: rsync, AOMEI Backerupper, and R8t (though TBH the $159 price is a bit steep). I would like the copied data to be easily accessible at the per-file level. I have about 6TB of data and as it happens I have a 14TB WD external drive that I'm willing to shuck and install into the backup Yes, if backup implies compression / reformatting, then indeed I do mean "duplicate". The NAS isn't particularly huge and I've only recently moved from internal HDDs to a NAS mostly for reasons of multi-PC availability and ease of future growth. Rather, the backup job may be interrupted when the host computer goes to sleep, and I'd like it: 1) to be able to resume when the PC wakes up and 2) to maintain a steady state where all data older than X is backed up. I.e., it's not that the backup program is trying to write somewhere that isn't available. To answer some questions / Yes, the target disk will sometimes be unavailable, but more to the point, the computer that houses that disk and runs the backup job will be off. (Look for a thread on the lower half of the first Mac Ach page, whose title is the full name of that application followed by the obsolete version number 13-I can no longer change the title on the ongoing 6-year-old thread-and with my "handle" as Topic Starter.) That was originally designed 31 years ago as a client-server backup application, of which the cheapest Edition that will back up a NAS is US$159 (there is a cheaper Edition for US$50, but the developer company has-IMHO opinion stupidly-removed the ability to back up from a NAS using that Edition.) Copy this post into that dedicated Mac Ach thread, and I think I'll be allowed to answer your questions so long as I don't discuss in detail the archaic GUI-which is due to be replaced in the next major version-for R********t Windows. The other application, which I've used for 21 out of the last 26 years, I am only allowed to refer to outside of one dedicated Mac Ach thread as R********t. That'll cost you US$50 for one Windows machine. One application, which I've never used but has a good reputation, is Arq Backup-got to the "NAS Backup on Windows" section of the linked-to document. If you're not willing to go through that two-stage process, there are two applications you could run on your Windows machine to back up all your data directly to Backblaze B2 storage-but not using the Backblaze "client". If you're willing to go through that two-stage process, and expend the extra space on your local HDD needed to store a "duplicate" of the NAS data on your local HDD, you could run the "duplicate" part of the operation on your Windows 10 machine with AOMEI Backerupper-but I think you'd have to spend some money because it looks like the Standard version won't duplicate from a NAS. Click to expand.If the data on your NAS "goes bad" and has to be restored, you'd have to (1) restore the backed-up data from Backblaze onto your local HDD and then (2) copy that restored "good" data from your local HDD back to the NAS or its replacement.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |