[Feature request] add ability to update base image instead of the oldest snap

[matveevandrey]

If I understand soft logic correctly the base image is never updated and all the diffs are merged to the first (oldest) snap: current_image = base_image + oldest_diff + newest_diff

Theoretically oldest_diff could become large than base_image and restore could take for a while.

It would be nice to have an ability to update base image every time the oldest snapshot expired/deleted

Thanks

[franklupo]

Hi, good idea. I think about how to implement it.

Best regards

[matveevandrey]

Any chance to get this implemented?

[franklupo]

Hi, We are writing the new tool. It will take some time but we are well on our way.

Best regards

[matveevandrey]

Any news?

[lephisto]

Done here: https://github.com/lephisto/cv4pve-barc/commit/e4884b4b3b4cb7a61da05ba6e63ced5fd71535e8

[mrtwister76]

Done here: lephisto@e4884b4

I don't believe this is what @matveevandrey required.

Instead, I believe they were asking for the oldest dif to be merged into the initial base image, thus the base image is continually updated. This would prevent having to make a regular full base image backups, which on many production systems (multiple TBs) can take a very long time.

I'm not sure whether this is technically possible (i.e. to merge a dif into the base image).

[matveevandrey]

Done here: lephisto@e4884b4

I don't believe this is what @matveevandrey required.

Instead, I believe they were asking for the oldest dif to be merged into the initial base image, thus the base image is continually updated. This would prevent having to make a regular full base image backups, which on many production systems (multiple TBs) can take a very long time.

I'm not sure whether this is technically possible (i.e. to merge a dif into the base image).

Correct. On my production system full backup takes a while(