This article explains how Web60 protects your website data using multiple copies stored in different locations.
What Data Redundancy Means
Data redundancy means keeping multiple copies of your website files and database in different places. If one copy is damaged or lost, another copy is available immediately. This prevents your website from going offline or losing important content.
Web60 creates these copies automatically - you don't need to do anything.
Primary and Secondary Storage
Your website lives on a primary server in Ireland. This server handles all visitor requests and updates to your site. Every few hours, Web60 copies your entire website to a secondary server in a different data centre.
If the primary server has problems, the system switches to the secondary server automatically. Your visitors won't notice any difference.
Real-Time Database Replication
Your WordPress database contains all your posts, pages, comments, and settings. Web60 copies database changes to backup servers within minutes of you making them.
When you add a new page or update your contact details, that change gets copied to backup servers almost immediately. This means recent changes are never lost, even if something goes wrong with the main server.
Geographic Distribution
Web60 stores copies of your data in multiple locations across Ireland and the EU. This protects against local problems like power outages, internet connection issues, or natural disasters affecting one data centre.
Each location has its own power supply, internet connections, and cooling systems. Problems in one location don't affect the others.
Automated Backup Verification
Web60 automatically checks that backup copies are complete and working. The system tries to restore small test sections from backups every day to make sure they're not corrupted.
If a backup copy has problems, Web60 creates a new one immediately and sends an alert to the technical team.
Integration with Your Backups
Data redundancy works alongside the automatic backups that you can download from your Web60 portal. Redundancy protects against server failures, while your downloadable backups protect against accidental changes or deletions.
You can also create manual backups before making major changes to your website.
Recovery Time
If Web60 needs to switch to a backup server, this usually happens within 5 minutes. For database problems, recovery typically takes 10-15 minutes while the system finds the most recent clean copy.
Your website address and all content remain exactly the same - visitors just get served from a different physical location.
If you're still stuck or want more details about how your specific data is protected, contact Web60 support through your portal.
FAQ
Q: Do I need to set up data redundancy myself?
A: No, Web60 handles all data redundancy automatically. Multiple copies of your website are created and maintained without any action from you.
Q: How often are backup copies updated?
A: Database changes are copied within minutes, while full file copies happen every few hours. This ensures recent changes are always protected.
Q: What happens if both the primary and secondary servers fail?
A: Web60 maintains copies in multiple data centres. If two locations have problems, your site automatically switches to a third location.
Q: Can I access these redundant copies myself?
A: No, redundant copies are managed automatically by Web60's systems. You can download your own backups from the Web60 portal for your own records.
Q: Does data redundancy slow down my website?
A: No, copying data to backup servers happens in the background and doesn't affect your website's loading speed for visitors.
Q: Are redundant copies stored in Ireland?
A: Yes, Web60 keeps copies in multiple Irish and EU locations to comply with data protection laws while ensuring geographic protection.
Q: What if I accidentally delete something - will redundancy restore it?
A: Data redundancy protects against server failures, not accidental deletions. For that, you need to restore from a backup made before the deletion occurred.
Last updated: 1 March 2026