Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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

Back up to multiple destinations in the same profile #103

Closed
strmd opened this issue Dec 26, 2018 · 5 comments
Closed

Back up to multiple destinations in the same profile #103

strmd opened this issue Dec 26, 2018 · 5 comments
Labels
priority:medium Non-critical improvement to functionality or usability type:feature New functionality

Comments

@strmd
Copy link

strmd commented Dec 26, 2018

It would be very nice to be able to be able to manage profiles more directly. Here are some ideas:

  • Import/export - repo-specific, single file (obviously shouldn't contain passphrase or such).
  • Ability to duplicate profiles - for applying the same profile to multiple targets, e.g. two offsite drives.
  • Templates (possibly) - save profile as template, create profile from template. Repo-agnostic. Perhaps expand default settings to a default template to be used as starting point for novice users, i.e. 'back up home folder except [on macOS: .Trashes, **/.DS_Store] with these sensible prune options', or onboarding offer to install a few example templates.
@m3nu
Copy link
Contributor

m3nu commented Dec 27, 2018

Import/export would be easy since every profile is just a row in sqlite.

Instead of duplication, I'd suggest to have backups to multiple repos in a single profile. Borgmatic does it like this. Of course it would need to fail gracefully if the destination isn't available.

Personally I have 2 HDs for onsite backups (using the same source folders and exclusions). I find myself changing the repo and then running the backup again. It sounds like your use-case is the same.

@m3nu m3nu added the type:enhancement Improvement of an existing function label Dec 27, 2018
@strmd
Copy link
Author

strmd commented Dec 27, 2018

Instead of duplication, I'd suggest to have backups to multiple repos in a single profile.

That might work just as well, yes. The profile as a starting point is common across other software and might be easier to grasp (I'm thinking of Vorta as a way to get people with no CLI experience to adopt Borg) but doing it in the way that makes most sense from a Borg perspective might be more flexible. Multiple destinations in the same profile would open up some neat possibilities, i.e. back up to every available destination, local or remote.

Personally I have 2 HDs for onsite backups (using the same source folders and exclusions). I find myself changing the repo and then running the backup again. It sounds like your use-case is the same.
Indeed. I did make two profiles and named them accordingly, but all settings including the password are identical.

@m3nu m3nu changed the title Making profiles portable Back up to multiple destinations in the same profile Dec 27, 2018
@m3nu
Copy link
Contributor

m3nu commented Dec 27, 2018

Then let's start out with multiple repos in one profile. For implementation, the repo-dropdown could have checkboxes, like this:

llcc0

@strmd
Copy link
Author

strmd commented Dec 27, 2018

👍

@m3nu m3nu added status:idea Proposed feature, discuss if its useful and removed type:enhancement Improvement of an existing function labels May 29, 2020
@m3nu m3nu added priority:medium Non-critical improvement to functionality or usability type:feature New functionality and removed status:idea Proposed feature, discuss if its useful labels Jun 8, 2020
@mauromol
Copy link

Multiple destinations for the same profile would be very useful, indeed. I really hope you can add this feature to Vorta.

Just a little note: having the ability to "clone"/"duplicate" a profile would still be useful when you want to create a new profile similar to an existing one but with few changes, instead of recreating it from scratch.

@m3nu m3nu closed this as completed Feb 15, 2021
@borgbase borgbase locked and limited conversation to collaborators Feb 15, 2021

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
priority:medium Non-critical improvement to functionality or usability type:feature New functionality
Projects
None yet
Development

No branches or pull requests

3 participants