BUbuhtz·Sep 3, 2026Submission
Show HN: 2nd Release Canddiate for Back in Time 2.0.0
1 points · Open discussionbit-team
backintime
Python2019–2026
bit-team / backintime
backintime
A comfortable and well-configurable graphical Frontend for incremental backups, with a command-line version also available. Modified files are transferred, while unchanged files are linked to the new folder using rsync's hard link feature, saving storage space. Restoring is straightforward via file manager, command line or Back In Time itself.
3Distinct people
12Mentions
0Explicit recommenders
2.7KGitHub stars
What to know before exploring
What it is
A comfortable and well-configurable graphical Frontend for incremental backups, with a command-line version also available. Modified files are transferred, while unchanged files are linked to the new folder using rsync's hard link feature, saving storage space. Restoring is straightforward via file manager, command line or Back In Time itself.
GitHub
Where it is used
No documented product use has been verified yet.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:03:16 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year12 dated mentions
Observed mentions: 2019-06-12 11:08:37 UTC to 2026-09-03 06:29:41 UTC.
* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2019 | 2019-01-01 00:00:00 UTC | 2020-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2020 | 2020-01-01 00:00:00 UTC | 2021-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2021 | 2021-01-01 00:00:00 UTC | 2022-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2022 | 2022-01-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2023 | 2023-01-01 00:00:00 UTC | 2024-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2024 | 2024-01-01 00:00:00 UTC | 2025-01-01 00:00:00 UTC | 5 | 3 | 2 |
| 2025 | 2025-01-01 00:00:00 UTC | 2026-01-01 00:00:00 UTC | 3 | 2 | 1 |
| 2026 (partial) | 2026-01-01 00:00:00 UTC | 2027-01-01 00:00:00 UTC | 2 | 2 | 0 |
What Hacker News says
12 sourcesShow HN: Back In Time 2.0.0 – Release Candidate 1
7 points · Open discussionFaroese, Croatian, Slovenian and Vietnamese might be removed from GUI
1 points · Open discussionPlease allow me to announce the second release candidate preparing for version 1.5.4 targeting the upcoming Debian 13 Trixie.
https://github.com/bit-team/backintime/releases/tag/v1.5.4-r...
Please report if you use it even if there are no new problems.
- EncFS, used for encrypted profiles, has been marked as deprecated and is schedule for removal in 2026.
- The Smart & Auto remove GUI has been reorganized and renamed into "Remove & Retention", with improvements to the user manual section. Its behavior remains unchange.
- An offset minute can now be configured for hourly schedule options.
- Some config file fields have been moved to a newly introduced state file.
- License and copyright information is now provided in machine-readable SPDX format, following the REUSE standard.
- See CHANGELOG for more details.
In Back in Time – Second Release Candidate (1.5.4-Rc2)Back In Time [1] 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. Have a look at Good First Issues [2]
or Help Wanted Issues [3].
[1] -- <https://github.com/bit-team/backintime>
[2] -- <https://github.com/bit-team/backintime/labels/GOOD%20FIRST%2...>
[3] -- <https://github.com/bit-team/backintime/labels/HELP-WANTED>
In Ask HN: What open source projects need help?Back In Time release version 1.5.3
1 points · Open discussionRelease Candidate for Back in Time 1.5.3
1 points · Open discussionPlease allow me to announce a new Release Candidate in preparation for the Back In Time release version 1.5.3. Please report back if you use it, even if no issues are found. Details: https://github.com/bit-team/backintime/releases/tag/v1.5.3-r...
Changes:
- Extensive code refactoring.
- Added support for FCron.
- Improved text labels in the graphical interface.
- User manual updated.
- Serbian language now available in both Latin and Cyrillic scripts.
- New language: Interlingua (Occidental).
- Minimum supported Python version raised to 3.9.
- Removed dependency on libnotify-bin; now using DBus for notifications.
We encourage everyone to test this Release Candidate, as it helps ensure a higher-quality final release. Without testing and feedback, creating an Release Candidate would be pointless. Your input is essential to improving the pro
Read the rest
ject!
Thank you very much for support!
Indeed they only test on Python3: https://github.com/bit-team/backintime/blob/master/.travis.y...
In Cronopete – A Linux clone of Time MachineOr backintime (https://github.com/bit-team/backintime).
The only thing I am missing is that it doesn't work for sshfs mounted devices. Which is not provided by any alternative tool which supports snapshots (probably because of problems with hard links, although I never had issues with those over sshfs).
In Time Machine style backup with rsync in 540 lines of code