stephdl
May 23, 2024, 6:42pm
1
Something new to play with: BackupPC v4
it is something reliable, smb and rsync are workable
what is workable
backup via rsync
to install it
add-module ghcr.io/stephdl/backuppc:1.0.0-dev.7
to be able to backup a linux host you need to send your backup rsa key to the linux host because we won’t ask the password fro the backup
runagent -m backuppc1 podman exec -ti backuppc-app su -s /bin/sh backuppc
ssh-copy-id -i ~backuppc/.ssh/id_rsa.pub root@192.168.1.10
when you have configured the email notification in the cluster you could test the mail notificationEMailFromUserName to set it accordingly to your mail address.
runagent -m backuppc1 podman exec backuppc-app su -s /bin/sh backuppc -c '/usr/local/BackupPC/bin/BackupPC_sendEmail -u foo@domain.com'
you have either a basic authentication or you could test the LDAP one
4 Likes
stephdl
May 23, 2024, 6:54pm
2
tests on smb protocol are welcome
2 Likes
stephdl
May 25, 2024, 8:41am
4
sometime dopamin of coding is better than adrenalin of mountain bike
my patch has been accepted
tiredofit:main ← stephdl:fix-data-dumper
opened 09:30AM - 24 May 24 UTC
let me try to explain why I want to patch this from upstream (the code is from t… he main developer but never released)
first with version of smbclient < 4.16 we have an issue that we cannot use the smbclient, see https://github.com/backuppc/backuppc/issues/404#issuecomment-1890776117
the version of samba 4 in alpine 3.16 breaks the smbclient tar backup, hence I got the idea to upgrade to 3.17/.3.18/3.19/3.20 but I faced a bug that the configuration is badly rewritten, this bug comes from directly from backuppc and it has been fixed by the main developer but never released, we are still using 4.4.0 since years now, see upstream https://github.com/backuppc/backuppc/issues/466
redhat itself faced this issue, you can read a bug report https://bugzilla.redhat.com/show_bug.cgi?id=2091514
[They fixed it ](https://bugzilla.redhat.com/show_bug.cgi?id=2091514#c5) by applying the patch
https://github.com/backuppc/backuppc/commit/2c9270b9b849b2c86ae6301dd722c97757bc9256.patch
you can see it in the srpm https://koji.fedoraproject.org/koji/rpminfo?rpmID=31776462
so my idea is to upgrade to a major version of alpine (> 3.16) and to patch the source of BackupPC to avoid the bug of configuration badly rewritten by Data::Dumper versions >= 2.182
4 Likes
stephdl
May 27, 2024, 9:47am
5
Package backuppc · GitHub released, we are close to release
1 Like
Apologies for my folly.
I’ve seen it uses SMB, does it meant its only menat to backup locally within the local premise environment, or would a local to cloud backup scenario work for windows as well.
i see for *nx systems rsync via ssh is used. supposed its only for local within premise backup.
does it mean that we can have a local backup server, backing up windows clients to it, then using rsync backup to the cloud on another NS8 box?
or generally how is backuo to cloud handled… been trying to understand it all.
stephdl
May 28, 2024, 6:18am
7
Backuppc is a software to backup client on the LAN but I suppose if the NS8 is behind a VPN it is the same
The purpose is to be agentless so you use rsync or smb
For window you could also use rsyncd but it is a service that it must be installed
You have a UI to manage the backup and the restoration with LDAP for selfservice of users
1 Like
stephdl
May 28, 2024, 1:37pm
8
version ghcr.io/stephdl/backuppc:1.0.0-dev.4 is available, now it is your turn to brings tests, everything is up to be merged, only tests are needed before to release to NethForge
stephdl
May 30, 2024, 1:32pm
9
the backup and restoration of NS8 is tested and validated with ghcr.io/stephdl/backuppc:1.0.0-dev.7
