Revised statements and script RE: compression

main
capntack 2 years ago
parent e04cb5f7bc
commit 6e166ed967

@ -129,7 +129,7 @@ sudo chmod 600 /path/to/restic/password/.file
f. Pay attention to the restic tags in the script. When the script runs the forget and prune commands, it will run that against the entire repo. So you want to ensure the tags in that command match the backups you want it to actually affect. I would suggest, after running the initial backup in step 7 and then have the script ready, run it and then run the verification steps from step 8 again. Just to be sure you have it right. And if you have multiple sources going to the same repo, do the same. You can also perform [dry runs](https://restic.readthedocs.io/en/latest/060_forget.html#removing-snapshots-according-to-a-policy) on removal polices (and [on backups](https://restic.readthedocs.io/en/latest/040_backup.html#dry-runs) too, btw) to sanity check yourself before accidentally nuking your repo. See the disclaimer at the start of this README.
g. Regarding the compression level of the restic backup, you can choose `off`, `auto`, or `max`. I ran a super scientific one run each on my backup source and got the following results:
g. Regarding the [compression level](https://restic.readthedocs.io/en/latest/047_tuning_backup_parameters.html?highlight=compress#compression) of the restic backup, you can choose `off`, `auto`, or `max`. I ran a super scientific one run each on my backup source and got the following results:
Raw Data: 255 GB to Backup <br>
All levels of compression also deduplicate files <br>
@ -137,7 +137,7 @@ sudo chmod 600 /path/to/restic/password/.file
Compression Auto: 208.4 GB = 81.7% compression <br>
Compression Max: 206.1 GB = 80.8% compression
I did not note the time it took, but I want to say it was about an hour when set to `off`, and about an hour and a half for both `auto` and `max`. I personally use the `max` setting, as it didn't take much longer. And while it didn't really compress that much more, I feel like as I add more sources to the repo, it will slowly add up to better gains. But you can decide as you like for your own backups.
I did not note the time it took, but I want to say it was about an hour when set to `off`, and about an hour and a half for both `auto` and `max`. I personally leave it at the default of `auto`, as `max` didn't make much of a difference. But you can decide as you like for your own backups.
<br>

@ -42,7 +42,6 @@ readonly RSYNC_LATEST_LINK_02="${RSYNC_DEST_02}/latest"
readonly RESTIC_PASSWORD_01="/path/to/restic/password/01.file"
readonly RESTIC_SOURCE_01="/path/to/restic/repo-01"
readonly RESTIC_REPO_01="/path/to/backup/dest-01"
readonly RESTIC_COMPRESSION_01="max"
readonly RESTIC_RETENTION_DAYS_01="7"
readonly RESTIC_RETENTION_WEEKS_01="4"
readonly RESTIC_RETENTION_MONTHS_01="6"
@ -54,7 +53,6 @@ readonly RESTIC_TAG_02="tag02"
readonly RESTIC_PASSWORD_02="/path/to/restic/password/02.file"
readonly RESTIC_SOURCE_02="/path/to/restic/repo-02"
readonly RESTIC_REPO_02="/path/to/backup/dest-02"
readonly RESTIC_COMPRESSION_02="max"
readonly RESTIC_RETENTION_DAYS_02="7"
readonly RESTIC_RETENTION_WEEKS_02="4"
readonly RESTIC_RETENTION_MONTHS_02="6"
@ -110,7 +108,7 @@ cd -
####################
# --p points to the password file, -r points to the restic repo path
restic backup --verbose --compression "${RESTIC_COMPRESSION_01}" \
restic backup --verbose \
-p "${RESTIC_PASSWORD_01}" \
-r "${RESTIC_REPO_01}" \
--tag "${RESTIC_TAG_01}" --tag "${RESTIC_TAG_02}" \
@ -132,7 +130,7 @@ restic check \
-r "${RESTIC_REPO_01}"
# Remove or copy and paste as needed. Remember: multiple sources and tags can go to the same repo.
restic backup --verbose --compression "${RESTIC_COMPRESSION_02}" \
restic backup --verbose \
-p "${RESTIC_PASSWORD_02}" \
-r "${RESTIC_REPO_02}" \
--tag "${RESTIC_TAG_03}" --tag "${RESTIC_TAG_04}" \

Loading…
Cancel
Save