Sauvegarde WordPress Multisite sur Plesk WordPress Toolkit

Bien sauvegarder Multisite sur Plesk WordPress Toolkit

On Plesk WordPress Toolkit (panel hosting), a WordPress Multisite backup is more than copying wp-content. You need shared core files, network tables, per-site tables, and uploads under sites/ — or restore will miss users, settings, or media. Panel stacks (RunCloud/GridPane/Ploi/Forge/Plesk/cPanel) centralize PHP versions and cron.

Multisite Migrate runs chunked, resumable jobs from Network Admin (full network) or from a subsite dashboard when the role has manage_options. Free covers core network/subsite backup and restore plus one local schedule. Plus adds BYO cloud upload (Google Drive, Dropbox, S3-compatible, SFTP) and cloud schedules. Pro adds remote import, empty-server installer, Staging, WP-CLI, and network split. Confirm the site’s PHP binary matches the limits you expect for Multisite jobs.

Ce qu’une sauvegarde Multisite complète sur Plesk WordPress Toolkit doit inclure

Capture the network tables (wp_blogs, wp_site, wp_sitemeta, and related), each subsite’s tables, shared themes/plugins, and the sites/ upload tree. Skipping any of those on Plesk WordPress Toolkit creates “successful” archives that still fail a real restore drill. Exclude cache, tmp, and other regenerable noise so jobs finish faster on panel plans.

Use system cron for schedules when the panel offers it. Treat provider snapshots as an extra layer — not a Multisite-scoped import workflow. Keep a plugin archive you can move, import, and verify independently of the Plesk WordPress Toolkit control panel.

Comment Multisite Migrate exécute les jobs sur cette classe d’hôte

Shared and managed hosts often kill long PHP workers. Multisite Migrate therefore uses Jobs in Chunks that resume instead of restarting from zero after a timeout. On Plesk WordPress Toolkit, start from Network Admin for fleet backups, or from a single site when a subsite admin only needs their site. Watch the job log for the last completed chunk, disk/inode warnings, and cloud auth errors on Plus.

For schedules: Free keeps one local schedule; Plus can push finished archives to Drive, Dropbox, S3-compatible storage, or SFTP. Wasabi, Backblaze B2, Cloudflare R2, DigitalOcean Spaces, and MinIO are S3-compatible endpoints — not separate proprietary vaults. OneDrive is not a native destination.

Checklist de drill de restore pour Plesk WordPress Toolkit

Before you trust a Plesk WordPress Toolkit backup routine, restore once on Staging (or a throwaway site): check siteurl/home, HTTPS, domain mapping (sunrise.php if used), media under sites/, logins, and any WooCommerce or membership data. Confirm rewrite rules and purge CDN/object-cache drop-ins if the front end still shows stale content.

If import fails on Plesk WordPress Toolkit, raise upload_max_filesize and post_max_size only as far as needed, free disk, then retry with chunked resume.

Rétention, chiffrement et hygiène support

For wordpress multisite backup on plesk wordpress toolkit, 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.