Portfolio eEgnith Backup
A backup exists only once it is verified
Our in-house service for client sites on eEgnith. Servers send database and media copies to separate storage every night, and the service verifies each file, removes old copies on schedule and messages Telegram as soon as a site is left without a fresh copy.
Project
eEgnith Backup
- Client
- Asign — for the sites we deploy and maintain More than 20 servers with client sites, and we are responsible for each site if something breaks.
- System
- Central copy storage with verification and monitoring It receives copies from every server, verifies them, keeps rotation and shows the state of each site in one panel.
- Our role
- Architecture, back end, panel and deployment Plus server-side scripts, secure file transfer, notifications and tests.
- Technologies
-
- PHP
- Laravel
- Filament
- Livewire
- MariaDB
- Redis
- Control
- History of changes and downloads You can see who changed a server or site setting, who issued access and who downloaded a copy.
Task
Copies existed, but nobody knew if they worked
Each server made its own copies and kept them next to the sites. Nobody saw the whole picture: whether the nightly copy ran, whether the file was intact and how much space was already used.
The copy is not where the site is
If a server is broken or lost, copies stored on it disappear along with the site. Separate storage is needed.
A hacked server cannot erase copies
Even if someone gains access to a site’s server, they must not be able to delete or overwrite copies already stored.
Verification, not faith
A “copy done” report guarantees nothing. The file must be there, complete and able to open.
Know at once
A site without a fresh copy must be noticed the same morning, not when a restore is needed.
Solution
Transfer, verify, keep, alert
Write-only storage
Each server has its own key and access to its own folder only, and can only add files — not delete them or read anyone else’s. So even a hacked server cannot reach other copies or erase its own.
Every file is verified
After a server reports, the service checks that the file is there, has the expected size and checksum and unpacks without errors, and that a database dump is neither empty nor cut off. Only then does the copy count, and stored copies are re-verified regularly.
Rotation and alerts
Old copies are removed on a daily, weekly and monthly scheme, and the newest verified copy of each type is never deleted. An overdue or broken copy opens an alert in Telegram, and a summary of all sites arrives every morning.
Capabilities
Backups of every site in one panel
01 · 4
Copies
- Database, media and video as separate types
- An identical copy is not sent again — only confirmed
- Hourly copies in working hours for busy sites
- Downloading a copy from the panel
02 · 4
Verification
- Presence, size and checksum
- Archive integrity check
- Regular re-verification of stored copies
- State of each site: fine, attention, problem
03 · 4
Storage
- Rotation by days, weeks and months
- Rotation settings per site
- Space used by each site and server, with charts
- New sites appear in the panel by themselves
04 · 4
Security and control
- A separate key and token for each server
- Write-only access, no deletion
- Alerts and a morning summary in Telegram
- Admin and viewer roles, activity log
Result
For every site we know whether it has a working copy
Copies of all sites are kept apart from the sites themselves, and no server can erase them. Every copy is verified, and old ones are removed on schedule by themselves.
If a nightly copy did not arrive or turned out broken, Telegram says so the same morning — long before the copy is needed.