Borg Backup Config went missing

[theOne-Q]

c

Steps to reproduce

1. use NC 26
2. click create Backup in AIO
3. observe Error

Expected behavior

start creating a Backup

Actual behavior

abort Backup

Host OS

Fedora Server with Docker AIO succesfully installed

Nextcloud AIO version

beta 6.2.0

Current channel

beta

Other valuable info

"
Performing backup...
Did not find borg.config file in the mastercontainer volume.
Cannot create a backup as this is wrong.
"

[szaimen]

Hi, I am not completely sure how the file got missing on your system as I cannot reproduce this. Did you maybe delete the file at some point manually? I also did another look at the logic and could not find a way that could lead to this.

Anyway, you should be able to fix this by copying the config file from the borg backup directory into /var/lib/docker/volumes/nextcloud_aio_mastercontainer/_data/data/borg.config

[theOne-Q]

Thank you, but i cant find that config file...where am i supposed to find it ? i cant find it in the Github files.
Also i never manually deleted it....I truly never touched the containers or volumes

[theOne-Q]

alright thank you sir.
you saved my evening :)

[theOne-Q]

I`ll report if it worked

[theOne-Q]

it now gets past the error of not finding the file but now it has issues with the keys :

Performing backup...
Starting the backup...
passphrase supplied in BORG_PASSPHRASE, by BORG_PASSCOMMAND or via BORG_PASSPHRASE_FD is incorrect.
Deleting the failed backup archive...
passphrase supplied in BORG_PASSPHRASE, by BORG_PASSCOMMAND or via BORG_PASSPHRASE_FD is incorrect.
Backup failed!
You might want to check the backup integrity via the AIO interface.

I am now running the Backup integrity check from AIO

Edit: this may take a while

[szaimen]

Interesting! I think I know what happened. You apparently in the past already created a backup with an old aio instance in /mnt/speicher_backup/newBackup. Then you created a new AIO instance and chose /mnt/speicher_backup/newBackup as backup target as well. Now the script runs into this problem because this is not expected.

[szaimen]

To proof that, can you post the output of the following command?

grep 'id =' /var/lib/docker/volumes/nextcloud_aio_mastercontainer/_data/data/borg.config
grep 'id =' /mnt/speicher_backup/newBackup/borg/config

[theOne-Q]

id = 93fe17392b6fe0b5f838dcf7e59b52a169f849f808282ae0b221ad3193f074a4
id = 93fe17392b6fe0b5f838dcf7e59b52a169f849f808282ae0b221ad3193f074a4

[szaimen]

Ah sorry, that of course would be the same as we just copied it 🙈

[theOne-Q]

but your right regardles...I did exactly what you described

[Gabemedina23]

I am an idiot... I had external storage and mistakenly set the backup to local storage that wasn't large enough to handle the entire nextcloud instance so when I went to change the backup location it said it couldn't write to the config due to lack of storage. In my mind that was as simple as deleting the '/mnt/backup/data folder' when I went to change it after this point it saved the changes to the config... well some time later i forget the steps that got me to this terrible place it said could not find the borg.config file. So I found this and a couple of other threads and somehow while running backup, the log states this:

2024-11-07T22:00:18.530286197Z Performing backup...
2024-11-07T22:00:18.530339666Z Starting the backup...
2024-11-07T22:00:18.998125223Z Creating archive at "/mnt/borgbackup/borg::20241107_220018-nextcloud-aio"

and hangs

before I brick anything else, and without a backup, how do I restore AIO/borg so that I can start my server up again?

Edit: NextCloud doesn't start anymore, but I did find another borg backup and deleted it, the backup is running now, will update when it's finished

[NEVARLeVrai]

i dont have my borg config anymore how to restore ???