Sadly it still means if the source gets corrupted for whatever reason the backup is done, for business files sync is really not backup (I don't think I'm teaching you anything there, but really this sadly doesn't fit my needs at all). Also Hyper Vault is all about the intelligent versionning.
While it's possible to trick it by doing the backup somewhere and then syncing THAT to B2 (and I do it for my personnal NAS), it's too much of a hassle and "complex" setup that I can't see myself pushing that to my customers.
OVH managed to get them to add HubiC in there so clearly there is a way. Hope you will keep pushing them until they move on it ! And thanks for making such a great product :)
Anyway, snapshots give me what I'm looking for re: versioning.
They know we'd like it in there, think that OVH was there before C2 was ready so they are "grandfathered in". Best way to let them know you want it is to add your voice to the thread!
With versioning it is.
The purpose of file syncing and backuping is very different, one is ensuring that a change on the source is replicated to the destination and is kept up to date on changes, the other is taking a snapshot frozen in time no matter what happens on the source.
Backup is not just about having a copy, it's having a copy that stops being kept in sync with the original after it is made.
There is also a concept of Write Once Read Many in storage which is used for compliance. So you can use sync with WORM and it's basically append only.