docs: Update backup script example #7734
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mmomjian
changed the title
jrasm91
reviewed
Mar 8, 2024
alextran1502
approved these changes
Mar 13, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When using a deduplicating backup program (Borg, Restic, etc), using gzip is counter-productive because small changes in the input data stream can lead to much larger changes in the compressed data to backup.
As an alternative, some programs advise that you can use
gzip --rsyncable, but uncompressed data is typically still preferred as it has a better chance of matching up with the existing chunks from prior backups.I propose that we update the docs to make Borg more space efficient as Immich will often have small daily changes to the database.
Also fixed some unquoted vars