11/7/2023 0 Comments Duplicacy fix missing chunk![]() ![]() The downside is it doesn’t have the robust versioning and scheduling like duplicati, but there are work-arounds for that. I couldn’t find the chunk being deleted in the prune logs, and the chunk doesn’t exist on the storage (GDrive). I can also map my backup drive as a “network drive” which gives me the ability to easily copy/paste data back to my array in the even I need to. I went through Prune operation returned an error, FATAL: chunk xxxx cant be found and Fix missing chunks. I have since switched to rclone as my backup agent, which syncs all 50ish TBs of data to my google drive. Backups can be created as usual, but to restore files you’ll need to provide the corresponding private key. As suggested in the fix missing chunks page I deleted the folders for those two snapshots from my google drive under the snapshots//10 and 11 and ran the backup job again. You can rebuild the database, but if you didn’t know you had an issue and went to recover data you would be totally out of luck. Starting from version 2.3.0, you can initialize a storage with an RSA public key. I notice that my Check job had failed in duplicacy web and reported missing chunks in the latest 2 snapshots numbers 10 and 11. I used duplicati for years, but similar to other posters here experienced database errors/database corruption. Disconnecting a drive is the guaranteed way to do this, since it simulates the loss of a drive. To do a real restore test, you need to restrict duplicati’s access to your locally stored data. There is nothing wrong with this, but if you do a test restore it’s possible/likely that you just grabbed the files you already had and it didn’t even look at your actual backups. ![]() ![]() By default, duplicati will look for local data to restore from before trying to pull that data from your actual backup. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |