New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.

Comments
Thanks, that sounds pretty good.
Need to setup my homelab properly, but way to lazy atm. I have nothing important stored on VPSs luckily.
Seriously restic with those settings I discovered yesterday is a beat with speed. The backup of 400GB (documents, source code, photos, etc) to iDrive e2 (Ireland location, I'm in Finland) completed in just over a hour with my Gigabit connection and a restore of 54 GB completed in 9 minutes, so 2 minutes slower than with Storj but still super fast. This is the first time I see a backup tool consistently maxing out my connection for both backups and restores. I love it
If you are a developer, you might like rustic. It respects your
.gitignorefiles and all your build output can be excluded from your backups.I saw mentions of rustic but it's very new so I don't know if I would trust it with my backups yet. Are you using it?
Yeah, hosthatch has been awesome for me, I now have a 2TB in NL, 5TB in LA and 7TB in Stockholm, all used as borgbackup targets.
>
Funnily enough, I use basic settings like restic backup PATH --exclude=, works pretty fast for me but I do not have TBs of data to backup just yet.
Can Uptime Kuma monitor backup success / failure from Kopia or restic? how?
You can configure a "PUSH" check. Then in your backup script you make a CURL request to the URL for the check.
raw encrypted zfs send using syncoid. keys never leave the pocket
syncoid -r --no-sync-snap --sendoptions=w zfs/personal remote:zfs/personal-w, --raw
For encrypted datasets, send data exactly as it exists on disk. This allows backups to be taken even if encryption keys are not currently loaded. The backup may then be received on an untrusted machine since that machine will not have the encryption keys to read the protected data or alter it without being detected. Upon being received, the dataset will have the same encryption keys as it did on the send side, although the keylocation property will be defaulted to prompt if not otherwise provided. For unencrypted datasets, this flag will be equivalent to -Lec. Note that if you do not use this flag for sending encrypted datasets, data will be sent unencrypted and may be re-encrypted with a different encryption key on the receiving system, which will disable the ability to do a raw send to that system for incrementals.