Is management of Backup-Manager still active?
I like the tool very much, and want to use it on all mu servers, but I'm woried that there is no development since Sep 30, 2014. Is this repository still active? I've already got a patch almost ready and will create a pull request in a few hours
It seems like you mistyped the year. The last version I know of is 0.7.10.1 - back in the days when the original BM website did still exist. AFAIK the project has been relatively dead since then.
Though, we still use it on all our production servers with Debian Squeeze, Wheezy, Ubuntu Lucid, Precise. Then again, if I had to choose a backup software right now, I would probably choose another one.
On 17-09-14 06:52:46, larsen0815 wrote:
Though, we still use it on all our production servers with Debian Squeeze, Wheezy, Ubuntu Lucid, Precise. Then again, if I had to choose a backup software right now, I would probably choose another one.
Is there any good alternative you can suggest? :)
We still use BM, so no =)
Can we fork and continue development on some other repo?
I am no developer of BM. Forking is always possible.
You can fork it without any problem :) Sorry guys, I didn't have much time to maintain the repository, and I think I won't have enough anymore.
Thx for your work so far! @dobber: In case you fork, please also post here. I might have small patches to add.
I would also be interested in a fork and would like to add some patches.
it's enough mature to continue serving for the next 5 years, hopefuly :)
On 18-09-14 03:23:27, madhifallah wrote:
it's enough mature to continue serving for the next 5 years, hopefuly :)
Nope. The version in Debian fails with FTP/TLS due to some missing perl modules which were removed by Debian IIRC. I patched my version so that it works again. So it would be nice if anyone could fork BM and took care of its future ;)
Since I'm new to this comunity, I would trust more seniour guys to do this.
Anyone tried TKLBAM as an alternative ? -> https://github.com/turnkeylinux/tklbam/blob/master/docs/RelNotes-1.4.txt
@kbojens Can you create an issue for this problem?