Back(up)Thing - an alternative to Crashplan (and BuddyBackup)


(Antony Male) #40

Just another lesson: not everything you read on Wikipedia is correct!


(xor-gate) #41

In my opinion mixing synchronisation and backup is a bad thing, as they are two different things. You could fire an external application on event or periodic (e.g rsync, restic backup or borgbackup, zfs snapshot and zfssend).

If you use filesystem snapshots with delta sending you get performance and stability for free because it is in kernel space implemented. Userspace backup software has also advantages because you are less bound to specific kernels and filesystems.


(Jakob Borg) #42

Insofar as Syncthing can transport files from A to B it can be used as part of a backup solution. But a backup solution as a whole requires lots of functionality Syncthing lacks - point in time snapshots and the ability to restore from them, for one.


(xor-gate) #43

Exactly, I use Syncthing to sync or push files to central places and backup with periodic cron jobs from there. Which IMHO is a robust and reproducable solution.


(Kluppy) #44

To call Syncthing backup software is missleading and incorrect… I removed it from the list. Notice Rsync wasn’t on the list either… My backup solution is based on Rsync but it isn’t backup software.


(Bob Hope) #45

I believe like this is a good idea:

So Syncthing is just bringing the data to the Backupsoftware, but has no part in the Backup itself.


Sync'ing to different destination folders
(xor-gate) #46

Yes this is the architecture I have implemented.


(Rasmus Kallas) #47

Any idea why my desktop displays a white window after multiple FULL reinstalls? Can’t get it to work :sob: my home isp requiers their router and you can’t foward, open or lease anything, i can’t foward any ports…


(Rasmus Kallas) #48

Right now the only things I’ve got to work have a central server with usually an account… Guess syncthing wasn’t meant for my isp…


(Kluppy) #49

The relay pool should look after this for you…

Is this with synctrazor? I think it has a log that can give you more details but I don’t use it so I can’t be much help…


(Hacker Zeus) #50

You guys might want to take a look at Veeam, just for the sake of comparison before going and re-inventing the wheel yet again.

It is kind of hard to justify putting all of the time and effort into an open source project when such well matured free alternatives exist, albeit closed-sourced, but nonetheless still excellent software.


Edited by calmh to remove links that look like spam, while retaining the messaging.

Dude, seriously? I’m not a spammer. Are you seriously censoring me from mentioning Veeam Free Backup?


(Jakob Borg) #51

No, I’m just removing multiple links from the first post of a user who joined to read just one topic and within minutes post a reply full of links. Welcome to the forum. :slight_smile:


(Simon) #52

I disagree - backup is one point where open source is not only nice to have, but very important to me (mostly for being future-proof). I do agree that there are already great backup solutions (open source) out there and don’t really understand the point of making Syncthing another one (obviously I see the point why it would be awesome if the same application could do both synchronization and backups, but that’s true for many things :slight_smile: ).


(jan fousek) #53

Well, based on experience with some the softwares that call themselves backup…syncthing is a rocking backup solution. Windows internal backup has its issues, even huge paid backup systems have their. So most of this thread is just a wordplay. Syncthing as it is with properly set versioning gives a cool intime backup option having its own drawbacks - easy acces to older versions being the biggest pain. While some of the drawbacks are very opinion based - should really the amount of used space be primary thing for backup? I preffer easy acces to the backed files just as they are in the filesystem - no need to run an app, navigate thru it and hope it can pull the required file from its superextracomplicated megafile.

I understand that developers dont want it to be called backup - every single glitch in stable would be a big problem, even a showstopper. Their target is different and possibility to use as a backup is resultfor the rest of us :slight_smile:


(Audrius Butkevicius) #54

There is a shitty ui for restore, which was proposed in the request and it made sense. If you have a better idea how to improve the UX, it would be interesting to hear.


(Bengalo Bongali) #55

So…? I know it can’t do that, but what would be bad about that?


(Jakob Borg) #56

When at least I say “restore” in a backup context I mean from a remote computer, after I’ve fried my local files in some way. No disrespect to the versioning restore UI, it’s just something orthogonal.


#57

Well, not 100%! In above diagram the error is the two way arrow between “Syncthing network” and “Local Server”. It should be a one way arrow, from the network to the local server, this is about making backups. Besides that, yes, that’s what I implemented as well. I have a couple of clients that syncthing onto one machine. The synced folders on this machine are then hardlink backed up every night via dirvish (rsync based). That works fantastically.

And yes, syncthing is no backup software, it need not be. But I do think it can well be a solid part of a backup strategy. And here IMHO what Rasmus is asking is indeed not going in the right direction. Unix always had a tradition of:

  • Creating small tools that serve precisely one job and do it well.
  • Make those tools so that they can easily be plugged and piped - building blocks.

So using syncthing to mirror files onto another machine and then having dirvish backing them up is no different from piping dmsg into grep on the command line. All those tool do one great job - precisely one job. Combining many jobs gives great power and flexibility. Leave it that way.

Those here that do prgramming know what “encapsulation” means in the OO context and they know the “single responsibility” paradigm. These are integral parts of building reliable software. It’s the same here, dmesg, grep, syncthing, dirvish, etc. - they all have a single responsibility and they do kind of encapsulating the task they are doing.

So, yes, you may add encryption to the folder where synthing is offloading files - but even that is not really its job. Why you want encryption here is for a different reason, it’s about storing sensitive data on untrusted servers and providers on the internet. This has nothing at all to do with backups and only very little with syncing files. So my idea would be to keep these things - syncing, backing up and untrusted storage - separate. Synthing should definitely not get any backup functionality, there are plenty of open source backup solutions out there that can be used with syncthing.


(Rasmus Kallas) #58

I already got it that syncing to one machine and backing it up is a good idea, just syncthing for some reason doesn’t like Inteno & Thompson(or thomson I don’t remember) (default modem/router what basically everyone in Estonia has) paired with Telia’s service (there are other isps, but noone really uses them)


(Bob Hope) #59

The “back” part of the arrow is just there, so you are able to bring back your backup to the Syncthing network if necessary.

So if you restore from your backup, you can just put it in the correct folder in the local server and everybody gets the restored files… otherwise it might be a pain to get the files back into the network.