To run one WordPress Multisite network on several servers, keep the application code and configuration identical, give every web node one authoritative database state, make all media files available through shared or deliberately replicated storage, and place consistent DNS, HTTPS, caching, and background-job controls in front of the nodes. A load balancer alone does not synchronize a network: independently writable databases or unsynchronised local upload folders can diverge and corrupt the experience for different sites.
Antihost offers managed WordPress hosting with free migration, one-click staging and a 14-day free trial.
What “synchronizing” a Multisite network actually means
WordPress Multisite is one coordinated application containing multiple sites. The WordPress Developer Resources Advanced Administration Handbook describes a network as sites that share one WordPress installation’s core files. Sites can also share plugins and themes, while each site keeps its own media-upload directory and database tables. That division defines what must be synchronized and what must remain logically separate.
As an Amazon Associate I earn from qualifying purchases.
Code and configuration
Every web node should run the same WordPress core version, plugins, themes, must-use plugins, PHP extensions, wp-config.php network constants, PHP settings, and web-server rewrite rules. Store custom code and configuration in version control. Promote one tested build rather than updating individual nodes by hand; a node with one extra plugin or a different rewrite rule is already a different application.
Database state
The network database contains network-level tables as well as tables for each site. A change to one subsite can involve options, users, relationships, scheduled events, and network metadata. Treat the database as one coordinated state store. Copying only a single site’s tables is not a safe method for cloning the whole network.
#1 Best Overall
- [Ultra-Lightweight Ear Buds Designed for Small Ears] Each earbud weighs only 3.7g and features a compact, ergonomic in-ear design made especially for small ears. Secure, low-profile, and comfortable for workouts, all-day wear or overnight sleeping.The ultra-slim profile sits flush in your ear with no hard edges poking or rubbing, so you can even sleep on your side without discomfort.
- [Immersive Stereo Sound with TOZO OrigX Technology] TOZO OrigX tuning delivers clear vocals, balanced mids, and natural stereo sound for music, podcasts, and videos.
- [Long Battery Life for Daily Use] Get up to 7 hours of playtime on a single charge, with up to 32 hours total using the charging case—ideal for workdays, commuting, and extended listening sessions.
- [Bluetooth 5.3 & Stable Connection] Bluetooth 5.3 provides fast pairing, stable wireless performance, and reduced dropouts as you move around home or office.
- [Deep Bass with Clear Vocals] High-performance drivers produce punchy bass while keeping vocals clean and detailed for everyday listening.
Uploads and generated files
Media files live in per-site directories inside the shared installation. Every node that can receive a request must be able to read files created by another node and write new files where required. Shared storage is the simplest model. Replication or object storage can work, but you must define delay, deletion, permissions, locking, and large-file behavior.
Runtime state
Page caches, object caches, cron locks, sessions, image derivatives, temporary files, and queue state are not automatically coordinated by Multisite. Decide where each item lives and how invalidation or locking works before sending traffic to more than one node.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Choose the topology before you copy anything
The correct synchronization design depends on the operational goal. A live, load-balanced network has different write and failover rules from a warm standby or a one-time migration.
| Topology | Database approach | Uploads approach | Main operational concern |
|---|---|---|---|
| Active traffic on multiple web nodes | One database service or a replication system with a clearly designated writer and tested failover | Shared storage or tested, conflict-aware replication accessible to every node | Prevent split-brain writes, stale reads, cache inconsistency, and duplicate background jobs |
| Warm standby | Primary database replicated to a passive target; promote only through a documented procedure | Continuous or scheduled replication with a measured recovery point | Keep the standby from accepting writes until promotion is complete |
| Staging or test mirror | Point-in-time database copy isolated from production | Restored copy of uploads, usually not writable by production users | Prevent test mail, webhooks, cron, and API calls from reaching production services |
| One-time migration | Full export and restore during a controlled cutover | Full copy, checksum-checked before DNS change | Freeze writes, apply only planned URL changes, and retain rollback access |
Compare candidate designs on consistency, upload semantics, recovery point and recovery time objectives, deployment effort, observability, network behavior, and total cost for database, storage, bandwidth, managed services, and staffing. A design that is inexpensive to build but difficult to restore is not operationally cheap.
Build identical application nodes
Create one reproducible build
- Record the exact WordPress version, PHP version, enabled extensions, web server, plugin versions, theme versions, must-use plugins, and network constants.
- Keep custom themes, plugins, mu-plugins, deployment scripts, and server rules in version control. Exclude secrets from the repository and inject them consistently at deploy time.
- Build a fresh node from the same release artifact. Do not “fix” one server manually after deployment; make the fix part of the artifact and redeploy.
- Verify file ownership and permissions for the web process, especially the per-site upload directories. The process must be able to write where WordPress expects uploads without making the entire installation world-writable.
Coordinate updates
Run plugin, theme, and core updates once through a controlled deployment process, then roll the same build to every node. During a rolling deployment, keep versions compatible with the database schema and avoid exposing a node that cannot understand data written by another version. Take a database and file backup before a network-wide update.
Use one authoritative database writer
All nodes must observe a consistent database state. Point them at one database service, or use database replication with explicit write ownership, lag monitoring, failover, and recovery procedures. Do not place two independent writable databases behind a load balancer and expect WordPress changes to reconcile safely. Simultaneous edits to options, users, posts, taxonomy relationships, scheduled events, and network tables can overwrite one another without a WordPress-level conflict resolver.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problemsRank #2
- 【IP68 Waterproof Multifunctinal Smart Watch】Torjalph fitness activity tracker smart watch is IP68 waterproof technology ,you can wear it when swimming,handwashing,it's rain-proof which means that you perform multiple exercise modes outside without worrying about sweat or rain corroding your fitness smart watch,and this watch equipped with a 230 mAh large capacity battery magnetic charging ,and this sports activity tracker watch can be used 5-7 days If fully charged.
- 【Larger 1.83'' Full Screen Watch & Multi-dial Selection】1.83 inch full HD color touch screen smart watch for men / women provides excellent 240*284 resolution image quality ,This Bluetooth smart watch offers a better touch experience and remarkable immersion and ,more than 200 watch faces for you to choose from App"Da Fit ", you can change the dial style according to your mood to wear keeping the world on your wrist
- 【Accurate Activity Tracker Smart Watch 】sports watch activity tracker uses sweat and dust resistant breathable silicone strap, our Fitness Tracker Smart Watch for Android iOS Phones supports 12 sports modes,walking,running,bicycle,swimming,badminton,basketball,football,rope skipping. This bluetooth calls smart watch for men women is lightweight and stylish, bringing more convenient and relaxing sports experience while also providing more protection.
- 【Your 24 Hour Personal Daily Health Monitor】Fitness watch for women men full touch screen IP67 waterproof bluetooth smartwatch for Android iOS Phones with heart rate blood pressure monitor multifunction Andriod smart watch with steps counter sleep monitor sports fitness watch, monitoring blood oxygen saturation allows you to understand your physical condition in real time to track fitness progress ,to know your health status in time.
- 【More Functions Bluetooth Call Smart Watch】This fitness activity smart watch full screen for iPhone and Android phones includes a bunch of new features including:The bluetooth smart watch can hang up the phone, receive and display WhatsAPP /Text /Facebook /Twitter /Messenger reminder.Support sedentary reminder, alarm clock, stopwatch, timer,weather information,music control, remote camera control compatible with Android 5.0 and above or iOS 9.0 and above smartphones.
Single writer with read replicas
A primary database accepts writes. Read replicas may serve carefully selected read traffic only when your application and cache policy tolerate replication lag. Administrative operations, logins, media metadata, and immediately-after-save views should not be routed to a replica that can be behind the writer.
Replicated primary with failover
If the primary fails, promote a replica through a runbook that verifies replication health, prevents the old primary from returning as a second writer, updates the connection endpoint, and checks application writes. Monitor replication lag and record the last known consistent position so you can state the possible data-loss window.
Database backup is separate from replication
Replication copies mistakes and deletions as well as valid changes. Keep independent, restorable backups with retention appropriate to the network. Test restoring the full database, not just one site’s tables, into an isolated environment.
Make uploads available on every node
Shared filesystem
A shared filesystem gives each node the same path and immediate visibility of new files. Test latency, locking, ownership, quotas, directory creation, and behavior during a storage outage. Verify that a file uploaded on node A can be downloaded through node B before declaring the layer ready.
Free tools Windows power users keep installed
One-click scans. No signup required.
Object storage or file replication
Object storage and file replication can reduce dependence on a single filesystem, but they introduce synchronization semantics. Define how quickly a new upload becomes readable, how deletes propagate, how retries are handled, and how two nodes behave if they attempt to create or replace the same object. Large uploads need tested timeouts and multipart or resumable behavior where supported.
Do not rely on local disks without a routing rule
If each node writes to its own local wp-content/uploads, a visitor can see a broken image whenever the next request lands on a different node. Local disks are suitable only when traffic is deliberately pinned to the node that owns the files and a separate process guarantees replication before failover.
Rank #3
- [Low Noise High Fidelity] New bee guitar cord with 22AWG oxygen-free-copper center conductors provides enhanced signal transfer, the PVC insulation material and the high-density stranded copper double shield provide noise rejection for quiet operation
- [Ideal for Choice] New bee 1/4 straight and right angle metal connectors, ensures a secure connection in any instrument, pedal, or amp jack. L shape great fro on stage guitar stands
- [Wide Compatible] Suitable for mixer, power amplifier, microphone, effector, decoder, equalizer, electoronic organ, electric guitar, electric bass and other electronic equipments. Widely used in the installation of smart home, karaoke speaker, professional stage audio, etc
- [Easy Disassemble] Making incidental repairs quick and easy! Very nice, flexible cable
- [Dont Hesite to Order] 24 hours customer services and professional technology team are standing by
Validate the complete media path
- Upload an image from a representative subsite and confirm its attachment metadata and file are visible through every node.
- Generate an image size and request that derivative from a different node.
- Rename or delete a file and verify that the change propagates according to your stated delay.
- Test filenames containing non-ASCII characters, large files, and simultaneous uploads.
- Confirm backups include the entire per-site media tree and can restore it with correct ownership.
Put DNS, HTTPS, and routing in front of the nodes
Choose subdomains or subdirectories early
WordPress requires a network addressing model: subsites use either subdomains or subdirectories. The administration handbook warns that changing this choice later can be difficult, so decide before production. A subdomain network needs wildcard DNS and certificates that cover the required names; a subdirectory network keeps sites beneath the primary host and has different rewrite requirements.
Configure mapped domains deliberately
Native domain mapping is available from WordPress 4.5. Each mapped domain must exist in DNS and resolve to the front door. Issue a certificate for every hostname, including the primary network domain and mapped domains. Use Server Name Indication (SNI) when one HTTPS endpoint serves additional domains. Keep certificate, virtual-host, redirect, and rewrite configuration identical across nodes.
Health checks and client affinity
Configure load-balancer health checks to test application readiness, not merely whether a TCP port is open. A node should be removed when it cannot reach the authoritative database or uploads store. Prefer stateless operation; if a plugin requires sessions, use a shared session mechanism or deliberate client affinity and document the failure behavior.
Cache invalidation
Define how a post update, plugin change, or network setting change purges page and object caches on every node. A local cache that survives an update can serve old HTML even though the database is correct. Include cache purge in deployment and rollback scripts.
Control cron, queues, and other background work
Multiple nodes can run the same scheduled task at once. That can duplicate email, imports, image generation, cache purges, or external API calls. Choose one of these patterns:
- Run the system scheduler on one designated node and disable competing triggers elsewhere.
- Use a distributed lock with an expiry and monitoring so another node can take over after a failure.
- Place jobs in a queue with one consumer or an idempotent worker design.
Whichever pattern you choose, record ownership, lock duration, retry behavior, and alerting. Test what happens when the worker dies halfway through a job and when the database is temporarily unavailable.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Rank #4
- Digital Family Calendar: BSIMB digital calendar wall touch screen puts an end to your chaotic life. Designed for busy families, the digital calendar keeps you organised and in step with your family. Assign different colours and tasks to each family member to make family scheduling easier and more intuitive.
- Easy Setup and Auto-Sync: Plug in, connect to WLAN and auto-syn your electric calendar in minutes. Digital wall calendar compatible with Google calendar, iCloud calendar, Outlook calendar, Cozi calendar and Yahoo calendar. Add events directly on the device or through the ecalendar app. Electronic calendar stays current whether you're at work or traveling—no manual updates needed.
- All-In-One Home Assistant: Smart calendar builds habits and encourage independence with personalised chores. Display daily meal plan to reduce the daily ‘What's for dinner?’ stress. To-do lists keep track of everything you want. Turning chores into valuable achievements with stars and rewards, making life easier and more enjoyable.
- Manage Anytime Anywhere: BSIMB electronic calendar for family stay connected with the powerful ecalendar app. Access and manage your digital wall calendar anytime, anywhere with free features like stars & rewards, photo screensaver, chore charts, meals plans, to-do lists etc. Electronic planner paid features like Magic Import tailor advanced tools for users with special needs.
- Stay in Touch with Loved Ones: Share photos or videos from your phone to electronic wall calendar with app, instantly update your life moment, and keep in touch with your family, especially those who are far away; you can also surprise your smart calendar digital wall by sending him a wish card; it's also great for keeping tech-illiterate elders in touch with the youngsters.
Automate checks and changes with WP-CLI
WP-CLI provides scriptable database, plugin, theme, cache, and multisite administration. Run commands from a controlled release environment, authenticate to the intended database, capture output, and review a dry run before changing production.
# Inspect the network database update without changing it
wp core update-db --network --dry-run
# Apply a reviewed network database update
wp core update-db --network
# Typical migration operations; adapt paths and URLs to the environment
wp db export backup.sql
wp search-replace 'https://old.example' 'https://new.example' --all-tables
wp cache flushThe --network flag makes the database update network-aware, while --dry-run lets you inspect the operation first. Use --url when a command must target a particular site, and log the command, operator, timestamp, and result. The official WP-CLI project and command reference document export/import, search-replace, plugin and theme management, and multisite administration.
Make search-replace serialization-safe
Multisite databases contain serialized values and many references to domains and paths. A blind SQL replacement can corrupt serialized lengths and leave unusable options. Use WP-CLI search-replace or another serialization-aware tool, limit replacements to the planned old and new values, and inspect the result before opening the site to users. Export first so the original state can be restored.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Move a Multisite to another server or domain
A same-domain move is simpler than a domain or path change. The migration handbook notes that Multisite is more complicated because the database stores multiple references to server names and folder locations. Copy the complete application and database together for a same-domain move. For a domain or path change, update references deliberately and review network and per-site values.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →- Freeze or announce the change. Put the network in a maintenance window or stop content edits so the database and uploads have a known point in time.
- Back up everything. Export the full database and copy
wp-content, configuration, custom server rules, and all per-site uploads. Verify that the backup can be read before proceeding. - Provision the target. Install the exact application build, PHP extensions, web-server rules, permissions, and network constants used by the source.
- Restore database and files. Restore the complete database and uploads before testing URLs. Keep the source environment untouched for rollback.
- Apply planned substitutions only. For a domain or path change, review
wp_blogs,wp_site, and each site’shome,siteurl, andfileupload_urlvalues. Use a serialization-aware search-replace tool; never run an unscoped SQL replacement across serialized data. - Check the network database schema. Run
wp core update-db --network --dry-run, review the output, then run the command without--dry-runonly when the change is approved. - Test representative sites. Check the main site and subsites with different domains or paths, including a newly created site if possible.
- Cut over traffic. Change DNS or the load-balancer target, issue or activate certificates, and monitor errors, database lag, storage errors, and cache behavior.
- Retain rollback. Keep the old environment available until logs, uploads, admin actions, scheduled jobs, and external integrations remain healthy for the agreed observation period.
Test before declaring the network synchronized
- Authentication: log in and out on more than one node; verify administrator and ordinary user permissions.
- Content: create, edit, schedule, trash, and restore content on multiple subsites.
- Media: upload, edit, resize, replace, and delete files, then fetch them through each node.
- URLs: test permalinks, redirects, canonical URLs, subdomain or subdirectory routes, and every mapped domain.
- Forms and APIs: submit forms, test REST and other API calls, and confirm webhooks point to the intended environment.
- Background work: observe cron, queues, image generation, cache purges, and scheduled publishing for duplicate execution.
- Failure paths: remove one web node, interrupt storage access, simulate database failover, and verify health checks and recovery steps.
- Observability: centralize web, PHP, database, load-balancer, storage, and cron logs. Alert on failed health checks, replication lag, disk or storage errors, and repeated job retries.
Common failure modes and fixes
Different nodes show different content
Check whether nodes point to different databases, whether a read replica is behind, and whether page or object caches are local and stale. Confirm the database endpoint and cache purge behavior on every node.
Images work intermittently
The usual cause is node-local uploads or replication delay. Compare the upload path and storage mount on each node, test cross-node reads, and verify permissions and deletion propagation.
Users are logged out after a request moves nodes
Inspect cookie domain and HTTPS settings, then determine whether a plugin stores sessions locally. Prefer stateless authentication or a shared session mechanism; use client affinity only as a documented temporary measure.
Scheduled tasks run twice
More than one node is acting as a cron runner or a lock is expiring too soon. Assign one owner or introduce a monitored distributed lock, then make jobs idempotent where possible.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minutePC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Subsites redirect to the old domain
Review network and site URL values, mapped-domain DNS, certificate names, rewrite rules, and serialized options. Run a scoped, serialization-aware search-replace and clear caches after verification.
A plugin update breaks only some nodes
The deployment is inconsistent. Compare plugin and theme inventories, stop routing traffic to the outlier, restore the known-good artifact, and redeploy the tested build to every node.
Operational checklist
- Document the topology, database writer, failover owner, storage design, and expected recovery point and recovery time.
- Build all nodes from one versioned artifact and record checksums or release identifiers.
- Monitor database connectivity and replication lag, not just web-server uptime.
- Back up the full database, configuration, custom code, and uploads; test isolated restores on a schedule.
- Keep DNS records, certificates, SNI configuration, rewrites, and redirects aligned.
- Define cron and queue ownership, lock recovery, retries, and alerting.
- Run WP-CLI commands through reviewed scripts with dry runs and captured output.
- Rehearse node loss, database promotion, storage recovery, rollback, and DNS reversal before an emergency.
Bottom line
Multisite can serve traffic from several servers reliably, but it is not a collection of independent WordPress installations. Synchronize the shared code and configuration, keep database writes under one deliberate authority, provide a consistent uploads layer, configure every domain and certificate, coordinate caches and background jobs, and automate migrations with tested WP-CLI procedures. Backups, representative subsite tests, and a rehearsed rollback are the safeguards that turn a multi-node design into an operable one.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
Recommended Free Tools
