Ubuntu, server and client on the same machine

client
1

Hello

I have been using UrBackup for a long time, previously I had the server in an isolated RPI in which I made backups of windows clients and another RPI in which my home automation system was running.

I’ve recently modified my system to run everything I used to have at 2 RPI’s on a minipc, the minipc runs Ubuntu 20.04 and I have numerous containers running, including urbackup-server and urbackup-client.

The server works fine, the backups are made to an external usb drive and it allows me to backup windows clients without problems, but the local client installed in another container on the same machine does not work well, it returns an error when it is raised and it does not appear as connected to the server.

In one of the multiple tests that I have carried out, the most that I have achieved is that the server detects it as connected, but it gave an error when trying to make a file backup manually.

I would like to be able to have a server and a client on the same machine to be able to make backup copies of the configuration and databases of my home automation system without having to configure another machine for this, but no matter how hard I try, I am not able to achieve it.

My partial docker-compose of urbackup is as follows:

urbackup-server:
container_name: urbackup-server
image: uroni/urbackup-server:latest
restart: unless-stopped
environment:
  - PUID=1000
  - PGID=1000
  - TZ=Europe/Madrid
volumes:
  - /home/docker/urbackup/server/database:/var/urbackup
  - /home/docker/urbackup/server/www:/usr/share/urbackup
  - /media/Backups/Backups:/backups
network_mode: host

urbackup-client:
container_name: urbackup-client
image: uroni/urbackup-client:latest
environment:
  - URBACKUP_SERVER_NAME=192.168.1.10 # IP of the machine
  - URBACKUP_CLIENT_NAME=IOT-SYSTEM
  - URBACKUP_CLIENT_AUTHKEY=qvDtlj6rOl
volumes:
  - /home/docker/urbackup/client/backup:/backup

and the client log is this:

2022-03-30 20:38:24: SQLite: recovered 25 frames from WAL file /usr/local/var/urbackup/backup_client.db-wal code: 283
2022-03-30 20:38:24: ERROR: urbackupserver: Failed binding ipv6 socket to port 35623. Another instance of this application may already be active and bound to this port.
2022-03-30 20:38:24: urbackupserver: Server started up successfully!
2022-03-30 20:38:24: Started UrBackupClient Backend...
Backing up volume /backup
2022-03-30 20:38:25: Looking for old Sessions... 0 sessions
2022-03-30 20:38:25: Final path: /backup
2022-03-30 20:38:26: Socket has error: 111

Any help you can give me on this will be greatly appreciated, thanks in advance

[Translated by Google]

2

Does anyone have such a setup working?

3

Hi,

My setup consists of a Linux host and multiple clients (including itself) but was something that I set up 2+ years ago, so can’t remember exactly how I set the host/server to back itself up currently…but wanted to add that it very much is possible…

Am thinking that one [albeit possibly extreme] way would be to set the host’s client up as if it is an external machine, using the “long-winded” setup of using the manual configuration…but there may well be an easier/simpler method to get the host to back up to itself…

4

I have a Windows server backing itself up without issues… I can’t see why a Linux one would be more problematic… as long as you don’t include the backup storage in the backup it should be OK.

I can’t tell you if you get an endless runaway situation or an error if you do that… it seems pretty obvious it wouldn’t work to back the storage volume / folder up to itself.