You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks for your comment, sorry I didn't respond earlier but apparently my email notification on Github got messed up.
You can technically back up to a local usb drive, put both the data catalog (the sqlite3 db file) and the vault directory on that drive, and then when that drive is hooked up to a remote server you can use normal file copying utilities to sync it over to the other server's storage.
Note, that if you have a low-powered 2.5 inch usb hard drive, I've found that the sqlite operations can be somewhat slow -- in those cases, I keep the backup catalog (the "meta" directory variable in the /etc/snebu.conf file) on local storage, then copy it to the usb drive when the backup operations are finished.
Oh, and FYI, there is a new version I'm working (commits at the top of the git repository are working, but I need to write some more unit tests for them), which support public key data encryption (see the "tarcrypt.txt" file to see how it works underneath). Also working on creating a front-end in the main client script where you can back up to a local repository, and sync to the remote one transferring only the delta data. Working through how the UI will look, as it can be confusing (too many parameters) the way I currently have it set up.
hello! Thanks for a great backup tool!
I'm wondering if there's a way to seed a network backup with snebu?
I'm guessing that if so, it would be a process like:
Is this possible somehow?
The text was updated successfully, but these errors were encountered: