How We Manage Database Backups

BulkMail follows a structured, multi-layered backup strategy to ensure client data is secure, recoverable, and protected against system failures.

System Architecture Overview

• Each client has a dedicated database instance on a primary server within our secure database cluster.
• Every primary server is paired with two secondary servers that continuously replicate the data.
• These secondary servers are typically a few seconds behind the primary, ensuring near real-time redundancy.

Real-Time Replication

• Secondary servers replicate data in near real-time with a slight delay due to data volume.
• Each secondary server is equipped with multiple storage drives.
• If one drive fails, the server continues operating without data loss or service disruption.

Regular Backup Process

• Full database backups are taken multiple times daily.
• Backups are stored in a separate data centre, providing an added layer of protection.

• We retain:

  • Daily backups for the past 7 days
  • Weekly backups for the 3 weeks prior to that

No Cloud-Based Data Storage

• We do not store client data in the cloud.
• Cloud infrastructure is used only for non-sensitive assets such as images.

System Resilience and Monitoring

• Our database architecture is built for resilience and redundancy.
• Most system issues are resolved internally without affecting clients.
• Backup processes are actively monitored and continually optimised to maintain high standards of data protection.