Then turn the wifi on and try to back up again. Then generate another file, disconnect the wifi, but CANCEL the backup. The way I tested was to create a random 1G file and randomly disconnect the wifi in the middle of a backup while uploading that file, then turn it back on. Now all that said, it’s been many versions ago, both in Restic and Rclone. It just wasn’t as resilient to dropped connections, long pauses (say, putting your computer to sleep in the middle of a backup), etc. I think at one point I even showed that by backing up to B2 with just restic, then with B2 as an Rclone backend. My theory was that using rclone as a backend wasn’t as stable. But it does come in, eventually, and everything checks out. I have him backing up every Sunday, and sometimes I won’t get the snapshot to fully come in until like Tuesday. Now, at the same time, I’ve had zero issues on B2, even with his snapshots. Step 4 (Optional): The other possibility would be to use a standard WebDAV-Client like netdrive or webdrive (which you can download) and try if it works using such a tool.Īdditional Information: You can ask your local network/system experts to download the Fiddler tool from to identify the network/system problem.I think one of the issues is that I had one client on a spotty connection, plus he’d randomly put his computer to sleep in the middle of a backup (my grandpa).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |