Summary
BeeTcore backs up every platform in its care to storage held separately from the production host, so a failure that affects the host never affects the ability to recover from it. Backups capture everything needed to restore a working platform, are protected in storage, and are tested by restoring them. Backup data belongs to the client.
1. Principle
A backup stored only on the system it protects is not a backup. Backups are held independently of the production hosting environment, with separate access credentials.
2. Coverage
Every backup captures a complete, restorable state of the platform:
- Content management platforms: the full file system, database, media, and configuration.
- Custom applications: databases, uploaded files, and environment configuration. Application code is held separately in version control, as set out in the Development Methodology SOP.
A backup that captures files without the database, or the reverse, is not a recoverable state.
3. Frequency and retention
Backup frequency and retention are set for each platform according to its service tier, as defined in the Service Continuity and Disaster Recovery Strategy, and confirmed in its project agreement. Where a client has its own backup or testing requirements, BeeTcore adopts them.
An additional backup is always taken immediately before any significant change, including platform upgrades, plugin and dependency updates, and structural changes, as set out in the Change Management Framework.
4. Storage and security
- Backups are stored in encrypted object storage, independent of the production host.
- Access is restricted to authorised team members, with credentials separate from hosting credentials.
- Credentials and secrets are never stored in backup archives in plain text.
5. Verification
A backup that has never been restored is unverified. Backups are tested regularly, at planned intervals, by restoring them into an isolated environment and confirming that the platform works.
6. Restoration
- After an incident: restoration follows the Incident Management Response Strategy, within the recovery objectives set for the platform.
- On request: clients can ask for a restoration of their platform or of specific content, handled according to their maintenance plan.
- Every restoration is verified for function, data integrity, and integrations before it is confirmed with the client.
7. Documentation and reporting
Backup schedules, storage locations, and restoration procedures are documented for every platform. Backup status and test results are available to clients on request.
8. Ownership, retention, and review
- Backup data belongs to the client, and a copy can be requested at any time.
- At the end of an engagement, backups are handed over or securely deleted, as set out in the project agreement.
- These standards are reviewed annually and as technology and client needs change. Findings feed into Continuous Service Improvement.
Frequently asked questions
How often does BeeTcore back up my platform?
Backup frequency and retention are set by your platform's service tier and confirmed in your project agreement. An extra backup is always taken before any significant change.
Where are backups stored?
In encrypted storage, independent of your hosting provider, with separate access credentials. A problem with your host never affects the ability to restore from backup.
Can I get a copy of my backups?
Yes. Backup data belongs to you, and a copy can be requested at any time.