What type of hardware are you using: VPS bought online
What YunoHost version are you running: 12.1.15.1
How are you able to access your server: The webadmin
SSH
Describe your issue
So my productive server recently crashed. I have a somewhat recent backup of the entire yunohost instance which was created using the CLI via SSH, backing up everything from user settings to apps to databases to about 420GBs of Nextcloud data.
That backup.tar of about 460GB was written to a remote storage mounted to the old server - in this case, a Hetzner Storage Box.
So I did what I thought was the logical choice: I spun up a new server, remote-mounted the storage box into /home/yunohost.back/archives/Hetzner in order to circumvent possible “wrong location” hiccups and started the restore process using the CLI.
Two hours later the process failed due to “not enough space”.
I then symlinked the .tar from the remote drive to /home/yunohost.backups/ and started the process again.
Two hours later, it failed due to “not enough space”.
However, in the meantime, about 155GB have been written to /dev/vda1, leaving about 592GB available on that disk.
So, in theory, this means
- there’s de facto enoug space
- the process starts, but then interrupts itself at some point, writing data to disk until then
- I need to figure out another way of doing this.
Is it possible to only partially restore a full_system_backup.tar? This would enable me to go app by app, thereby hopefully circumventing whatever weird troubles the restore process encounters. How would I go about that?
NB: I could also start the restore process from the webadmin … but ever since I put the symlink to the remote Hetzner backup.tar in the yunohost.backups folder, the webadmin backup function just loads and loads and loads forever, never actually displaying any files or anything at all really.
Edited to add:
sudo yunohost backup restore /home/yunohost.backup/archives/hetzner_mount/backups/20250812-153523.tar --apps linkwarden --debug
returns
35 DEBUG acquiring lock...
45 DEBUG lock has been acquired
82 DEBUG loading python module yunohost.backup took 0.037s
82 DEBUG processing action 'yunohost.backup.restore'
83 INFO Preparing archive for restoration…
84 DEBUG action executed in 0.001s
84 DEBUG lock has been released
Traceback (most recent call last):
File "/usr/bin/yunohost", line 108, in <module>
main()
File "/usr/bin/yunohost", line 97, in main
yunohost.cli(
File "/usr/lib/python3/dist-packages/yunohost/__init__.py", line 59, in cli
ret = moulinette.cli(
^^^^^^^^^^^^^^^
File "/usr/lib/python3/dist-packages/moulinette/__init__.py", line 143, in cli
).run(args, output_as=output_as, timeout=timeout)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3/dist-packages/moulinette/interfaces/cli.py", line 530, in run
ret = self.actionsmap.process(args, timeout=timeout)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3/dist-packages/moulinette/actionsmap.py", line 580, in process
return func(**arguments)
^^^^^^^^^^^^^^^^^
File "/usr/lib/python3/dist-packages/yunohost/backup.py", line 2265, in backup_restore
restore_manager.mount()
File "/usr/lib/python3/dist-packages/yunohost/backup.py", line 1115, in mount
mkdir(self.work_dir, parents=True)
File "/usr/lib/python3/dist-packages/yunohost/utils/file_utils.py", line 280, in mkdir
raise Exception(f"Folder {path} already exists")
Exception: Folder /home/yunohost.backup/archives/hetzner_mount/backups/20250812-153523.tar already exists
timon@gedoens:~$
I don’t know what that means. Of course the folder already exists?!
Share relevant logs or error messages
from this discussion [SOLVED] BACKUP / RESTORE : How to restore a (too) huge backup? as I forgot to actually save the snippet before I terminated the screen session I used to execute the restore command