02:00:17.513 INFO SNAPSHOT_FILTER Loaded 20 include/exclude pattern(s) 02:00:17.504 INFO BACKUP_INDEXING Indexing /path/to/repo 02:00:17.504 INFO BACKUP_START Last backup at revision 24 found 02:00:01.338 INFO STORAGE_SET Storage set to b2://duplicacy There have been changes, each file will be listed in the output. When no changes have been made to the local repository since the last backup. When you run the backup script, here’s an example of what the output looks like 0 2 * * * root /path/to/repo/.duplicacy/scripts/backup.sh > /var/log/duplicacy/backup.log 2>&1īefore this can work, you must first create the /var/log/duplicacy/ĭirectory for the backup script output to be logged. This will run the script at 2am every morning. To actually cause the backup script to run, I call it from cron like withĪn entry in my /etc/cron file. usr/local/bin/duplicacy prune -keep 7:60 # keep a snapshot every 7 days after 60 days usr/local/bin/duplicacy prune -keep 0:365 Snapshots older than 1 year and keep 1 snapshot every 7 days for snapshots older The one I currently use below will remove all usr/local/bin/duplicacy -log backup -threads 2ĭuplicacy will execute scripts that you create in file called path/to/repo/.duplicacy/scripts/backup.sh #!/bin/bash The paths will need to be updated for your environment. Generate a lot more output which might be relevant if you’re logging the output If you want a slower and more thorough backup that hashes allįiles to determine what needs to be backed up rather than looking at file sizes This script will run a backup with log-style output, 2 threads, and otherwiseĭefault settings. Technique from stackoverflow, but I haven’t tested and implemented that yet. It to use flock instead of the DIY lockfile Here’s what my backup script currently looks like. Someone a backup script starts running before the previous one completes.
BackupĪt least as of Duplicacy 2.1.0, it does not nicely handle the situation where My backup script that ends up getting called by cron in there too. In order to keep everything in one place, I store Scriptingĭuplicacy expects certain scripts to live in a scripts directory within the Repository, which might be perfectly fine depending on your use case. For detailedĭocumentation on configuring exclusions that do what you’re looking for, seeīy default it will include everything in the local There are a lot of options for configuring exclusions.
#Duplicacy restore to another folder password#
duplicacy set -storage b2://duplicacy -key b2_id -value accountidgoeshereĭuplicacy set -storage b2://duplicacy -key b2_key -value keygoeshereĭuplicacy set -storage b2://duplicacy -key password -value passwordgoeshere Present more information on these options is on the project wiki Has the option to save these credentials in certain keychains if they’re duplicacy/preferences file using the following commands. Then all of this information can be stored in plain text in a If you feel comfortable with being able to protect the. Time you run your backup this obviously is an impediment to automated backups. Saving passwordsīy default, you will be prompted for your b2 id, key, and storage password every If you don’t want ecrypted storage, then don’t use the -e option. You’ll need the chosen storage password, the repository id (or access to theīucket to look it up), and the Backblaze B2 account ID and key. Your backup you won’t necessarily need to keep a copy of the config file, but In the config file in your storage bucket. Used to encrypt the key used to encrypt your files. $ duplicacy init foobar b2://duplicacy -eĭuplicacy will prompt you for your B2 bucket id and key, along with a password To initialize a Duplicacy repo at /path/to/repo/ with a repository id ofįoobar with encrypted storage to my duplicacy bucket in Backblaze B2, $ cd /path/to/repo The upside is that not anyone with access to your storage can The main ones are what you want to call your backupĪnd whether or not you want your backup to be encrypted Your repository and storage you can see the options usingĭuplicacy init help. There are a variety of options that need to be decided on before initializing Initialization Repo/Storage Initialization
I downloaded the latest version (2.1.0 as of when I’m writing this) and This article documents the steps I took to set up a daily backup to myīackblaze B2 bucket using Duplicacy on Linux.įor the sake of this article, lets say that my Backblaze B2 bucket is calledĭuplicacy (it doesn’t since someone else took that name) and the path to theĭirectory with all of the data I want to back up is called /path/to/repo/.
0 kommentar(er)
