スタック経路：Agency Siteground Plus Cloud Schedules

スタック経路：Agency Siteground Plus Cloud Schedules

This stack guide covers agency siteground plus cloud schedules as a concrete Multisite operations path. Combine hosting-class limits (PHP time/memory, cron, disk) with Multisite Migrate’s Jobs in Chunks and the correct destination: native Plus targets are Google Drive, Dropbox, S3-compatible storage, and SFTP.

Wasabi, Backblaze B2, Cloudflare R2, DigitalOcean Spaces, and MinIO are used through S3-compatible endpoints — not as separate proprietary vaults. Free keeps local schedules; Plus adds cloud schedules and upload; Pro adds remote import, empty-server installer, Staging, and network split/extract. For migrations between hosts, take a verified archive first, move with the matching restore path, then confirm URLs, media, and users on Staging before DNS cutover. Tier focus: Plus. Keep the previous host reachable until the new Staging drill passes twice, and document which Plus destination holds the rollback object so on-call staff are not hunting buckets during an outage.

ホスト制約と Jobs in Chunks

For agency siteground plus cloud schedules, prepare PHP limits, real cron where wp-cron is delayed, and free disk for Multisite-sized archives. Jobs in Chunks resume after interrupts so host timeouts do not force a full restart.

Exclude cache/tmp noise. Confirm Network Admin vs subsite scope before the first production schedule.

このスタックの保存先の事実

Connect Plus destinations you actually have: Google Drive, Dropbox, S3-compatible, or SFTP. Test the connection with a small job before relying on overnight schedules. OneDrive is not native. S3-compatible services share endpoint/credential patterns — label them clearly in ops docs.

Retention: keep enough generations for rollback. A stack named “Agency Siteground Plus Cloud Schedules” still fails if you only keep one corrupt overnight object.

移行とカットオーバー

Archive → transfer → restore → verify before DNS cutover. Use import, remote import, or empty-server flows as your tier allows. Staging is the place to catch HTTPS, mapping, and media issues — not the live cutover window.

If only media fails after cutover, inspect sites/ paths and CDN purge before rebuilding the whole DB archive.

保持・暗号化・サポート衛生

For agency siteground plus cloud schedules, 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.

運用者が見落としがちな関連判断

For agency siteground plus cloud schedules, decide schedule windows that avoid peak traffic, who owns Network Admin credentials, and how long local plus offsite copies are retained. Align Free local schedules with Plus cloud upload only after a Staging restore has passed.

Also record whether the job is full-network or include/exclude subsites. That single choice prevents most “backup succeeded but site missing” surprises after a restore drill.