Fabian Ebner b20bf9bf7d replication: find common snapshot: use additional information ... which is now available from the storage back-end. The benefits are: 1. Ability to detect different snapshots even if they have the same name. Rather hard to reach, but for example with: Snapshots A -> B -> C -> __replicationXYZ Remove B, rollback to C (causes __replicationXYZ to be removed), create a new snapshot B. Previously, B was selected as replication base, but it didn't match on source and target. Now, C is correctly selected. 2. Smaller delta in some cases by not prefering replication snapshots over config snapshots, but using the most recent possible one from both types of snapshots. 3. Less code complexity for snapshot selection. If the remote side is old, it's not possible to detect mismatch of distinct snapshots with the same name, but the timestamps from the local side can still be used. Still limit to our snapshots (config and replication), because we don't have guarantees for other snapshots (could be deleted in the meantime, name might not fit import/export regex, etc.). Signed-off-by: Fabian Ebner <f.ebner@proxmox.com>		2021-11-08 10:35:34 +01:00
debian	bump version to 4.0-2	2021-06-09 10:07:42 +02:00
src	replication: find common snapshot: use additional information	2021-11-08 10:35:34 +01:00
Makefile	build: switch upload target to bullseye	2021-06-09 11:39:15 +02:00