Re:Backblaze Announces B2 Compute Partnerships
by fnord123 on Wednesday April 04, 2018 @01:09PM
(#16756731)
If you have a file version, it's frozen in time. So if you have syncing with file versions you can rollback files individually.
Re:Backblaze Announces B2 Compute Partnerships
by nolok on Friday April 06, 2018 @06:37AM
(#16772223)
I don't think I was clear enough: with a two way sync, if a disgruntled employee / script failure / any other thing destroys the file version 1.0, it gets uploaded and replace the old file version 1.0
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.
Re:Backblaze Announces B2 Compute Partnerships
by fnord123 on Friday April 06, 2018 @06:08PM
(#16777909)
The version (in S3) is a hash of the data so if you remove your local version and replace it then you won't be tricked into thinking version 1.0 is the wrong thing (unless someone brute forces a new file with the same hash).
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.
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.