Backup stuck in first pass

[dodedodo]

I've tried to make a backup by setting both app_data and restoring points to the same external storage (sftp), both in sub-folders. I don't have enough free disk space to duplicate all the data locally.

I ran a manual full-backup through the web UI first and waited about 15 minutes for some data to appear on the remote server. It never got past 2.8MB so I assumed the process failed. These are the files and folders that got created remotely.

20211207233004-full-rVdbX4adce6TfYy/
├── app.zip
├── data
│   └── data-17a75f77-d188-450a-aac5-0e3fd8790954
└── restore.php

I tried again this time by running occ backup:point:create and letting it run mostly unattended for roughly 2 hours. The same folder structure got created with again no data. I noticed the docker container ran out of space and the occ command was consuming 100% of a single cpu core. Occ was not consuming much cpu at the start of the process, I don't know when this started.

I was unable to log into the docker container so I could not inspect the offending files. I know it must have been outside /var/www/html because that's mounted to another filesystem. After recreating the container (flushing docker overlayfs), about 10,6GB of space was returned.

This is the output from occ:

www-data@c734ca92f6b1:~/html$ php occ backup:point:create
> maintenance mode: on
> initialization of the AppData
> initialization of the RestoringPoint: 20211207234018-full-ocppBxgNN8fWWvH based on NC23.0.0.10
> initialization of the storage
> preparation of the data to be stored in the restoring point
> preparation of internal data
> creating chunks
  * data: /var/www/html/data/, 58019 files

Maybe backup choked on the number of files?

I'm running nc v23.0.0 with backup app v1.0.0 through the official docker image with MySQL(mariadb v10.7) as database.

I may try again soon to see if I can get some more info on that disk usage thing.

[ArtificialOwl]

Do you have anything in nextcloud.log ?
Do you have at least a folder created within the external storage you assigned as appdata ?
Can you access the external storag assigned as appdata from the Files App ?

[dodedodo]

I forgot to mention, there were no errors in nextcloud.log for both runs.
I can access and upload stuff on the external storage through nextcloud, and there was some data created (app.zip, restore.php and an empty data-dir). Please refer to the file list in the opening post.

[ph00lt0]

I am having the same issue, but for me it doesn't list the amount of files and directory. I just get:

> maintenance mode: on
> initialization of the AppData
> initialization of the RestoringPoint: 20220327153627-full-OCdD7uwbSs1CRQY based on NC23.0.2.1
> initialization of the storage
> preparation of the data to be stored in the restoring point
> preparation of internal data
> creating chunks
  * data: 

Using backup version 1.0.6

[major-mayer]

Same problem here as you @ph00lt0.
Have you eventually found a solution for this problem?

[major-mayer]

I've just checked the app directory of the backup app and it indeed created a new directory for the backup.
But this folder contained only an app.zip file (with the contents of the backup app itself) and a restore.php file.
I found nothing in the nextcloud.log file regarding this app.

[ph00lt0]

No this issue has not been resolved. Generally this backup app is very unstable and often not compatible with the latest version of Nextcloud. I would discourage anyone from using it as for now.
Personally I use a cronjob to run a small script putting nextcloud in maintenance and after running borg backup to another server.

[thiswillbeyourgithub]

No this issue has not been resolved. Generally this backup app is very unstable and often not compatible with the latest version of Nextcloud. I would discourage anyone from using it as for now. Personally I use a cronjob to run a small script putting nextcloud in maintenance and after running borg backup to another server.

Same conclusion here in may 2024, the backup app kept getting stuck and leaving my server in maintenance mode