This article explains how to set up automated backups for your development or staging website on Web60.
1. Access Your Web60 Portal
Log into your Web60 account at your portal URL. You'll see a list of your websites. Click on your development or staging site (not your live site).
Development sites usually have names like "mysite-dev" or "staging.mysite.ie".
2. Navigate to Backup Settings
In your website dashboard, look for the "Backups" section in the left menu. Click on "Backup Settings" or "Automated Backups".
You'll see options for backup frequency and retention (how long backups are kept).
3. Choose Your Backup Schedule
For development environments, select how often you want backups:
- Daily: Good if you're actively developing
- Weekly: Suitable for less frequent changes
- Before updates: Automatic backup before any WordPress or plugin updates
Click "Daily" if you're making regular changes to your development site. This ensures you don't lose recent work.
4. Set Backup Retention Period
Choose how many backups to keep:
- 7 days: Keeps one week of daily backups
- 30 days: Keeps one month of backups
- 90 days: Longer retention for important development milestones
Select "30 days" for a good balance of safety and storage.
5. Enable Database and File Backups
Make sure both options are ticked:
- Database backup: Saves your content, settings, and user data
- File backup: Saves your WordPress files, themes, and plugins
You need both to fully restore your development site if something goes wrong.
6. Test Your Backup Setup
Click "Create Manual Backup Now" to test the system. This creates an immediate backup outside your normal schedule.
Wait 5-10 minutes, then refresh the page. You should see your new backup listed with today's date.
7. Set Up Backup Notifications
Click on "Notification Settings" to get emails when:
- Backups complete successfully
- Backups fail
- Storage space is running low
Enter your email address and click "Save". This helps you catch problems early.
8. Document Your Backup Schedule
Write down your backup settings somewhere safe. Include:
- Backup frequency (daily/weekly)
- Retention period (30 days)
- Your Web60 login details
This information helps if you need to restore your site later or if someone else needs to access it.
Development environments are perfect for testing changes before updating your live site. Regular backups mean you can experiment safely, knowing you can always go back to a working version.
For additional protection, consider setting up off-site backup storage to store copies outside Web60's servers.
If you're still stuck, contact Web60 support through your portal. Include your website name and describe which step isn't working.
FAQ
Q: Should development site backups be different from live site backups?
A: Yes, development sites often need more frequent backups since you're making regular changes. Daily backups work well for active development.
Q: How much storage space do development backups use?
A: Development sites are usually smaller than live sites, so backups use less space. A typical small business development site backup is 50-200MB.
Q: Can I restore my development site to my live site?
A: Yes, but be very careful. Development sites often contain test content or broken features that shouldn't go live. Always review changes first.
Q: What happens if my development backup fails?
A: You'll get an email notification if you set them up. Check your development site's storage space and contact support if failures continue.
Q: Should I backup before every change I make?
A: No need for every small change. Daily automatic backups are usually enough, but create a manual backup before major changes like new themes or plugins.
Q: How long do development backups take?
A: Development sites are typically smaller than live sites, so backups complete faster - usually 2-5 minutes for a small business development site.
Q: Can I download my development backups to my computer?
A: Yes, you can download backup files through your Web60 portal. This gives you an extra copy stored locally on your computer.
Last updated: 1 March 2026