$ borg init -encryption=repokey ~/Desktop/borgĭo you want your passphrase to be displayed for verification? : nįailed to securely erase old repository config file (hardlinks not supported>). My comment, however, was referring to the ability to use the borg mount command to view the contents of the borg repo itself, not to simply add the remote filesystem upon which the repo is In the thread that was referenced earlier ( ) it appears you were never able to reproduce the original poster's issue? My understanding of his post was just that there was some issue using borg with rclone mount it seems that even if the original poster correctly identified a reproduce-able issue, one solution might just be single threaded operation of both borg and rclone. That is not my understanding of his post. My intention was to do this with an rclone mount, but should that prove impossible, I would use a locally mounted storage for the initial repo, move that repo to google drive, and attempt to merely run the incremental backups against rclone mount.Īs mentioned near the top of this thread, people trying to do that are having trouble, and he was so far unable to diagnose, much less fix it. Run borg in server mode with the "cloud storage" either attached to it (currently not possible with Google Drive storage AFAIK, so you'd have to use Google Cloud storage which is expensive in the long run), or writing to attached instance storage and then copying from there to some "cloud" like Google Drive using rclone separately. But obviously, many many thanks to for his amazing work, and involvement with the community. (and kudos for a fantastic utility but please note that I didn't write borg nor rclone nor any other "utilities" mentioned here If you mean rclone, then the guy to thank for is but please note that I didn't write borg nor rclone nor any other "utilities" mentioned here If you mean rclone, then the guy to thank for is I was under the impression you were involved in borg development. To do "cloud storage" with borg right now, you'd either have to try and run it writing to an rclone mount mountpoint (with the caveat noted above), or set up a VM instance (like the micro instance you mentioned above) to run borg in server mode with the "cloud storage" either attached to it (currently not possible with Google Drive storage AFAIK, so you'd have to use Google Cloud storage which is expensive in the long run), or writing to attached instance storage and then copying from there to some "cloud" like Google Drive using rclone separately. I'm not familiar with Arq, but regarding Borg please note that it only does the first two right now ("local backup" and "NAS backup", and the latter presuming you NAS is either running borg in server mode and being accessed via SSH from the client, or exporting a network - NFS, SMB, etc - share to the client, where borg would handle it just like local storage). Borg, on the other hand, would let me do a local backup, a NAS backup, and a cloud backup all with one tool, so it is far superior Arq manages to do basically this task, so I'm confident it is possible to interact with the API in such a way as to keep a deduced, incremental backup on my gdrive.
0 Comments
Leave a Reply. |