So the latest master AND the current stable build both give me: Plus we have forced updates with automatic reboots, which sometimes screws things up too. I don’t have this issue if I run prune from work - I just don’t like using my work connection for that. All this happened cause I got the idea in my head that now would be a good time to run prune since I moved and now have 100mb fiber now instead of DSL. I’ve done check -read-data about three times just to check on it occasionally with no errors at all. I should mention I’ve used pCloud for about a year now, with no issue at all - but I’ve been (justifiably) paranoid about running prune. Might make it more robust with the occasional network hiccup? I’m still wondering if there isn’t a retry or low-level retry switch I should try passing to rclone via restic. I’ve been messing with duplicacy CLI, which natively supports webdav, and it’s been working just fine with pCloud and a ~70GB repository - but I vastly prefer restic. Hopefully over time restic + rclone webdav stability will improve. I’m going to try continuing to use pCloud, but only prune once or twice a year - and on a cloned repository, at that. Unfortunately I’ve already bought a lifetime account. Then I’ll do a little manual pruning if anything is missing, then run a check -read-data and see what that does, as you suggested. After this backup is done I’ll do the check and I am indeed using the latest master build, as of today (I’ve been using one from about a month ago before this, too). Nearly all of it should already be in the repo, unless it got corrupted. It’s got about 700GB to sort through still.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |