Confusion about Cloud Sync "local" and "remote" folders when using Backblaze B2

[Gene]

I am setting up Cloud Sync to back up my DS920+ to Backblaze B2. I do not understand what folders to choose for "local" and "remote." This is my folder structure when I select the "local" field in Cloud Sync. It appears I need to create 5 tasks to back up everything, since I can't leave the field blank (or just select DS920).

If it helps, I have two volumes, vol 1 is "GENE" and vol 2 is "JOSH." I think "home" and "homes" are both on vol 1. I am brand new to using a NAS, so am slowly figuring this out. Thanks for your help.

-- post merged: 16. Mar 2022 --

After writing the above I did more searching on the Backblaze site and ran across an article "How to use Synology Hyper Backup with Backblaze B2." In the graphics they supply it appears I can backup by volume, so I would need only two tasks to backup myself and my son. Is this correct?

Which Synology app is best for backing up to Backblaze (Cloud Sync or Hyper Backup or another)? Thanks.

​

 

[Rusty]

Which Synology app is best for backing up to Backblaze (Cloud Sync or Hyper Backup or another)?

It depends on your need. Cloud Sync is actually a sync tool, and HB is a scheduled backup solution. So it will be up to you to decide.

 

[Gene]

Rusty, thanks. That was my problem. I didn't understand Cloud Sync was actually a sync tool (duh). I have found instructions for Hyper Backup and started it backing up to Backblaze.

 

[Telos]

I didn't understand Cloud Sync was actually a sync tool (duh).

Let me confuse you then. All that @Rusty said is correct. Cloud Sync IS a sync tool. However, if your B2 bucket is set to versioning, Cloud Sync is for all practical purposes, a backup tool.

However (again), since you changed to Hyper Backup, you will want to disable B2 bucket versioning, as Hyper Backup handles all versioning (otherwise you will be paying to store useless versions of discarded Hyper Backup files).

Also... if you are unfamiliar with Hyper Backup, it stores files in a database, so that the native files are not viewable from the B2 bucket.

Was I successful? Are you now more confused

 

[Gene]

No, actually, I did understand what you said; thank you. But now I seem to have two opinions - yours and the person whose video I watched.

I set up Hyper Backup following SpaceRex (

To view this content we will need your consent to set third party cookies.
For more detailed information, see our cookies page.

Accept third party cookies

). He advised setting Lifecycle Settings to the last 30 days. But if Hyper Backup handles versioning (which I did not know, or at least did not understand), then it seems logical to turn that off in B2.

I just read an article on Synology about Hyper Backup, which says "With Hyper Backup, up to 65535 versions of data can be retained while storage consumption is minimized with cross-version deduplication. Data backed up are kept in a proprietary database which can be easily browsed, downloaded or restored...." So deduplication means versioning? I just opened Hyper Backup in DSM and since it is running I can't find a way to look at the settings. Do I just let it run? Or is there something I should look at and set correctly?

Why would SpaceRex tell us to turn on versioning on B2? I would appreciate comments and/or advice regarding the SpaceRex video. As a brand new NAS owner I found his video easy to follow step by step, so I did. But if there is a better way to do this I want to learn. Thank you.

-- post merged: 17. Mar 2022 --

[Edit] Oops. Sorry, I didn't know putting that link in was going to embed the video. Is that bad etiquette?

 

[Rusty]

Is that bad etiquette?

Its fine, don't worry about it

 

[Telos]

He advised setting Lifecycle Settings to the last 30 days.

He's well-intentioned (I'm a fan, FWIW), but I see this as impractical. Here's why... His premise is that your last B2 back up is crypted. If that were to happen, you will find it nearly impossible to determine which versions of which files were present prior to encryption. Even your latest HB backup to B2 contains numerous files and folders with differing dates, Know which of those versions of each file represent a specific backup is near impossible. For example... a backup I took last night shows this in part...

Each of these folders are "current"... but how would I know that as I was wading through the B2 versions, unless I knew absolutely the entire HB database structure.

If 30 days makes you feel safer, then fine, nothing wrong doing that, but trying to recreate the HB database of a prior backup is daunting beyond words.

As far as HB versioning goes, that was covered in the video (11:26) under "retention".

I didn't know putting that link in was going to embed the video

Actually, I prefer that. Good for others seeking info here.

 

[Gene]

Guys, thank you. I am finally getting back to this. I went into Backblaze to turn off versioning and see "Keep all versions" or "Keep only the last version." Which setting turns off versioning? I'm guessing from what you have said already that "Keep only the last version" is correct, because inside the HB database will be a record of all the versions. This way I am keeping only the HB database online, as it is updated and uploaded each evening, and it contains "all versions." Is this correct? Thanks.

 

[Telos]

I went into Backblaze to turn off versioning and see "Keep all versions" or "Keep only the last version." Which setting turns off versioning? I'm guessing from what you have said already that "Keep only the last version" is correct,

This is correct. Only the last version.

 

[Gene]

That is very helpful. Thank you, Telos.