Borg backup failed

Mon serveur YunoHost

Matériel: Raspberry Pi à la maison / Brique Internet avec VPN
Version de YunoHost: 11.0.9.8 (stable).
J’ai accès à mon serveur : En SSH | Par la webadmin
Êtes-vous dans un contexte particulier ou avez-vous effectué des modifiiations particulières sur votre instance ? : non

Description du problème

Bonjour,

J’ai installé la dernière version de l’application Borg sur mon Pi suite à une migration impossible. Je restaure petit à petit mes applications et données depuis une sauvegarde faite avec Borg. J’ai fini de réinstaller mes sauvegardes faites avec l’application Borg (de Borgbase.com vers mon Pi) avec les commandes :

borg list ssh://xxxxxx@xxxxxx.repo.borgbase.com:22/~/repo

puis, par exemple pour restaurer Nextcloud :

borg export-tar ssh://xxxxxx@xxxxxx.repo.borgbase.com:22/~/repo::_auto_nextcloud-2022-08-14_02:36 /home/yunohost.backup/archives/nextcloud.tar.gz

J’ai ensuite tenté de reconfigurer l’application Borg de mon Yunohost pour faire des sauvegardes de ma nouvelle installation vers Borgbase.com.

Dans la page web de configuration de Borg j’ai :

Public key: ssh-ed25519 AAAAC3NzaCxxxxxxxxxxlloKVvFef9ZDmsenlK1M9fu9to1 root@arnauld.org

Frequency: Daily

Mail alert: always

Et ensuite la liste des applications à sauvegarder.

En cli j’ai ensuite fait :

sudo yunohost app setting borg on_calendar -v "*-*-* 2:00:00" Pour définir l’heure de la sauvegarde, 2 heures du matin.

Puis :

You also need to change the timer with the new oncalendar value:
nano /etc/systemd/system/borg.timer
And next :
systemctl daemon-reload

Mais la sauvegarde ne fonctionne pas. Je reçois un mèl à minuit (alors que la sauvegarde devrait commencer à deux heures du matin) spécifiant :

The backup miserably failed to backup system configurations.
The backup miserably failed to backup system data.
The backup miserably failed to backup borg application.
The backup miserably failed to backup freshrss application.
The backup miserably failed to backup h5ai application.
The backup miserably failed to backup hotspot application.
The backup miserably failed to backup jirafeau application.
The backup miserably failed to backup nextcloud application.
The backup miserably failed to backup redirect application.
The backup miserably failed to backup roundcube application.
The backup miserably failed to backup vpnclient application.
The backup miserably failed to backup wallabag2 application.

Si je prends les premières lignes dans le mèl reçu :

Création d’une archive de sauvegarde à partir des fichiers collectés …
L’archive contiendra environ 366.4KiB de données.
L’opération ‘Créer une archive de sauvegarde’ a échoué ! Pour obtenir de l’aide, merci de partager le
journal de l’opération en utilisant la commande ‘yunohost log share 20220821-220009-backup_create’

Voici donc le journal de l’opération de dessus ‘yunohost log share 20220821-220009-backup_create’ :

https://paste.yunohost.org/raw/ecefuqojef

Que faire ?

Merci de vos conseils.

Hello,

I installed the latest version of the Borg application on my Pi following an impossible migration. I gradually restore my applications and data from a backup made with Borg. I finished reinstalling my backups made with the borg application (from borgbase.com to my pi) with the commands:

borg list ssh: //xxxxxx@xxxxxx.repo.borgbase.com: 22/~/repo

Then, for example, to restore NextCloud:

borg export-tar ssh: //xxxxxx@xxxxxx.repo.borgbase.com: 22/~/repo: _auto_nextcloud-2022-08-14_02: 36 /home/yunohost.backup/archives/nextCloud.tar.gz

I then tried to reconfigure the Borg application of my Yunohost to make backups of my new installation to Borgbase.com.

In the Borg configuration web page I have:

Public Key: ssh-ed25519 AAAAC3NZACXXXXXXXXXXXXLKVFEF9ZDMSENLK1M9FU9TO1 root@arnauld.org

Frequency: Daily

Mail Alert: Always

And then the list of applications to be saved.

Via the cli I then entered:

sudo yunohost app setting borg on_calendar -v"*-*-*2:00:00 " To define the backup time, 2 am.

Then :

You also need to change the Timer with the new oncalendar value:
nano /etc/systemd/system/borg.timer
And Next:
systemctl daemon-reload

But backups do not work. I receive an e-mail at midnight (while the backup should start at two in the morning) specifying:

The Backup MISERABLY FAILED TO BACKUP SYSTEM Configurations.
The Backup MISERABLY FAILED TO BACKUP SYSTEM DATA.
The Backup MISERABLY FAILED TO BACKUP BORG Application.
The Backup MISERABLY FAILED TO BACKUP FRESHRSS Application.
The Backup MISERABLY FAILED TO BACKUP H5AI Application.
The Backup MISERABLY FAILED TO BACKUP Hotspot Application.
The Backup MISERABLY Failed to Backup Jirafeau Application.
The Backup MISERABLY Failed to Backup NextCloud Application.
The Backup MISERABLY Failed to Backup Redirect Application.
The Backup MISERABLY FAILED TO BACKUP RoundCube Application.
The Backup MISERABLY FAILED TO BackUP VPNClient Application.
The Backup MISERABLY FAILED TO BACKUP WALLABAG2 Application.

If I take the first lines in the e-mail I received:

Creation of a backup archive from collected files …
The archive will contain approximately 366.4kib of data.
The creation of a backup archive’ has failed! To get help, please share the
Operation log using the ‘yunohost log share 20220821-220009-backup_create’ command

Here is the log of the yunohost log share 20220821-220009-backup_create’ command above:

https://paste.yunohost.org/raw/ecefuqojef

What to do ?

Thank you for your advice.

The error seems to be that :

ssh://ivxtoba5@ivxtoba5.repo.borgbase.com/./repo
2022-08-22 00:00:31,807: WARNING - Remote: lalalalalala@lalalalalalala.repo.borgbase.com: Permission denied (publickey).
2022-08-22 00:00:31,848: WARNING - Connection closed by remote host. Is borg working on the server?

I know that when you set up a new borg client on the server, a public/private key is created, and the public key should be uploaded to borgbase for authentication.

It seems that there is an incoherence with the key.

1 Like

Thank you, I did a test and backups are working now.

1 Like

This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.