Comments (8)
not officially. you could amend your source containers manually to achieve this though (by renaming the source container .sxbackup to something else and changing the config file .btrfs-sxbackup on both source and destination accordingly)
from btrfs-sxbackup.
what's your usecase for this?
from btrfs-sxbackup.
I think that it would be nice to have in case someone would need to make backups to a different physical locations.
from btrfs-sxbackup.
I am trying to set up a local and offsite backup solution that operates on independent schedules/frequencies. Let's say for example, I might have daily local backups, but only weekly offsite backups. I have been using duplicity in the past, which supports this, but I have been getting much better performance with this method of btrfs snapshotting.
from btrfs-sxbackup.
ok. I will consider re-introducing the customization of source container names. until then you can rename them manually.
I would suggest to keep the naming with .sxbackup- as a prefix eg:
.sxbackup-offsite
.sxbackup-local
as this will probably be the naming scheme I will follow when adding this.
if you have more questions let me know..
from btrfs-sxbackup.
does it work for you?
from btrfs-sxbackup.
I was able to get it working, but I had to do a few more things than just renaming the source container. This is what I did:
- Created the local backup job:
# btrfs-sxbackup init /source /dest
- Renamed the source container directory:
# mv /source/.sxbackup /source/.sxbackup-local
- Changed a line in the source container config file
/source/.sxbackup-local/.btrfs-sxbackup
source-container = .sxbackup-local/
- Changed a line in the destination config file
/dest/.btrfs-sxbackup
:source-container = .sxbackup-local/
- Ran the local backup job:
# btrfs-sxbackup run /source
- Renamed the source container directory:
- Created the remote backup job:
# btrfs-sxbackup init /source ssh://[email protected]:/dest
- Renamed the source container directory:
# mv /source/.sxbackup /source/.sxbackup-remote
- Added 2 lines in the source container config file
/source/.sxbackup-remote/.btrfs-sxbackup
source = /source
source-container = .sxbackup-local/
- Added 2 lines in the destination config file
ssh://[email protected]:/dest/.btrfs-sxbackup
:source = ssh://[email protected]:/source
source-container = /source/.sxbackup-remote/
destination = /dest
- Ran the remote backup job:
# btrfs-sxbackup run ssh://[email protected]:/dest
- Renamed the source container directory:
This method does work, but it is very cumbersome and annoying. One thing that bothers me is that I have to trade ssh keys two ways (source <-> remote) because when I run the remote job, it connects back through ssh to my local computer to run the backup. Its adding this additional SSH connection that seems totally unnecessary.
from btrfs-sxbackup.
yes, renaming the source and editing the config file, two steps as mentioned.
takes like 10 seconds, I don't really see how that's cumbersome, even though it's a manual process admittedly.
you wouldn't need to have two backup jobs to have both push and pull though, except you really want to keep them entirely separate.
if you have suggestions how to avoid two way authentication in this case I would be pleased to hear them..
from btrfs-sxbackup.
Related Issues (20)
- Individual commands for local (`snapshot`) and remote transfer (`sync`) HOT 4
- No way to disable compression HOT 2
- Allow to disable ssh compression HOT 2
- Allow to specify ssh cypher HOT 5
- Backup not working unexpected EOF in stream HOT 4
- Incremental backup not working HOT 19
- Destination retention is not applied HOT 2
- sxbackup uses pv when invoked by systemd timer. HOT 3
- Run a pre- script on remote source? HOT 5
- Btrfs-send resiliency in the presence of tcp connection drops HOT 1
- btrfs-sxbackup requires (but does not document) "ionice" on the target HOT 1
- Enable compression on destination only HOT 4
- Command to make instant snapshot only, to transfer it later HOT 4
- Add cli argument to force disable pv for launching in cron scripts HOT 1
- Add transferred snapshot data size to logs output HOT 1
- Missing destination url in ssh source .sxbackup/.btrfs-sxbackup config file HOT 6
- btrfs-sxbackup fails to update backup job with ssh source HOT 1
- add webhook support HOT 1
- Add "--proto 0" to send/receive HOT 2
- File contains no section headers HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from btrfs-sxbackup.