Quick Summary
A database backup is a copy of the database taken at a specific point in time, used to restore the database if the original is lost, corrupted, or encrypted by ransomware. Database backup is distinct from server-level backup — a server backup may capture a snapshot in an inconsistent state; a proper database backup uses the database engine's own backup mechanism to guarantee a consistent, restoreable copy. For Ethiopian businesses, the risks that make database backup critical include power surges that damage servers, ransomware attacks that encrypt database files, and hardware failures where replacement can take weeks.
Database Backup Types
| Backup Type | What It Captures | Speed | Storage Size | Use Case |
|---|---|---|---|---|
| Full backup | Complete copy of the entire database at backup time | Slowest | Largest | Weekly or daily full backup as foundation; the base from which other backup types restore |
| Differential backup | All changes since the last full backup | Medium | Medium (grows over time) | Daily backups between full backups — faster than full, faster to restore than transaction logs alone |
| Transaction log backup | All transactions since the last log backup | Fastest | Smallest | Frequent backups (every 15–60 minutes) for low-RPO databases; enables point-in-time recovery |
| Snapshot | Point-in-time copy at the storage level; may not be database-consistent | Near-instant | Variable | Supplement to, not replacement for, database-level backups; useful for quick rollbacks in test |
Recommended Backup Schedule for Ethiopian Businesses
A standard tiered backup schedule that balances recovery granularity against backup overhead:
- Weekly full backup — complete database copy taken at low-activity time (Sunday/Saturday night)
- Daily differential backup — changes since last full backup, taken nightly
- Transaction log backups every 15–60 minutes — for databases where losing more than one hour of transactions is unacceptable (financial systems, ERP, operational databases)
The 3-2-1 Rule Applied to Databases
3 copies of the database
The live database plus two backups (local backup destination and off-site / cloud backup)
2 different storage media
For example, local backup on a NAS or external drive, plus cloud storage (AWS S3, Backblaze B2, Azure Blob)
1 copy off-site
Stored separately from the primary server, so a physical event (fire, theft, power surge) does not destroy both the database and the backup
1 copy immutable (recommended extension)
Cloud backup with object lock that cannot be deleted or encrypted by ransomware — the 3-2-1-1 strategy
Ransomware and backups: Ransomware encrypts all data it can access — including backup files on network-attached storage that is connected to the infected server. A backup stored on a mapped drive or NAS share accessible from the database server may be encrypted alongside the database itself. Off-site backups and cloud backups with immutability are the protection against ransomware destroying both the database and its backups simultaneously.
Database Backup Tools and Platforms
| Tool / Platform | Database Support | Key Features | Ethiopian Context |
|---|---|---|---|
| MySQL/MariaDB built-in (mysqldump, mysqlbackup) | MySQL, MariaDB | Native logical and physical backup; scriptable for automation | Free; requires scheduling via cron or Task Scheduler; no monitoring without additional tooling |
| PostgreSQL built-in (pg_dump, pg_basebackup) | PostgreSQL | Logical and physical backups; WAL-based continuous archiving for point-in-time recovery | Free; requires WAL configuration; suitable for businesses with IT capability |
| SQL Server Maintenance Plans / SQL Agent | Microsoft SQL Server | GUI-configured backup jobs; full/differential/log; native integration | Included with SQL Server; suitable for businesses on Microsoft stack |
| Veeam Backup | SQL Server, Oracle, MySQL, PostgreSQL | Centralised management; monitoring; alerting; immutable backup; cloud replication | Commercial; enterprise-grade; appropriate for businesses with multiple databases |
| Cloud-native backup (AWS RDS, Azure SQL Backup) | Cloud-hosted databases | Automated by provider; point-in-time recovery; retention configuration | Included with cloud database services; the simplest option for cloud-hosted databases |
Backup Verification: The Most Skipped Step
A backup that cannot be successfully restored is not a backup — it is the illusion of a backup. The most common failure scenario is a business that believes its databases are backed up, discovers during an actual recovery scenario that backup jobs have been failing silently for weeks, and has no usable backup to restore from.
- Backup job monitoring: Every backup job must have monitoring and alerting. A failed job should generate an alert that is reviewed — not manual checking that may not happen.
- Restoration testing: At a minimum quarterly, restore the backup to a test environment and verify the restored database is complete and consistent. This is the only way to know with confidence the backup is usable.
Frequently Asked Questions
How often should an Ethiopian business back up its database?
The backup frequency should be driven by the RPO (Recovery Point Objective) — the maximum acceptable data loss. For a financial database where losing more than one hour would have significant consequences, transaction log backups every 15–30 minutes are appropriate, with daily full or differential backups. For a less critical database where losing a full day is acceptable, daily backups are sufficient.
Is backing up a database to the same server sufficient?
No — a same-server backup provides no protection against hardware failure, fire, theft, or ransomware. If the server fails, both the database and the backup on the same server are lost simultaneously. A minimum viable backup strategy requires at least one copy stored separately — on a NAS, an external drive taken off-site, or cloud backup. For ransomware protection, the backup must not be accessible from the server via a network share at the time of infection.
Reliable Database Backup Solutions for Ethiopian Businesses
Bright IT Solutions configures, monitors, and manages database backup solutions for Ethiopian organisations — including off-site and cloud backup with monitoring and regular restoration testing.
Prefer to talk first? Contact us