OliverIn 2025 @storj price increase was moderate: for ~1TB from 3$ to 5$. Fine by me. Still a good deal.
As of July 2026 the minimal fee jumps to 50$ - #10x
Let’s try out @hetzner instead. Did I say #arqbackup is amazing
Tom SheppardTIL that when Arq Backup does a backup and verify to my old low-end DS-116 Synology NAS, and I allow 100% CPU on 2 threads, it brings the NAS to its knees so bad that it can't even act as a reverse proxy anymore. I can't log into the web console, or open a Vaultwarden web interface, or refresh my Mastodon feed (and presumably all other servers can't reach mine).
A real annoying issue with Arq is that when it's verifying it can literally take 12-16 hours for large backups.
Robert Böttner@marcr Sieht bei mir im Zuhause/Homeoffice gerade so aus:
1. Backup in ein lokales Verzeichnis oder auf externe Platte (ArqBackup)
2. Sync auf lokales NAS mit RAID 1
3. Dezentrales Backup auf Cloudserver. Gerade noch pCloud, überlege aber Wechsel zu Filen oder auf meine selfhosted Nextcloud.
Läuft zuverlässig und tatsächlich ohne große Skripterei.
#backup #homeoffice #datasecurity #arqbackup #pcloud #filen #nextcloud
https://www.arqbackup.com
https://www.pcloud.com/
https://filen.io
Tom Sheppard has movedTIL that #ArqBackup doesn't consider a fingerprint being changed on a server as being an error and thus doesn't email any error message, even though it fails to back up. My wife's computer hadn't been backed up for 237 days and the only reason I know that is that I saw a transient notification pop up while I was standing at her computer. When I checked her backup logs it clearly showed the backup had failed. Sigh.
Sebastian CohnenI'm getting pretty close to a point where I feel I would not totally embarrass myself when publishing my first Rust code 😅
I already added some basic integration tests, removed more hardcoded stuff, etc. But I still need to rebuild a "test backup” for testing, collect my notes for things that are missing, write at least a little bit of README etc.
I'll push something to Codeberg in the next couple of days 🤞
Got distracted when I tested a slightly older backup created with Arq 6.2.54 (current major version is 7). The Arq 5 and 7 formats are "documented", the Arq 6 format is not. At first I thought this can't possibly work, but the extra undocumented byte I found in a metadata object in Arq 7 is not used in Arq 6. Other than that everything seems to work just fine.
Your backup repository can contain a mix of Arq 5,6 and 7 data. Arq 7 simply reuses data created by older versions.
I just realized that I can hash the restored files instead of writing them to disk. This way I can easily build a test mode which writes a text file with all files that would be restored with their respective hashes and compare that against a golden file. Could do the same with other file metadata too… 🤔
Yesterday I mostly did all kinds of refactorings, which was VERY rewarding! Most unwraps are gone, cleaned up a TON of “&str, String and PathBuf”-conversion mess and other unnecessarily complicated stuff.
I also caught myself trying to make sure not to accidentally mutate something… only to realize eventually, that the compiler won't let me unless I say so 😅
Slightly better error reporting to the user is next on my list, before I want to look at some basic integration tests.
oh, one more thing: There is plenty of meta data for files stored (like owner, group, permissions, extended attributes, …), but no checksums whatsoever 🙄 This means when a larger or slow restore gets interrupted there is no good way resume and safely skip files that are already provably correct restored.
That's not a good design IMO. And let me tell you, the oddities don't end there 😅
Today I did some testing using a read-only mount of one of my real backups using “rclone serve nfs” so I don't have to implement an SFTP client. This works quite well so far.
Also: I quickly learning that quite a few assumptions on the semantics of certain repository metadata objects are incorrect. As already mentioned, the docs are quite spotty to begin with, so this is basically reverse engineering now to figure out how this is meant to be used 🙄