Go back to the morning before it all went wrong.
Most backup keeps one copy: last night's. If last night already had the mistake in it, that is exactly what you get back. SimbaVault keeps every version of every file, every day, so you choose which morning to return to.
- A separate copy each day
- Daily
- A separate copy each day
- Before it leaves your network
- Encrypted
- Before it leaves your network
- A restore before we leave
- Tested
- A restore before we leave
Every day kept, off site
Encrypted before it leaves your network
Versioning: every version, every day
The copy you need is almost never last night's.
By the time anybody notices, the damage is usually a few days old. A backup holding one copy hands the damage straight back to you. We keep each day separately, so the bad day is just one day in a list and you pick a different one.
- Day 1Clean
- Day 2Clean
- Day 3Clean
- Day 4Clean
- Day 5Encrypted
- A folder deleted on Friday and noticed on Tuesday: take Thursday's.
- A quotation somebody overwrote three weeks ago: take the version from before they did.
- Ransomware that ran overnight: take the last clean day, not the encrypted one.
The moment this matters
You will not plan for this. You will be interrupted by it.
- Someone deletes the wrong folder on a Friday afternoon, and nobody notices until Tuesday.
- A laptop is taken from a car in town, and six months of work goes with it.
- The finance server will not boot, and the person who set it up left in 2023.
- Ransomware encrypts a share, and the sync folder faithfully copies the damage to every other machine.
- An auditor asks to see evidence of a restore test, and nobody has ever run one.
Every one of those is an ordinary Tuesday somewhere. What decides whether it is an inconvenience or a closure is whether somebody kept a copy the trouble could not reach, and whether anyone ever checked that it comes back.
Let's clear this up
“We already have Google Drive.”
Drive and OneDrive are very good at what they do, and what they do is keep one copy matching across your devices. That is syncing. It is not backup, and the difference only shows on your worst day.
| What happens | Drive, OneDrive or a synced folder | SimbaVault Backup |
|---|---|---|
| Someone deletes a folder by mistake | It disappears from every machine in seconds. Roughly 30 days in the bin, if anyone notices in time. | Every day is kept. Pick a date before it happened and take the folder back. |
| Ransomware encrypts your files | The encrypted versions sync everywhere, overwriting the good ones. | Encrypted copies, saved offline, that nothing on your network can alter, with every earlier day still sitting there. |
| A laptop is stolen | Whatever sat in the synced folder is safe. Everything else goes with the laptop. | Everything agreed at setup comes back, wherever on the machine it was kept. |
| A server, PC or database crashes | Documents in Drive survive. The machine, its databases and its settings do not, because they were never in Drive. | Whole-machine copies, snapshots, database copies taken cleanly, and a rebuild onto different hardware. |
| Someone leaves and their account is closed | Their files go with the account unless ownership was transferred first. | That machine's history stays in your backup regardless. |
| Your Microsoft 365 mail | Microsoft keeps the service running. Under their own terms, your data is your responsibility. | Mail, OneDrive, SharePoint and Teams backed up separately, on your retention. |
Keep using Drive. It is good for working together on documents. This sits underneath it and catches what it was never built to catch.
Frequency and schedules
Your business does not run on one clock. Neither should your backup.
Nightly is a default, not a rule. You tell us which systems matter and how often, and each one runs to its own schedule, inside a window you choose.
The finance server, every hour
Systems where an hour of re-keying is real money back up through the working day, not only at night.
Design and CAD machines, once overnight
Large files, one copy a day, running at 11pm when nobody is competing for the line.
Databases, continuously
Accounting, patient and case systems that are open all day get a clean copy without anyone stopping work.
Laptops, whenever they connect
Field machines back up when they reach a network, instead of missing a schedule they were never on.
If your line is tight, we throttle or pause during working hours and catch up after them. You set the window; we stay inside it.
How far back you can go
Retention, in plain terms.
Retention is simply how far back you can reach. You choose it per system, and you can keep short-term copies close and long-term copies for the auditor.
| Copies kept | For how long | What it is there for |
|---|---|---|
| Every day | 30 days | The mistake nobody noticed until Tuesday |
| Every week | 12 weeks | The problem you only spot in a monthly report |
| Every month | 12 months | The audit, the dispute, the year-end |
| Every year | up to 7 years | Whatever your regulator or your lawyer requires |
Copies are deleted automatically when their period ends, and the deletion is recorded, so you are not quietly paying to store 2019 forever.
Reports: what lands in your inbox
You should never have to wonder whether it ran.
Backups die quietly in March and are discovered in September. Ours report to you whether or not you ask.
Every morning
A one-line summary per site: what ran, what succeeded, what failed, and how much changed overnight.
Every month
The full report: jobs, storage used, restores performed, the restore-test result, and every access to your data with a name against it.
The moment something fails
A failed job raises an alert with our desk the same morning. We ring you. You should not be the one chasing us.
Whenever you want to look
A portal showing every protected machine, its last successful backup, and the list of days you can restore from.
Encrypted before it leaves the network
Encrypted on your own machine, with a key you hold.
Your data is encrypted on your own hardware before anything crosses the internet, and it stays encrypted where we keep it.
You hold the key alone
We cannot read your files. We also cannot recover your key: lose it and the copies are unreadable, by us or anyone else.
Once it's written, it's written
Nobody can change the copy. Not your staff. Not an attacker. Not us.
Ransomware goes after the backup first, because a business with a working backup does not pay. So every copy is locked at the moment it is written. For the whole of the retention period you chose, it cannot be altered or deleted: not by a member of your staff, not by an attacker holding your administrator password, and not by our engineers.
The industry word for this is immutable. If another provider uses it, that is what it ought to mean. So ask them one question: can an administrator override it? On a great many setups, they can.
Scope
What a backup plan can cover.
So you know before you buy rather than after.
Can be protected under a backup plan
- Files, folders and shared drives on every machine we set up
- Whole-server copies: Windows and Linux, physical or virtual
- VMware, Hyper-V, Proxmox and KVM virtual machines
- Microsoft 365 and Google Workspace: mail, OneDrive, SharePoint, Teams
- SQL Server, MySQL, PostgreSQL and Exchange, copied cleanly while in use
- NAS shares and staff laptops
Handled by a different service
- Somewhere to run while yours is repaired. That is disaster recovery, priced on how fast you need to be back.
- Rebuilding a whole environment, applications and settings included. That is a managed server arrangement.
- Your CCTV footage. Recorders need a different kind of copy. That is Simba CCTV CloudVault.
Plans
Priced on what you protect and how far back you keep it.
Setup, the first tested restore and the monitoring are in every plan. Need more than the plans allow? Customized is built around you. Tell us what you run and we'll quote the right one, usually the same day.
| Starter | Most chosenBusiness | Professional | Customized | |
|---|---|---|---|---|
| Protected data | Up to 250 GB | Up to 1 TB | Up to 2 TB | More than 2 TB, sized to you |
| Backup frequency | As per your schedule needs, e.g. every 1, 3, 6 or 8 hours | As per your schedule needs, e.g. every 1, 3, 6 or 8 hours | As per your schedule needs, e.g. every 1, 3, 6 or 8 hours | As per your schedule needs, e.g. every 1, 3, 6 or 8 hours |
| Encrypted copies | Yes | Yes | Yes | Yes |
| File and folder restore | Yes | Yes | Yes | Yes |
| Restore to new hardware | Yes | Yes | Yes | Yes |
| Restore testing | Annual | Quarterly | Monthly | As agreed |
| Quote | Get a quote about the Starter plan | Get a quote about the Business plan | Get a quote about the Professional plan | Talk to us about the Customized plan |
How it starts
From first call to protected.
Step 1
Tell us what you run
A short call, or send a list. We size it and quote, usually the same day.
Step 2
We set it up
On site or remotely, wherever you are.
Step 3
We restore a file while you watch
Before we leave. An untested backup is a hope, not a plan.
Step 4
It runs, and we watch it
To your schedule, with a report every morning. If a job fails, you hear it from us first.
In plain English
The words the industry uses, and what they actually mean.
You will hear these from every vendor you talk to, including us. Here is what to check when you do.
| The word | What it means | What to ask |
|---|---|---|
| Versioning | Each day's copy is kept separately instead of overwriting yesterday's. | How many days back can I go? |
| Retention | How far back you can reach. | Is it the same for every system, or set per system? |
| Immutable | Once written, a copy cannot be changed or deleted until its period ends. | Can an administrator override it? |
| Incremental | After the first copy, only what changed is sent, which is why it is quick. | What does the first full copy do to my line? |
| Application-aware | A database copied while people are still working in it, without corrupting it. | Does that cover my accounting or patient system? |
| Bare-metal restore | Putting a whole machine back on different hardware, operating system and all. | Can I watch you do it before I sign? |
| RPO | How much work you would lose. Hourly backups mean at most an hour. | What is mine, per system? |
| RTO | How long until people are working again. | Is that a measured figure or a hope? |
Common questions
Before you ask us.
- Can we set our own backup times?
- Yes, per system. Hourly for the systems that earn money, overnight for the ones that do not, continuous for databases. You also set the window we are allowed to use your line in.
- How many previous versions do you keep?
- Every day within your retention, and weekly and monthly copies beyond it if you want them. You can see the list of available dates in the portal before you ask for anything back.
- Who can read our data?
- Nobody without your key. It is encrypted on your machine before it leaves your network, and it stays encrypted with us. You hold the key, so we cannot read your files, and we cannot recover the key for you either.
- Can you back up servers you don't host?
- Yes. On-premise servers, VPSs elsewhere, other people's clouds, Microsoft 365. We do not need to host it to protect it.
- How long does a restore take?
- A single file, minutes. A whole server depends on its size and your line. We give you the realistic figure for your setup when we quote, and we publish what we actually achieved last year.
- What happens when we outgrow this?
- Backup answers “will I get my data back”. When the question becomes “how long can I afford to be shut”, that is disaster recovery, and it builds on this.
One bad morning is all it takes.
Send us a list of what you run (how many computers, which servers, whether there is a database) and we will size it, price it, and tell you what we would protect first.
- Every day kept
- Encrypted before it leaves your network
- Copies nobody can change
- A restore tested at setup
Explore other services
Web Hosting
NVMe hosting with cPanel and free SSL.
Learn more →
Business Email
Secure email on your own domain.
Learn more →
Virtual Private Servers
Guaranteed resources, full root access.
Learn more →
Disaster Recovery
A standby site and a rehearsed way to get there.
Learn more →
CCTV CloudVault
Off-site copies of your camera footage.
Learn more →
Managed Services
24/7 monitoring, NOC and SOC.
Learn more →