So: looking for advice: I am redsigning my backup plans: I Image and Increment with Macrium to a Synology NAS for local backup. I want to load the NAS to a cloud for offsite backup. I want the NAS > Cloud to be backed up on a schedule. Will likely use BackBlaze/IDrive for transparency of costing,usability and Price. So PC > NAS > Cloud. Any insights as to how the NAS backup (- Could be Synology Hyperbackup or Cloud Sync for convenience-) will handle a coincidental MAcrium Backup/Incremental creation/consolidation? Obviously, additionally, with a new Macrium Image file, the whole new file will be uploaded Any insight into how other backup tools: Backblaze/I Drive/MSP will handle any schedule overlap? PS: was annoyed to find I cannot get Macrium Support without paying for an a new license for upgrade to Workstation: seems like there were some changes I mised ??
A couple things, if I were you I'd ditch incrementals in favor of differentials since it eliminates any kinks in the chain. Also, does backblaze still require the file to be locally stored or else it gets deleted? That used to be the case, where files would get deleted if they did not locally exist. Carbonite is the same way. That kind of defeats the purposed of off-site backup. I would not use idrive for backup; although it can be done I trust Reflect a lot more. Try, maybe, pcloud+rclone, or mega.nz+rclone.
Thx Nate Sorry aboot the typos Yes you are correct: Bblaze and Carbonite and others are not meant for "archiving" By default, Backblaze saves any old versions or deleted files for 30 days, with the option to enable One Year Extended Version History for free. Thats ok for me: I want the cloud to "mirror" the NAS as total disaster coverage: the house burns down or gets burglarized. The NAS has 1.8 TB on board. Macrium processes will have some dynamic efects there: expand that on and off. I actually like pCloud implementation and sync, but downloads are zipped before downloading iDrive and Backblaze are a bit clunky but have worked ok on testing small files IDrive and Backblaze have native apps in Synology Mgt console AWS and S3 pricing and implementation hurts my brain. IceDrive and Sync.com are options Synology has Hyperback up and CloudSync as built in apps: hyperback up has special versioning and file structures Cloud Sync is just that a sync and so has limitations re security. I possibly could seed another NAS and put it in a remote location and backup via Tailscale: no specific advantage I can see over cloud options. There are plenty of possible options: The Macium image files are large files: not all cloud services will accept large files. Initial Upload speed is always an issue ater that not so difficult/time consuming. ( idrive and BB offer a physically seeding service with HDD via mail.) I appreciate your comment re incrementals: I had thought of Weekly full with daily incrementals for space consideration. I confess that I struggle with MAcrium templates and retention settings What I cant visualise is how any "sync" function from NAS to cloud will handle incrementals/full Synthetic mode which for me is any easy concept. I am not sure how large daily differentials will get: there is not much difference here on the PC week to week. Most of the NAS storage is archives of Docs, photos : very "quite" files A recent Macrium restore after a blown HDD reinforced the value of Macrium Maybe Weekly full with daily differentials? The other background problems will be speed uploading each "new" full image created in the Macrium template, and retention of deleted MAcrium files on NAS contributing to storage costs, although that can probably be managed through "cloud policies/retention rules. FWIW: Wasabi looked great: but Wasabi retains deleted files for a time and charges as if they are part of your storage!! Some of the fineprint in the Cloud services is pretty granular. There are hundreds of useful tutorial/review sites, the more challenging aspect is effective of use of Macrium which is now the cornerstone of my recovery plans. Oh: I also back up the NAS to a local USB for when the NAS goes pffft . Also time to update the NAS and USB with SSD me thinks. Ok, maybe my OCD is showing a bit Is any of this making sense LB
Wait, are you saying you prefer Idrive because it's synching software is easy to use? If that's the case, I think you're going to love rclone. I can help you with it's implementation with pcloud. I use that combination, so I know for a fact that there is no zipping unless you use the official pcloud software. How much data storage/bandwidth are you planning on? With rclone just mount your NAS on-demand, run your sync script to pcloud, and dismount if you want. It's pretty easy once you get your scripts ironed out.
Thankyou Heh: I aint no cli guru: beginerer at best I suppose, to condense the OP, : What is the best method for backing up or syncing Synology NAS to cloud. I get some mixed info re continous sync of large numbers of files and RAM use on the NAS ( Has 2GB) I know sync is not "BackUp", but this is a plan for disaster recovery.
I hate to repeat myself, but rclone really is awesome. I'm pretty sure it'll do what you want with a little scripting, which I'll help you with. Question, how do you typically access your NAS locally on your system?
Sorry about lag... W10: I have the backup folder with everything I want to save mapped as network drive I have the NAS link in the "Network" folder in PC
If it's already mapped it makes everything a lot easier. The NAS at that point becomes just like any other data. There are a lot of things that can do what you want. Rclone, FreeFileSync, or even the built-in robocopy. Essentially, you are not at all limited to the software provided by the cloud service. Next thing to do if pick which cloud service you want.
OK The other problem I am working around is that ( along with many others!!) my network drives will not reconnect after a reboot: that issue is a recurrent theme on many forums. Not sure how that would affect ant sync tool from Windows. Would have to , likely, install backup agent on NAS: is that what you are thinking? BTW: anyone else have the Network drive not reconnecting at reboot issue?
