When doing a restore, I decode the base64 file and overwrite the restored config file and everything works as expected. To work around this for all of my repositories I created a base64 encoded version of the config file that sits alongside the actual config file. Backblaze must be modifying the config file in some manner that corrupts it and makes it impossible to restore! I did an md5sum on the restored config file and the real config file and found they are different. My initial restore failed with the error “Fatal: Fatal: config cannot be loaded: ciphertext verification failed”. Well it took me longer than it should have, but I finally got around to actually testing out a restore and boy am I glad I did! If a new snapshot has been created on the Windows server, but Backblaze hasn’t finished uploading all of the new repo files I want to make sure that the repo files stored in Backblaze are valid (in particular i’m worried about files in the index folder). My only concern is how restic stores snapshot information. Restic repo files to the Windows server first, and then I will be able to use restic to restore the actual files to the Linux server. I will have to use Backblaze to restore all of the

I know i won’t be able to directly restore the data using restic. If the Windows server dies, I can use restic to redo the backup.īackblaze will only be used for disaster recovery in the case that both servers are lost at the same time. If my Linux server ever needs to be restored, then I can use restic to restore from the repository on the Windows server. From there the Backblaze client can backup all of the restic raw repo files (config/data/index/keys/snapshot folders). Restic will be used on the Linux server to send backups, manage snapshots etc to the restic repo on my Windows server. Linux Server Windows Server Backblaze backup service I am not looking for restic to push data directly to Backblaze backup service though. However B2 is cost prohibitive for the amount of data I am looking to store (~7TB+ without any versioning). Understood that restic can’t directly push data to the Backblaze backup service and can push directly to B2.

Backblaze linux client