Przejdź do treści

Rozwiązywanie problemów

Napraw: Fix Network Split Archive Incomplete

Przyczyny i naprawy dla „Network Split Archive Incomplete“ w backupach Multisite.

Pro

Naprawa: Fix Network Split Archive Incomplete

When you hit network split archive incomplete, start with the Multisite Migrate job log: last completed chunk, PHP/memory messages, HTTP 502/504, disk/inode errors, or cloud auth failures. Multisite archives are larger and table-heavier than single-site jobs, so shared hosts interrupt long PHP requests — Jobs in Chunks exist specifically for that.

Check tmp/disk free space, upload_max_filesize for imports, S3/Drive/Dropbox/SFTP credentials for Plus uploads, and security plugins that block admin-ajax. After restore issues, verify siteurl/home, rewrite rules, domain mapping (sunrise.php), object-cache drop-ins, and CDN caches. Reproduce once on Staging before changing production limits.

Diagnoza od logu dla „Network Split Archive Incomplete”

Separate backup failures from post-restore URL/media/login problems. Capture job percent, last log line, HTTP status, hosting class, and whether a local archive already exists. That evidence decides whether you raise PHP limits, free disk, fix cloud auth, or only re-upload.

For “network split archive incomplete”, avoid restarting from scratch if a chunked job can resume. Lost locks, cleared tmp, or a new job ID are common reasons a progress bar jumps back to 0%.

Poprawki zgodne z Multisite

Raise PHP time/memory enough for safety, but keep chunked jobs — shared hosts can still kill long workers. Free disk and inodes before large network archives. Allow admin-ajax through WAF or security plugins. On Plus, re-test Drive/Dropbox/S3-compatible/SFTP credentials and quotas.

Free handles core backup/restore; Plus covers BYO cloud; Pro covers remote import, empty-server installer, Staging, and split/extract. Pick the tool that matches the failure — do not upgrade tiers hoping a cloud auth typo will disappear.

Gdy archiwum już gotowe

If the local archive is good, you can restore even when cloud upload failed. Fix destination auth/quota, then re-upload, or restore from local. On Staging, confirm HTTPS, mapping, media, and logins before production.

If mid-restore failed, do not “fix” production DNS first — finish Staging validation and confirm table/prefix expectations.

Retencja, szyfrowanie i higiena supportu

For fix network split archive incomplete, keep enough archive generations to roll back a bad deploy or failed migration. Optional .venc AES-256 encryption on Multisite Migrate archives protects copies at rest when you store offsite on Plus destinations. Document credentials, schedule windows, and who may run Network Admin jobs.

When opening a support ticket, include the last job log lines, hosting class, PHP limits, free disk, and whether a local archive already exists.

Dlaczego to ważne

Diagnoza od logów

Ustal, czy awaria to PHP, dysk, DB, chmura czy rewrite URL.

Jobs in chunks jako domyślna naprawa

Wznów zamiast restartować ogromne joby Multisite od zera.

Kontrole po restore

Oddziel awarie backupu od problemów URL/mediów/logowania po restore.

Dowody gotowe dla supportu

Wiedzieć, które linie logów i fakty środowiska zebrać dla wsparcia.

Kroki

  1. 1Uchwyć punkt awarii

    Wykonaj ten krok w Network Admin lub na subsite i sprawdź na Staging.

  2. 2Zastosuj właściwą naprawę

    Wykonaj ten krok w Network Admin lub na subsite i sprawdź na Staging.

  3. 3Uruchom ponownie w chunks

    Wykonaj ten krok w Network Admin lub na subsite i sprawdź na Staging.

  4. 4Confirm local archive integrity (zlokalizowane)

    Wykonaj ten krok w Network Admin lub na subsite i sprawdź na Staging.

  5. 5Zweryfikuj ścieżkę restore

    Wykonaj ten krok w Network Admin lub na subsite i sprawdź na Staging.

Częste pytania

Krótkie odpowiedzi o tym temacie Multisite. Nadal problem? Otwórz docs lub kontakt ze wsparciem.

Pytanie: Should I raise PHP limits forever?

Odpowiedź Multisite Migrate: Free/Plus/Pro, joby w chunkach, chmura BYO i drill restore na Staging.

Pytanie: Why did the job restart at 0%?

Zwykle utracony lock, wyczyszczone tmp lub nowe ID joba. Sprawdź locki i dysk przed ponownym uruchomieniem.

Pytanie: Cloud upload failed but local archive exists?

Napraw auth/quota celu i wyślij ponownie — albo przywróć z lokalnego archiwum.

Pytanie: Is “network split archive incomplete” usually backup or restore?

Odpowiedź Multisite Migrate: Free/Plus/Pro, joby w chunkach, chmura BYO i drill restore na Staging.

14-dniowy zwrot pieniędzy w Plus i Pro

Przeczytaj przewodnik restore →