nextcloud / nextcloud/backup

Restoring point not complete

Open
#133 2 comments 0 reactions 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

Hi

What can I do when a restoring point is "not complete" on the external storage?

The output of :details says:

Data: apps-apps-56437402
Type: 1
Absolute Path: /var/www/html/apps/
+---------------------------------------------------------+-----------+-------+-----------------------+----------------------------------+-------------+----------+
| Chunk Id                                                | Size      | Count | Part Id               | Checksum                         | Algorithm   |          |
+---------------------------------------------------------+-----------+-------+-----------------------+----------------------------------+-------------+----------+
| apps-apps-56437402-5acf26bb-022b-4d2c-b9ee-b59eb5f5723a | 245.79 MB | 10237 | 00001-C5AsAtxsfprinMN | d69c6b2a37655cf3f6adba320f558029 | aes-256-cbc | checksum |
+---------------------------------------------------------+-----------+-------+-----------------------+----------------------------------+-------------+----------+

Data: apps-custom_apps-256b7c54
Type: 1
Absolute Path: /var/www/html/custom_apps/
+----------------------------------------------------------------+-----------+-------+-----------------------+----------------------------------+-------------+---------+
| Chunk Id                                                       | Size      | Count | Part Id               | Checksum                         | Algorithm   |         |
+----------------------------------------------------------------+-----------+-------+-----------------------+----------------------------------+-------------+---------+
| apps-custom_apps-256b7c54-08387988-e2bd-47f7-af9b-7ad880470caf | 255.69 MB | 8739  | 00001-IBpvl2pyyLrN6os | c31026ed7366f0232158bd3a49fd119f | aes-256-cbc | missing |
+----------------------------------------------------------------+-----------+-------+-----------------------+----------------------------------+-------------+---------+

Data: internal
Type: internal
Absolute Path: /
+-------------+--------+-------+-------------+----------------------------------+-----------+---------+
| Chunk Id    | Size   | Count | Part Id     | Checksum                         | Algorithm |         |
+-------------+--------+-------+-------------+----------------------------------+-----------+---------+
| app.zip     | 0.00 B | 0     | app.zip     | 7d2b0a4c918c6a4bf136e01bd68d6a67 |           | missing |
| restore.php | 0.00 B | 0     | restore.php | 923980dab732add2807e8e1e9dd5701c |           | missing |
+-------------+--------+-------+-------------+----------------------------------+-----------+---------+

Data: sqldump
Type: 1001
Absolute Path: /
+----------------------------------------------+----------+-------+-----------------------+----------------------------------+-------------+---------+
| Chunk Id                                     | Size     | Count | Part Id               | Checksum                         | Algorithm   |         |
+----------------------------------------------+----------+-------+-----------------------+----------------------------------+-------------+---------+
| sqldump-32581215-b4d9-436d-86d6-79059e0d82bd | 77.49 MB | 1     | 00001-KdGfilh9OHplmY9 | dcbe5819be7d1bef88ad01b4b58957eb | aes-256-cbc | missing |
+----------------------------------------------+----------+-------+-----------------------+----------------------------------+-------------+---------+

Status of the restoring point  at 10:nextcloud_backup: not complete

This is the case on nearly all restoring points made until now.

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

Use the reported :details output as the starting case, focusing on the entries marked “missing” and the final “not complete” status. Trace how the backup status is determined and compare it with the displayed restoring-point data; done means identifying the cause and documenting or implementing the appropriate recovery behavior.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.