linux-timemachine
Back In Time
linux-timemachine | Back In Time | |
---|---|---|
11 | 38 | |
752 | 1,848 | |
- | 1.4% | |
0.0 | 8.9 | |
7 months ago | 2 days ago | |
Shell | Python | |
MIT License | GNU General Public License v3.0 only |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
linux-timemachine
-
Ask HN: What compression doesn't re-include the same file multiple times?
> I am concerned about the longevity of my archives
If you're concerned about archival longevity, and I for one certainly are, then maybe consider not to compress at all. Both compression and encryption add to obscurity and loss of redundancy in the backup. Using a widely understood file system and a very obvious arrangement of the data (for me that means: directories with dates, below a tree of files that mimics their original locations) will be a huge plus should the data have to be recovered at some point in the future.
Personally I am using a slightly adapted version of https://github.com/cytopia/linux-timemachine for this task. You do get de-duplication for the file transfer, but each file is written as it was on the target. You'll get a timestamped directory for each time a backup was run. Like MacOS' timemachine, the script uses hard links to de-duplicate identical files across different timestamped directories so the overall space requirement for that incremental backup you did an hour or a day later can be very small.
I can certify that this setup, while it does not occupy the least conceivable amount of storage area, is very amenable to be searched and trivial to use for recovery. much better in this regard than any kind of compressed archive format which are always a pain in terms of searchability and so on.
- What's the simplest way to take a snapshot of your server
-
Good data backups?
And for file version history and to protect against accidental deletion i use linux-timemachine which backs up over SSH to the same server and keeps versioned incremental backups. This backup also includes my entire /home folder so all apps, appdata and config is contained here.
-
What is your favourite Linux backup software and why?
Linux-TimeMachine: https://github.com/cytopia/linux-timemachine
-
Best practices for backups
If you only want to backup specific folders i like the tool linux-timemachine which uses rsync and hardlinks to create incremental backups based on a input and output folder.
-
Tumbleweed without btrfs/snapper?
You know, another option might be to just rely on something external to your machine if you're worried enough. When I'm dealing with personal machines (usually servers) that are important to me, I usually use Backblaze B2. You could maybe even try using open source variants of Time Machine designed for Linux machines or Borg Backup...though, to be fair, I've never really tried using them for backing up my entire system ( "/" ) partition (https://github.com/cytopia/linux-timemachine).
- cytopia/linux-timemachine - Rsync-based OSX-like time machine for Linux, MacOS and BSD for atomic and resumable local and remote backups
- rsync based linux timemachine clone - now with full remote support
-
Rsync-based OSX-like time machine for Linux, MacOS and BSD for atomic and resumable local and remote backups
linux-timemachine
Back In Time
-
Opportunity for beginners: Some code cleaning in "Back In Time"
it is often asked by beginners how and where starting to contribute. As member of the maintenance team of Back In Time (Backup software using rsync in the back, written with Python and Qt) I would like to introduce one of our "good first issues" (#1578).
-
Free software project "Back In Time" requests for translation
I'm member of the upstream maintenance team of Back In Time a rsync-based backup software. No one gets payed. No company behind hit. Even the maintainers and developers are volunteers.
-
Why is contributing soo hard
Back In Time is a round about 15 years old backup software using rsync in the back. I'm part of the 3rd generation maintenance team there. A lot of work in investigating and fixing issues, understanding, documenting and refactoring old code.
-
[English -> Portuguese EU / Brazil] Text about attracting translators to a FOSS project
This request is related to an Open Source project named Back In Time. Everyone there works voluntarily and unpaid.
-
Is it normal practice in Github for a valid issue to be closed if the Dev can't work on it at the moment?
In my own project we do it more transparent. We close if there is a good reason for it. We don't close just because no one is working on something. If there are no resources to work in it now but it seems important we keep it open until it is fixed. We do use milestones and priority labels to give the users an idea about our plans.
-
Free Software project "Back In Time" requests for translators
I'm member of the maintenance team of Back In Time a rsync-based backup software.
Most of the strings are form two past developers (the founder and the past maintainer). Since last summer we took over the project and try to clean things up. Some of the source strings just got a review from a linguist and he also mentioned about that exclamation marks. But he kind of stopped at some point because it was to much. ;)
Currently the translation is locked because of maintenance issues and an open PR offering review of original English strings.
Great and thanks. Feel free to ask further questions in the Issues section of our project or the bit-dev.python.org mailing list. Of course you can contact me directly here.
-
Date of "069 17 - 'Back In Time' Backup Software for Linux"
I'm interested in that topic because I'm member of the maintenance team of Back In Time, the software discussed in that video. The version in video is 0.9, today Back In Time reached 1.3.3. Also interesting is that I'm the third generation of maintainers to that project. I'm not sure but 0.9 there was the fist maintainer and founder involved only.
What are some alternatives?
BorgBackup - Deduplicating archiver with compression and authenticated encryption.
TimeShift - System restore tool for Linux. Creates filesystem snapshots using rsync+hardlinks, or BTRFS snapshots. Supports scheduled snapshots, multiple backup levels, and exclude filters. Snapshots can be restored while system is running or from Live CD/USB.
docker-pihole-sync - A Docker Container To Sync Two Piholes
Rsnapshot - a tool for backing up your data using rsync (if you want to get help, use https://lists.sourceforge.net/lists/listinfo/rsnapshot-discuss)
snapper - Manage filesystem snapshots and allow undo of system modifications
Duplicati - Store securely encrypted backups in the cloud!
restic - Fast, secure, efficient backup program
snapper-gui - GUI for snapper, a tool for Linux filesystem snapshot management, works with btrfs, ext4 and thin-provisioned LVM volumes
rsync-time-backup - Time Machine style backup with rsync.