Could not open Zip Archive during backup restoring
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 272
- Forks
- 37
- PR merge metrics
- No merged PRs in 30d
Description
Hi,
when trying to restore a full backup from scratch from my workstation, the chunks of the found data packs cannot be extracted, giving the error message: "Could not open Zip Archive (21)" . I'm using Nextcloud Hub 3 (25.0.4) with the Backup app version 1.2.0 .
Has anybody had a similar issue? Any ideas how to tackle it? Thank you very much!
Here is part of the terminal output:
./occ backup:point:restore 20230312070011-full-NwFg1nXomSbt1CG
Restoring Point: 20230312070011-full-NwFg1nXomSbt1CG
Date: 2023-03-12 07:00:11
Checking Health status: ok
WARNING! You are about to initiate the complete restoration of your instance!
All data generated since the creation of the selected backup will be lost...
Your instance will come back to a previous state from 3 hours, 0 minutes and 27 seconds ago.
Do you really want to continue this operation ? (y/N) y
> Enabling maintenance mode
> Restoring 20230312070011-full-NwFg1nXomSbt1CG
> Found data pack: data
> will be extracted in /home/user/nextclouddata/
- enter a new absolute path, or type yes to confirm this location or no to ignore this part of the backup: yes
> extracting data to /home/user/nextclouddata/
> Chunk: data-ee317c64-365a-4684-a137-ef08855dfafa.zip (11551 files) Could not open Zip Archive (21)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the occ backup:point:restore command and the data-pack extraction step shown in the terminal output, using the listed backup point if it is still available. Trace why data-ee317c64-365a-4684-a137-ef08855dfafa.zip cannot be opened, then verify that the full backup restores its data chunks 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
- 25/100