I have to say, this is an excellent solution and I am seriously contemplating on deploying it for all of our servers.
I'm a little unclear on one thing, are alternative S3 providers supported?
Restic 0.13.0
11–20 of 68 posts
Re: Restic 0.13.0
#12Unless it's for experimenting, I've stopped caring for backup solutions other than borg and zfs as the only way to prove their stability is to have them exist for a while without big complaints and new ones all seem to have complaints. Just having no data loss isn't enough which is the absolute base point but huge memory consumption and other operational issues are also showstoppers.
Borg being single-threaded is painful in the era of consumer 12 and 16 core CPUs, and even prosumer 64-core.
Re: Restic 0.13.0
#13Any thoughts on how this compares to duplicacy?
Re: Restic 0.13.0
#14Any thoughts on how this compares to duplicacy?
…or Duplicity?
Re: Restic 0.13.0
#15I have to say, this is an excellent solution and I am seriously contemplating on deploying it for all of our servers. I'm a little unclear on one thing, are alternative S3 providers supported?
Yes! I back up directly into Backblaze B2 using restic.
Re: Restic 0.13.0
#16I have to say, this is an excellent solution and I am seriously contemplating on deploying it for all of our servers. I'm a little unclear on one thing, are alternative S3 providers supported?
Yes! I back up directly into Backblaze B2 using restic.
Excellent. One more question. Assuming someone gains access to a node - will they be able to access the backups or screw with them in any way?
Re: Restic 0.13.0
#17I have to say, this is an excellent solution and I am seriously contemplating on deploying it for all of our servers. I'm a little unclear on one thing, are alternative S3 providers supported?
These seem to be the supported backends
Local directory
sftp server (via SSH)
HTTP REST server (protocol, rest-server)
Amazon S3 (either from Amazon or using the Minio server)
OpenStack Swift
BackBlaze B2
Microsoft Azure Blob Storage
Google Cloud Storage
And many other services via the rclone Backend
Re: Restic 0.13.0
#18Where can I read about the best solutions for backups? For nerdy people
There is also https://github.com/restic/others which has some keywords (e.g. is it encrypted, does it do compression) for most FOSS backup solutions. It can be outdated or incomplete for some entries, though.
Re: Restic 0.13.0
#19I have to say, this is an excellent solution and I am seriously contemplating on deploying it for all of our servers. I'm a little unclear on one thing, are alternative S3 providers supported?
These seem to be the supported backends Local directory sftp server (via SSH) HTTP REST server (protocol, rest-server) Amazon S3 (either from Amazon or using the Minio server) OpenStack Swift BackBlaze B2 Microsoft Azure Blob Storage Google Cloud Storage And many other services via the rclone Backend https://github.com/restic/restic#backends=
I saw that, I was specifically wondering about different regular S3 implementations like Linode object storage, Digitalocean spaces, Wasabi, etc
Re: Restic 0.13.0
#20Earlier quoted context omitted.
Yes! I back up directly into Backblaze B2 using restic.
Excellent. One more question. Assuming someone gains access to a node - will they be able to access the backups or screw with them in any way?
Depends which back-end you use and which configuration. (Assuming "node" here means a backup client and not a backup-hosting server.)
If you just put stuff on some standard storage (FTP, B2, etc.) without any permissions set up, then no backup client could stop the attacker from using the credentials you've deployed to the backup client to login to your storage and delete your backup files. This is not really specific to restic.
Accessing old files from a backup client is a weakness. Though, personally, I don't store things on a system that this system is not supposed to know, so if someone compromises this system and they see data from the past year... that's nearly the same as just seeing the data that is on this system today. Nevertheless, this could be solved by using public keys, so the backup clients has an encryption but no decryption key (of course it's not as trivial as this sounds, e.g. how could it still do deduplication etc.), but restic does not do this.