backup
backup copied to clipboard
backup app - creates no further restoring points
Nextcloud version: 23.0.3 Backup App version: 1.0.6 Operating system and version: Debian 4.19.235-1 nginx version: 1.21.6 PHP version: 8.0.17
After configuring the app and exporting configuration and key, I initiated the first backup by pressing the button Create full restoring point. After two days the backup had still the status “not packed yet”.
So I assumed a problem and removed the whole folder by:
rm -fR 20220218090002-full-27uyPwv6nMPWU8M
This was probably not good.
The Restoring point is still shown under “Restoring points history” as "processing" / "not packed yet"
occ backup:point:list
shows
Now after pressing Create full restoring point again, it shows “The creation of a restoring point as been requested and will be initiated soon.” for a while. But after it is gone, no restoring point was created.
When I go to settings of the app, I get the message "Unable to fetch app data" for some seconds.
How can I analyse/repair the problem and start again with the backup app? The nextcloud.log shows no helpful information to me.
Thanks for your help
Hello! Have you been able to fix your issue? I'm experiencing exactly the same one (except I have not deleted the backup folder). After 2 weeks the backup is still marked as 'processing' and, on the webpage, the icon "not packed yet" is displayed. Thanks in advance.
No, unfortunately I have not. I do not use the app anymore. Best regards
Am 02.02.23 um 14:54 schrieb silaxe:
Hello! Have you been able to fix your issue? I'm experiencing exactly the same one (except I have not deleted the backup folder). After 2 weeks the backup is still marked as 'processing' and, on the webpage, the icon "not packed yet" is displayed. Thanks in advance.
— Reply to this email directly, view it on GitHub https://github.com/nextcloud/backup/issues/261#issuecomment-1413784638, or unsubscribe https://github.com/notifications/unsubscribe-auth/AW4KLQ7Q4OE7MI55UAFP6FDWVO4DDANCNFSM5S7B67FQ. You are receiving this because you authored the thread.Message ID: @.***>