Automate backups: backups you can actually rely on
You automate backups with a workflow that backs up all important data sources on schedule, such as Microsoft 365, servers, databases and cloud storage, distributes copies following the 3-2-1 rule, checks every backup for completeness and tests restores regularly. Failures are reported immediately. In the worked example it saves about 14 h of checking work a month.
- Time saved in the worked example
- approx. 14 h per month
- Delivery
- 3 to 5 working days
- Typical systems
- Microsoft 365, Google Workspace, Synology
- Fixed price
- from €990
, Rouven Jahnke
Flow: Backups
5 steps-
Start backup
On schedule, for every data source
-
Distribute copies
Local, offsite, immutable
-
Verify success
Completeness and integrity
-
Test restores
Regularly, automatically, logged
-
Review report
Owners sign off the test report
Green runs automatically. Orange is decided by a person.
Where time gets lost today
- Backups run, but nobody checks them
- Restores have never been tested
- Cloud data is wrongly assumed to be backed up
Most companies have some kind of backup. How good it is shows only in an emergency: after ransomware, an accidentally deleted folder or a failed server. Then it often turns out that backups have failed for weeks or can’t be fully restored.
A common misconception concerns cloud services: Microsoft 365 or Google Workspace keep their services running. Under their shared responsibility model, protecting your data from deletion, user error or encryption by malware is largely your job.
How the automation works
The workflow orchestrates backups of all important sources on schedule: Microsoft 365 or Google Workspace, servers, databases, NAS and cloud storage. Copies follow the 3-2-1 rule: three copies, two different media, one offsite, ideally immutable against ransomware.
After each backup the workflow checks that it is complete and readable. Failures, unusually small backups or missing runs are reported immediately, not at the next glance at the log.
At regular intervals it restores samples into a test environment and logs the result. Only a tested restore turns a copy into a backup you can rely on.
What your team still decides
Owners sign off the regular test reports and decide in an emergency what to restore when. You set retention periods and deletion rules, with your data protection officer where needed.
Calculate your savings
Adjust the values to your company. The calculation runs only in your browser; nothing you enter is transmitted.
- Working time saved per month
- – h
- Savings per month
- –
- Savings per year
- –
Excludes running costs for hosting and AI usage. You receive the implementation cost as a fixed price after the intro call.
Formula
Hours saved/month = (Jobs/day x 22 x 8 min + Jobs x 22 x Volume factor x 3 min + Copies x 2 min) x Automation rate / 60
Worked example
The calculator above starts with these assumptions. They are example values, not averages from studies.
- Backup jobs per day
- 5
- Data volume
- 100 GB
- Retention copies
- 7
- Share of work automated
- 85 %
- Labour cost per hour (fully loaded)
- 60 €
Result: about 14 h less manual work per month, roughly €820 a month or €9,800 a year.
Before and after
| Aspect | Today, by hand | With the workflow |
|---|---|---|
| Backup | Runs somehow | On schedule, for every source |
| Checks | Occasional look at logs | Every backup verified automatically |
| Restore | Never tested | Tested and logged regularly |
| Ransomware protection | Copies on the same network | Offsite, immutable copy |
Frequently asked questions
Does Microsoft 365 need backing up?
Yes, this is often underestimated. Microsoft keeps the services running but protects your data only to a limited extent against deletion, user error or encryption by malware. A separate backup of mailboxes, OneDrive, SharePoint and Teams is recommended.
What is the 3-2-1 rule?
Three copies of your data, on two different storage media, one of them offsite. In addition, at least one copy should be immutable or offline so ransomware can’t encrypt it too.
How often are restores tested?
We set that by how critical the data is; monthly samples and a full test each quarter are typical. Every test is logged, which also helps with audits by insurers or customers.
Does this replace our IT provider?
No. The workflow makes sure backups run, are verified and tested, and reports problems. Backup architecture and emergency restores are coordinated with your IT provider where needed.
What does this workflow cost and how quickly is it live?
Implementation is a fixed price from €990; the exact price is set after the free intro call and depends on the number of connected systems and exceptions. Typical delivery time for this workflow: 3 to 5 working days. Running costs for hosting and, where used, AI usage are quantified in the proposal.
Backups: free intro call
Describe a process that eats time today. I’ll tell you honestly whether automating it pays off, what it would look like and what it costs.
- We walk through your process together, ideally on screen.
- You learn which step has the biggest leverage and what it takes.
- You receive a fixed-price proposal within 48 hours. No obligation.
Pick a time in the calendar
Loading calendar…
Thanks, your message arrived.
You’ll get a confirmation email. I’ll reply within 24 hours.
Your reference number: