Versioning for deleted files

[RobertSandiford]

According to the documentation here: https://help.backblaze.com/hc/en-us/articles/226937867-How-do-I-use-the-b2-sync-command-

b2 sync does not support versioning files on deletion. The deleted file is either kept with no indication of deletion, or deleted with no copy kept.

This is simple not fit for purpose for something like an application data backup.

Any plans to address this, or is there any alternative within B2 cloud storage?

[RobertSandiford]

Seems that the service does handle this correctly, so there is a documentation issue.

[ppolewicz]

b2 sync uses hide marker to indicate file deletion and sync option --excludeIfModifiedAfter TIMESTAMP allows you to filter file versions to select a point in time from which you'd like to restore. Is this the option that you are looking for?

I've read the document you linked, but I can't pinpoint the error there. Could you please quote it?

[RobertSandiford]

For files that are present in the B2 bucket compared to the source:

When a destination file is present that is not in the source, the default is to leave it there. Specifying "--delete" means to delete destination files that are not in the source. This will delete older versions of updated files as well.

Files at the source that have a newer modification time are always copied to the destination. If the destination file is newer, the default is to report an error and stop. But with "--skipNewer" set, those files will just be skipped. With "--replaceNewer" set, the old file from the source will replace the newer one in the destination.

I guess this refers though to files that have never been present in the source, as opposed to files that were present in the source until they were deleted.

As written it could be interpreted that when a file is deleted (and then is present in dest but not source) nothing happens.