Your data is now backed up every night
Every night the whole WBSender database, including your contacts, campaigns, reports, templates and automation rules, is copied to encrypted cloud storage kept separate from the server. Thirty days of snapshots are kept, so a bad day on the server no longer means lost data.
Highlights
- A full snapshot of the database is taken every night at 03:00 Bangladesh time
- Snapshots are encrypted and stored off the server, in private cloud storage
- 30 days of history are kept, and the 7 most recent are never removed
- Every snapshot is checked after upload, so a broken copy is never counted as a good backup
- The first snapshot was taken on 5 October and checked against the original
In this release2
- NewSystemHigh impact
Nightly database snapshots to encrypted cloud storage
Until now the database only had an occasional copy taken by hand, and that copy lived on the same server as the database itself. If the server had a serious problem, the copy could have gone with it.
The database is now copied off the server every night.
What happens each night:
- At 03:00 Bangladesh time, the quietest hour of the day, a complete snapshot of the database is taken.
- The snapshot is compressed and sent straight to private cloud storage as it is being made, so it never fills up the server's disk.
- It is encrypted while stored, and a fingerprint of the file is saved next to it so any later copy can be checked against the original.
- Before anything is uploaded, the system proves that the storage location cannot be read without our credentials. If that check ever fails, the upload is stopped rather than risk exposing any data.
- After the upload, the stored size is compared with what was sent, so an interrupted copy is never mistaken for a good one.
- If something goes wrong, the job tries again an hour later, up to three times in total.
Nothing changes in how you use WBSender. Sending, campaigns and the dashboard carry on exactly as before while the snapshot runs.
BeforeAn occasional copy taken by hand, stored on the same server as the database.
AfterAn encrypted snapshot every night, stored off the server, with 30 days of history.
- ImprovedSystem
Thirty days of history, checked and tested
A backup is only useful if it can be restored, and only if it goes back far enough to reach a time before the problem started.
How the history is kept:
- Each night adds a new snapshot rather than replacing the last one.
- Snapshots older than 30 days are removed automatically, so storage does not grow forever.
- The 7 most recent snapshots are never removed, even if several nights in a row were to fail, so there is always a recent copy to fall back on.
How we know it works:
- The first snapshot was taken on 5 October. We downloaded it again, confirmed its fingerprint matched the original, and confirmed the file is intact and in the format the restore tool reads.
- A snapshot can also be taken by hand at any time, which we will do before any risky maintenance from now on.
0 days30 daysDatabase history that can be restored