nextcloud / nextcloud/backup

Backup Point Loses Integrity Status when Replicated to External Storage

Open
#166 4 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

I've been trying to troubleshoot some strange behaviors I've been seeing with the backup app. (e.g. #163, #114). I completely reset the backup app yesterday and started over with a full. My AppData location is within my NextCloud primary filesystem location - /data/nextcloud. I have an External Storage location defined as /data/nextcloud-backups/restore-points.

Yesterday I manually kicked off a full backup which completed successfully with a green checkbox and state of "unpacked". I then packed it manually and it maintained a green checkbox. Overnight, the logic that replicates it to the external storage happened as expected. When the replication was complete and I checked this morning, the backup status now has a issue of "cannot confirm integrity". I ran a backup:point:details on both the local and the external copy of the point and both verified fine. I've done nothing else manually to the backups.

I think this is different than #114.

1

2

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 by reproducing the reported flow: create a full backup, pack it, replicate it to the external storage location, and compare the local and replicated integrity status. Use backup:point:details on both copies, as described in the issue, and trace why replication changes the app's status to "cannot confirm integrity" despite both copies verifying successfully. Done means replicated points retain a confirmed integrity status.

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
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.