The Backup That Hung Forever on OneDrive
A Kopia job sat at 0% all night because it tried to read files that didn’t actually exist on disk yet.
A Kopia job sat at 0% all night because it tried to read files that didn’t actually exist on disk yet.
I deleted nine files on purpose — and my backup node helpfully deleted them everywhere else too.
A green-lit backup agent that hadn’t saved a single byte in weeks, because the machine and the server disagreed about what it was called.
One innocent git rm -r to untrack a folder, and 30,209 notes vanished off the disk in a single keystroke.
Google Drive and OneDrive are sync tools, not backups.If ransomware hits or files get deleted, they sync that too—straight into the void.☁️ Backup Rule 101