Corriger : Fix Opcache Stale After Restore

Correctif pour Fix Opcache Stale After Restore

When you hit opcache stale after restore, 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.

Diagnostic journal d’abord pour « Opcache Stale After Restore »

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 “opcache stale after restore”, 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%.

Correctifs adaptés à 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.

Une fois l’archive terminée

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 the front end is stale after a good restore, flush rewrite rules, object cache drop-ins, and CDN — the archive may already be fine.

Rétention, chiffrement et hygiène support

For fix opcache stale after restore, 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.

Separate schedule failures from restore failures in your runbook so on-call staff do not rebuild a finished archive unnecessarily.

Section ops complémentaire 5

Pour « Fix Opcache Stale After Restore », gardez le périmètre Multisite, les jobs en chunks et une archive importable. Free = backup/restore de base + un planning local ; Plus = cloud BYO (Drive, Dropbox, S3-compatible, SFTP) ; Pro = remote import, empty-server, Staging, network split. Faites un exercice de restore sur Staging avant tout cutover DNS. Les snapshots hôte ne remplacent pas l’archive plugin. Tarif : Free.