coop-cloud/backup-bot-two
coop-cloud/backup-bot-two
6
0
Fork 4
Code Issues 9 Pull Requests Packages Projects Releases Wiki Activity

--host flag for backup create not implemented #53

New Issue
Closed
opened 2024-07-05 14:44:42 +00:00 by iexos · 2 comments
iexos commented 2024-07-05 14:44:42 +00:00
Owner
Copy Link

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
Owner
Copy Link

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.

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
Owner
Copy Link

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?
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
Something is not working
duplicate
This issue or pull request already exists
enhancement
New feature
help wanted
Need some help
invalid
Something is wrong
question
More information is needed
wontfix
This won't be fixed
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
3wordchant aadil abra-bot ammaratef45 Apfelwurm appletalk arjan basebuilder Brooke carla cas codegod100 coopcloud decentral1se fauno flancian Frando iexos javielico kawaiipunk knoflook lambdabundesverband mac-chaffee marlon mayel mirsal moritz nicksellen notplants p4u1 pau renovate-bot rix sef simon stevensting tobias trav val virtualboys wolcen wykwit xynosis yksflip
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: coop-cloud/backup-bot-two#53
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?