nextcloud / nextcloud/backup

backup app - creates no further restoring points

Open
#261 2 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
PHP
Stars
272
Forks
37
PR merge metrics
No merged PRs in 30d

Description

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"
grafik

occ backup:point:list shows
grafik

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

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the Backup app's restoring-point history and the occ backup:point:list output, then reproduce a new restoring-point request while monitoring nextcloud.log. Investigate why the existing point remains “not packed yet” and why the settings page reports “Unable to fetch app data”; done means the stuck state is explained and a new restoring point can be created successfully.

Written by the indexing model from the issue text.

Assessment

Tech stack
php
Domain
backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.