--host flag for backup create not implemented #53

New Issue

2024-07-05T14:44:42Z

iexos commented

2024-07-05 14:44:42 +00:00

Wanted to test with a small service as stated in the README and now its backing up all services. Looking at the code, --host for backup create seems to be not actually implemented 😅

Wanted to test with a small service as stated in the README and now its backing up all services. Looking at the code, `--host` for `backup create` seems to be not actually implemented 😅

iexos changed title from ~~`backup --host create` not implemented~~ to `--host` flag for `backup create` not implemented

2024-07-05 14:46:16 +00:00

moritz commented

2024-07-05 23:14:32 +00:00

Its removed, because with restic deduplication it does not make sense to backup only one service. If you select one service to backup it removes all other services from the snapshot and the next time you do a complete backup it can't use the deduplication and a backup of everything is done. Maybe restic is just not the right tool for that. I would favor borg, but moving to borg is a big step.

decentral1se commented

2024-07-07 09:42:11 +00:00

Aha OK.

That does seem like a significant change in behaviour from the original create design in #20 This commit c73bbe8c0d right? Can understand the reasoning above but I think we do need to figure out a way to support this again with Restic?

I would imagine it's for the user to decide if they want to take the hit in performance? If they decide to backup a single service and then the whole thing, theys should just know they cannot avail of de-duplication between those backups?

Aha OK. That does seem like a significant change in behaviour from the original `create` design in https://git.coopcloud.tech/coop-cloud/backup-bot-two/issues/20 This commit https://git.coopcloud.tech/coop-cloud/backup-bot-two/commit/c73bbe8c0d3be5e7adee9f8669929d14847f8565 right? Can understand the reasoning above but I think we do need to figure out a way to support this again with Restic? I would imagine it's for the user to decide if they want to take the hit in performance? If they decide to backup a single service and then the whole thing, theys should just know they cannot avail of de-duplication between those backups?

decentral1se referenced this issue from toolshed/docs.coopcloud.tech

2024-07-07 09:44:23 +00:00

Backupbot Specification #258

moritz referenced this issue from a commit

2024-09-17 17:48:09 +00:00

add host while preserving filechange detection #53

moritz closed this issue

2024-09-17 17:48:37 +00:00

Sign in to join this conversation.