Database error before opening. System restored from last night’s backup.
An overnight server error corrupts recent quote records. The owner discovers it before opening. Using IBIOS one-click restore, they select the previous night's backup, check it, and restore everything atomically without any outside help. Staff carry on with a working system.
What happens to a trade business when its data is deleted or corrupted?
Without a tested, accessible backup system, a corrupted database means one thing: panic. You call your hosting provider. They tell you they have nightly backups but restoring them requires a support ticket and a wait. Your system is down for the morning. Staff cannot access quotes. Customers calling for updates get no answer. Jobs cannot be confirmed.
If the incident happens to a system built on generic hosting without a managed backup, the outcome is worse: the business owner spends the morning on the phone before discovering that “we take backups” meant “we back up the server image, not the database.” In the worst case, data is simply gone.
IBIOS is designed so that a business owner with no technical background can identify a backup, verify it is valid, and execute a full restore without any outside help. There is no support ticket to raise and no waiting for someone else to act.
How do you restore IBIOS after a data incident?
A step-by-step walkthrough of exactly what happens from the moment the owner discovers the problem.
Incident discovered before opening
The owner opens IBIOS over breakfast and finds recent quote records are corrupted or missing. An overnight server process wrote bad data to the quotes table.
Restore point selected
The owner opens the IBIOS backup panel. It shows the available restore points, each with a timestamp, verified size, and record count. They select the snapshot from the previous night — a clean, complete backup.
Checksum verified automatically
Before the restore begins, IBIOS verifies the backup checksum against the stored hash. The backup passes. The owner confirms the restore. The system shows an estimated completion time.
Atomic restore
The restore applies the entire snapshot to the database. Every quote, customer record, and order is returned exactly as it was when the snapshot was taken. The process is atomic — either all of it succeeds or nothing changes.
System live again
The restore completes and staff work on a fully operational system. The audit log records the restore event with the operator’s name and the restore point used.
What is the outcome?
One click
to start a full, atomic database restore once a restore point is chosen
Checksum
verification on every restore point before it is applied
Off-server
backup copies kept separately from the live server
The encryption and separate storage matter as much as the restore itself. A backup stored on the same server as the live database is no backup at all — a server failure takes both at once. IBIOS archives are written to a separate encrypted location from the moment the backup completes, so a live server incident cannot affect the restore point.
How does backup and restore work in IBIOS?
What does a “full database restore” actually cover — is it everything?
A full restore covers every table in your IBIOS database: customers, jobs, quotes, quote line items, products, suppliers, supplier orders, users, roles, and the complete audit log. It also restores uploaded files — quote documents, product images, and generated Word documents — from the same backup snapshot. Nothing is partial.
Can I restore just one customer record rather than rolling back the whole system?
Yes. In addition to full restores, IBIOS supports granular record recovery. You can select a specific customer, job, or quote from any restore point and bring it back without affecting the rest of the live system. This is useful for recovering accidentally deleted records without disrupting active work.
How do I know the backup is valid before I restore it?
Every backup includes a checksum verified at the time of creation and again at restore time. The restore interface shows the backup’s creation timestamp, verified size, and the number of records it contains — so you can confirm you are restoring a complete, uncorrupted snapshot before committing. If the checksum does not match, the restore is blocked and you are alerted.
What happens to changes made between the backup time and the restore?
Any changes made after the backup point — typically up to the time the incident occurred — are not included in the restore. IBIOS displays the exact backup timestamp before you confirm, and the audit log captures all changes up to the incident so you can identify what was lost and re-enter it manually if needed.
Is there any risk of a partial restore leaving the system in an inconsistent state?
No. Restores are atomic: either the entire backup is applied or nothing changes. If the restore process encounters an error partway through, it rolls back to the pre-restore state automatically. You cannot end up with a system that is half-restored. The live database is never touched until the restore is confirmed complete and verified.
Related features
Backups cover the records your team works in every day, including the IBIOS CRM and order management. See also the digital trade business checklist and IBIOS for showroom retailers. IBIOS (Integrated Business Intelligence & Operations System) is made by IBIOS Limited (NI743167), Northern Ireland. Access is by waiting list; there is no free trial.
A data incident should not cost you a trading day.
IBIOS one-click restore with checksum verification and copies kept off the live server. Recover the system yourself, without a support ticket.