restatic VS awesome-restic

Never used, but seems to be one here: https://github.com/Mebus/restatic

I use restic with BackBlaze on my servers and laptops. There are several guis for it; take your pick (another, and another).

Restic would be my main choice, particularly for offsite (over the network) backups. * Free, open-source, cross platfrom * Permissive license * deduplicating backup * can back up to local disk, dumb cloud file storage, or its own server (rest-server). This includes s3 buckets. * rest-server can run in append-only mode which prevents ransomware (etc.) from deleting your backups. * does not require shell/ssh access to remote system where backups are stored. However, shell access in at least the same datacenter may be helpful to reduce the network overhead of prune operations. * can mount backups, including from cloud storage, using fuse filesystem on linux * can pipe data into restic and add a file to a backup. So, for example, you can dump a database "mysqldump [...] | restic -r /srv/restic-repo backup --stdin --stdin-filename mysql.dump" * its own server, rest-server, can be setup to do append only backups so ransomware can't erase your backup (provided you make it difficult to log into backup server manually) * command line so you can script, ssh, etc. * There are various front ends available, though I don't see them as particularly useful. * Encrypted backups (unfortunately, there is no option for unencrypted ones, store the password alongside the backup if you really want "unencrypted"). Multiple users can have different keys so you can have an a master oops key for decrypting backups or an enterprise escrow key so you can decrypt backups after a user leaves. Make sure your encryption keys are stored somewhere you can access without restoring the backup (i.e. store your keepassxc file alongside the backup, not inside it). * in addition to built in drivers for various cloud based systems, it also can use rclone to access others. * backs up extended attributes including ACLs. Note that if you fail to backup extended attributes, some file based encryption systems (such as fscrypt) will not be recoverable as the information needed to recreate the per-file key is stored as an extended attribute. * multiple machines can backup to the same repository which can allow deduplcation across hosts. * You can do a local backup with restic, then transport the drive to an off-site location and use it online with rest-server. * important metadata is cached on local machine. * Deleting a file from a backup may be difficult after it is included. There is no command to prune or forget an individual file. However, this does make spoliation of evidence difficult. * Works around some windows bugs. Uses VSS (volume shadow copy services) on windoze to access open files.

Hey, check it out this GUI at https://relicabackup.com/