ThatGuyJack/DuplicatiDocs
1
0
Fork 0
mirror of https://github.com/kees-z/DuplicatiDocs.git synced 2025-04-26 15:02:28 +00:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #45 from drwtsn32x/master

Browse Source 
Add auto-compact-interval and auto-vacuum-interval
This commit is contained in:
kees-z 2019-09-05 12:11:08 +02:00 committed by GitHub
commit c5ada0d65d
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 8 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
docs/06-advanced-options.md
View File

@ -39,6 +39,10 @@ When performing asynchronous uploads, Duplicati will create volumes that can be
`--auto-cleanup = false` `--auto-cleanup = false`
If a backup is interrupted there will likely be partial files present on the backend. Using this flag, Duplicati will automatically remove such files when encountered. If a backup is interrupted there will likely be partial files present on the backend. Using this flag, Duplicati will automatically remove such files when encountered.
### auto-compact-interval
`--auto-compact-interval = 0m`
The minimum amount of time that must elapse after the last compaction before another will be automatically triggered at the end of a backup job. Automatic compaction can be a long-running process and may not be desirable to run after every single backup.
### auto-update ### auto-update
`--auto-update = false` `--auto-update = false`
Set this option if you prefer to have the commandline version automatically update Set this option if you prefer to have the commandline version automatically update
@ -47,6 +51,10 @@ Set this option if you prefer to have the commandline version automatically upda
`--auto-vacuum = false` `--auto-vacuum = false`
Some operations that manipulate the local database leave unused entries behind. These entries are not deleted from a hard drive until a VACUUM operation is run. This operation saves disk space in the long run but needs to temporarily create a copy of all valid entries in the database. Setting this to true will allow Duplicati to perform VACUUM operations at its discretion. Some operations that manipulate the local database leave unused entries behind. These entries are not deleted from a hard drive until a VACUUM operation is run. This operation saves disk space in the long run but needs to temporarily create a copy of all valid entries in the database. Setting this to true will allow Duplicati to perform VACUUM operations at its discretion.
### auto-vacuum-interval
`--auto-vacuum-interval = 0m`
The minimum amount of time that must elapse after the last vacuum before another will be automatically triggered at the end of a backup job. Automatic vacuum can be a long-running process and may not be desirable to run after every single backup.
### backup-name ### backup-name
`--backup-name = Duplicati.CommandLine` `--backup-name = Duplicati.CommandLine`
A display name that is attached to this backup. Can be used to identify the backup when sending mail or running scripts. A display name that is attached to this backup. Can be used to identify the backup when sending mail or running scripts.