![]() ![]() unclear future and support model - most questions and requests are answered by “here is source, pull requests are welcome”.the chunks store will be gc and reorganised to decrease server storage usage Can be workaround with rclone destination but this adds a layer of complexity). very limited support for cloud destinations (no *Drive type services.no stable version yet - so not suitable for production.rather complex multilevel datastore structure that if corrupted not clear how to recover.My suggestion to implement that on the forums was met with complete silence. does not support extended attributes driven exclusions (for example to exclude all Files skipped by Time Machine on a mac).support to run server side component to facilitate ACLs.It’s nice and frequently requested feature on duplicacy forums. ability to mount backup history as a virtual drive.backup configuration is stored on the destination.The steps to remediate this issue are outlined in GnuPG#Unattended passphrase. Generally speaking one needs to explicitly allow programs to provide the passphrase to gpg agent instead of prompting the user. If you get gpg errors revolving around “inappropriate ioctl for device” it most likely has to do with changes to the gpg agent behavior from gpg version 2.1 up. Type -P keychain &>/dev/null || " gpg-agent >/dev/null 2>&1 thenĮval "$(cut -d= -f1 -detach-sign test-gpg.txt # Keychain is used to source the ssh-agent keys when running from a cron job # Uses separate encryption and signing keysĭest="scp:////backups/homeserver" Requires duplicity and gpg-agent with the keys and passphrases loaded as root. Some additional command-line options exist for comparing the repository state to the state of the local files, and to delete old snapshots so as to only keep a fixed amount of snapshots or only ones that are newer than a given date. restore file(s) to the state they had on a specific date, rather than to the most recent available snapshot.restore a specific file instead of the whole repository.(A local backup repository would need to be explicitly specified using the file:// protocol prefix!)Īdditional command-line option exist to allow: The URL argument is always treated as the backup repository, and the local path argument as the directory to sync with the backup. Note the reversed ordering of the arguments compared to the backup command above. To restore the local folder /home/me to the state of the last snapshot saved in the remote repository /usr/backup on host other.host, do: fine-tune encryption and signing of the backups.include or exclude specific files and directories from the backup (using shell patterns or regular expressions).Running the exact same command again causes an incremental backup to the existing backup repository.Īdditional command-line options options allow to: $ duplicity /home/me first time this command is run, it will create a full backup. To backup the local folder /home/me to the remote location /usr/backup on host other.host through the scp/ssh protocol, use: Deja Dup - Simple backup tool, that hides the complexity of backing up the Right Way and uses duplicity as the backend. ![]() It manages backup job settings in profiles and allows to batch execute commands. Duply - A shell front end for duplicity. ![]() It can save snapshots of directories and files to a remote GnuPG encrypted tar file, which acts as a backup repository.Ĭonnecting with the remote backup repository can take place through any of the following protocols: rsync, ftp, HSI, WebDAV, Tahoe-LAFS, or Amazon S3.īackups are granularly incremental, meaning that only changes in files (since the last snapshot) are stored. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |