|
1 |
| -What's the state of this project? |
2 |
| -################################# |
3 |
| - |
4 |
| -backy2 is an artefact of my hosting company where I recognized that there are |
5 |
| -no sane and reliable backup solutions out there for block-based / snapshot-based |
6 |
| -backup in the many-terabyte to petabyte range. |
7 |
| - |
8 |
| -backy2 was the second backup software I wrote for our usecases. The first one |
9 |
| -(you guessed rightm it was called "backy") was designed for .img based virtual |
10 |
| -machines and had designated features for that. |
11 |
| - |
12 |
| -backy2 was designed around our mostly ceph/rbd-based cluster, that's where the |
13 |
| -most features come from. |
14 |
| - |
15 |
| -Meanwhile we have switched to local lvm thin pools and we have a very clever, |
16 |
| -fast and new pull-backup solution, for which I (of course) wrote the third |
17 |
| -iteration of backup software, however it's neither called backy3, nor it's open |
18 |
| -source (for now). |
19 |
| - |
20 |
| -That's why this project receives only very minimal maintenance from me and practically |
21 |
| -no updates. This means you can expect to have installation issues due to |
22 |
| -non-existing libraries on modern operating system versions. However they should |
23 |
| -be rather easy to be fixed and in some regard I'm willing to do this. So there's |
24 |
| -no reason to panic if you're using backy2 in 2022 and plan to use it for the |
25 |
| -next years. The python code will most likely be valid in several years and libs |
26 |
| -have shown to be very compatible in never versions in the last years. |
27 |
| - |
28 |
| -The code however is stable (no guarantees though), the software is feature |
29 |
| -complete and that's the main reason why there have been no significant commits |
30 |
| -in the last months. We have performend many years of stable backups and restores |
31 |
| -with it. |
| 1 | +What's the state of this fork? |
| 2 | +############################## |
| 3 | + |
| 4 | +The upstream `backy2 <https://github.com/wamdam/backy2>`_ project is `on hiatus |
| 5 | +<https://github.com/wamdam/backy2#whats-the-state-of-this-project>`_. This |
| 6 | +fork exists to satisfy the needs of `Tiger Computing |
| 7 | +<https://www.tiger-computing.co.uk/>`_'s clients. |
32 | 8 |
|
33 | 9 |
|
34 | 10 | What is backy2?
|
|
0 commit comments