Because by default, Backblaze sets all bucket lifecycle policies to “ Keep all versions of the file (default)” as shown below:įurther, here is a test file I’ve uploaded, made a few changes a couple times and you can see the different versions, time stamps and file sizes: The only thing I can say to that is those individuals simply have not even bothered trying this method. THEN come back and let us know your thoughts.

)Ī “backup” would retain the file, at least with a previous version. A backup will keep deleted and changed files for a significant period of time, typically a year or more. I’ve just been experimenting with that “Don’t remove” option as I just realised (slow on the update I realise) that my Amazon Prime subscription allows me to create a sync job to Amazon Drive for all the photos on my NAS! That’s 117.24 GB (31,681 files)! Still only a fraction of the 1.6TB of data though that I have backed up with CrashPlan. – Backblaze B2 – 2TB $123 but extra charges for restores 2TB restore = $40 – Sync only Still, using NAS->Amazon sync (not bi-directional) and retain deleted files isn’t too bad an option.Īt the moment, my options for cloud backup are: #Synology cloud station backup settings update# – IDrive (5TB $7 for the first year – 2TB $70pa normally) – I can use this for Synology Hyper Backup – Amazon Drive (£55pa for unlimited storage) – Sync only, no versioning.

#Synology cloud station backup settings plus#.

#Synology cloud station backup settings upgrade#.

#Synology cloud station backup settings update#.

#Synology cloud station backup settings install#.

Backblaze hyper backup