Cyclone Hosting practical guide: A backup plan is successful only when it can restore the site within the time your business can tolerate being offline.
Why One Backup Is Not Enough
A backup stored only inside the hosting account may be affected by the same account problem, deletion, compromise, or storage failure as the website. A stronger plan uses more than one location.
Follow The 3-2-1 Principle
A common approach is to keep three copies of important data, use two different storage types, and keep one copy in a separate location.
Back Up Files And Databases
Website files contain themes, plugins, uploads, code, and configuration. Databases contain posts, pages, users, settings, and application data. A complete website backup usually requires both.
Match Frequency To Change
A mostly static website may need less frequent backups than an active store or membership site. Back up often enough that the amount of lost work after an incident would be acceptable.
Test The Restore Process
A backup is useful only when it can be restored. Periodically verify that files can be opened, database exports are valid, and the restoration steps are understood.
Create a fresh backup before software updates, major design work, domain changes, or migrations.
Cyclone Hosting Practical Checklist
- Back up files and databases on a schedule based on how often the site changes.
- Keep at least one copy outside the hosting account.
- Label backups with the domain and date.
- Perform a test restore before an emergency.
When To Contact Support
Contact Cyclone Hosting support when the issue involves the hosting account, server access, DNS hosted with us, email-server settings, SSL issuance, or an error you cannot isolate. Include the domain, the exact error, the page or mailbox affected, when it began, and the troubleshooting already attempted. Never send a password in a normal support message.
What To Record For Future Reference
Keep a short change log containing the date, the setting changed, the reason for the change, and the backup or rollback point. This makes future troubleshooting faster and helps separate a hosting problem from an application change.