Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Seed a network backup #15

Open
levi730 opened this issue Jul 24, 2020 · 1 comment
Open

Seed a network backup #15

levi730 opened this issue Jul 24, 2020 · 1 comment

Comments

@levi730
Copy link

levi730 commented Jul 24, 2020

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:

  1. Backup to local drive (usb, sata, etc) for speed in creating the initial backup
  2. Move that drive into a server
  3. Reconfigure things so the future (differential) backups will go over the network,

Is this possible somehow?

@derekp7
Copy link
Owner

derekp7 commented Oct 3, 2020

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants