All demos

Demo · Cloud

A bad day, and the way back.

A backup only counts if your files come back from it. Pick one of three bad days, choose a copy from before it went wrong, restore it and check that the file opens.

  • About 2 minutes
  • Made-up business, made-up customers
  • Runs in your browser. Nothing is sent.

Three bad days at Example Drain Co.

Pick a bad day and read what happens. Then restore from the backup: choose a copy from before it went wrong, restore it and check that the file opens. Or press Play to watch it done.

DemoA made-up business, three made-up bad days and a scripted restore. The screens are simplified illustrations, not any real backup product. Nothing here touches a real file.

Pick a bad day

Bad day 1 is picked: ransomware on the front-desk PC. Press Play to watch the way back, or pick a restore point yourself.

Backup and recoveryExample Drain Co.Demo

Pick a copy and restore it

From the cloud backup, off-site

Restore points, newest first

Simplified illustration. Made-up business, made-up files.

Bad day 1 of 3

Ransomware locks the front-desk PC

Tuesday the 15th, 2:10 PM

What happens

  1. A ransom note fills the screen on FRONT-DESK, minutes after the office manager opened an “invoice” attachment. Files in the shared Office folder now end in “.locked”.
  2. The office manager pulls the network cable, leaves the PC on and calls the owner.
  3. The owner calls Callsmith. Nobody pays, and nobody replies to the note.
  4. The hourly backup copies the locked files as new versions. The older versions are kept, untouched.
  5. Restore the Office folder from the last copy before 2:10 PM. FRONT-DESK stays unplugged until it’s wiped and set up again.

From the written recovery plan

If a screen says your files are locked

  1. Pull the network cable or switch off Wi-Fi. Leave the computer on.
  2. Call the owner, then Callsmith. Don’t pay and don’t reply to the note.
  3. Restore from the last copy before it started. Wipe the computer and set it up again before it goes back online.

Restore points for the Office folder

  1. Tue 15th, 3:00 PM Locked files Made after the attack
  2. 2:10 PM Ransomware hits FRONT-DESK
  3. Tue 15th, 2:00 PM Last clean copy The one to restore
  4. Tue 15th, 1:00 PM Clean
  5. Tue 15th, 12:00 PM Clean
  6. Mon 14th, 11:00 PM Clean Nightly backup

Restored: the whole Office folder, 1,284 files, from Tuesday at 2:00 PM, back into the shared folder. Then the owner opened this week’s jobs to check them.

Jobs this week.xlsx, restored from Tuesday 2:00 PM
DayCustomerJobPrice
MonCustomer 4, unit 4BRunning toilet repair$149
TueCustomer 1, 123 Example StWater heater, 50-gal gas, installed$1,850
WedCustomer 3, 9 Cedar CtCamera inspection$249
ThuCustomer 4, unit 2CDrain clearing, tub$189
SatCustomer 2, 48 Maple AveDrain clearing, kitchen sink$189

Not in this copy: anything saved between 2:00 and 2:10 PM. The office manager re-entered one booking by hand.

Test restore logged: the owner opened the file and it looked right.

Bad day 2 of 3

The technician’s laptop is stolen from the truck

Thursday the 17th, 12:40 PM

What happens

  1. The technician’s laptop backs up as usual, between two jobs.
  2. The technician comes back to the truck at Customer 4’s apartment building. A window is broken and his laptop bag is gone.
  3. The technician calls the owner, who signs the laptop out of the business email and files, and changes the technician’s password.
  4. The technician reports the theft to the police, with the serial number from the recovery plan.
  5. A new laptop for the technician. His files come back from the last copy, Thursday at 11:00 AM.

From the written recovery plan

If a laptop or phone is lost or stolen

  1. Call the owner. The owner signs it out of business email and files, and changes the password.
  2. Report it to the police. Serial numbers are on the last page of this plan.
  3. Set up a replacement and restore the files from the last copy.

Restore points for the technician’s laptop

  1. Thu 17th, 2:00 PM Didn’t run Laptop not reachable
  2. Thu 17th, 1:00 PM Didn’t run Laptop not reachable
  3. 12:40 PM Laptop found stolen
  4. Thu 17th, 11:00 AM Last copy The one to restore
  5. Thu 17th, 9:00 AM Complete
  6. Wed 16th, 4:00 PM Complete

Restored: everything from the technician’s laptop, 3,819 files, from Thursday at 11:00 AM, onto his new laptop. Then the technician opened his job notes to check them.

Job notes.xlsx, restored from Thursday 11:00 AM
DateCustomerJobNotes
Mon 14Customer 4, unit 4BRunning toiletNew flapper and fill valve
Tue 15Customer 1Water heater, 50 galDrain pan added, old one hauled
Wed 16Customer 3Camera inspectionClay pipe, roots. Quote to the owner
Thu 17Customer 4, unit 2CSlow tubCleared, hair in the trap

Not in this copy: notes the technician typed after 11:00 AM on Thursday. He re-typed two lines from memory.

Test restore logged: the technician opened the file and it looked right.

Bad day 3 of 3

The office manager deletes “Customers 2025”, and the sync deletes it everywhere

Wednesday the 16th, 4:32 PM

What happens

  1. The office manager tidies the shared Office folder. She deletes “Customers 2025.xlsx”, thinking it’s an old copy, then empties the recycle bin.
  2. The sync does what it’s built to do: the file disappears from the owner’s laptop and from FRONT-DESK too.
  3. The owner goes to look up Customer 3’s address. The file is gone on every computer.
  4. The office manager checks the shared folder’s recycle bin. It’s empty.
  5. Restore the file from the backup: a separate copy that the sync can’t reach.

From the written recovery plan

If a file or folder is deleted

  1. Look in the shared folder’s recycle bin first.
  2. If it isn’t there, restore it from the backup. Pick the last copy from before it was deleted.
  3. Open the restored file to check it, then tell whoever needed it.

Why the sync didn’t save it

Sync keeps every computer the same, so a delete on one is a delete on all.

  • FRONT-DESKGone
  • Shared folderGone
  • Owner’s laptopGone

Why the backup still has it

A backup is a separate copy that keeps older versions. Deleting the file didn’t touch it.

Wed 4:00 PM copy: the file is there

Restore points for the Office folder

  1. Thu 17th, 8:00 AM File not in it
  2. Wed 16th, 11:00 PM File not in it Nightly backup
  3. Wed 16th, 5:00 PM File not in it
  4. 4:32 PM Office manager deletes the file
  5. Wed 16th, 4:00 PM Last copy with the file The one to restore
  6. Wed 16th, 3:00 PM Has the file
  7. Tue 15th, 11:00 PM Has the file Nightly backup

Restored: Customers 2025.xlsx, from Wednesday at 4:00 PM, back into the shared folder. The sync then put it back on every computer, and the office manager opened it to check it.

Customers 2025.xlsx, restored from Wednesday 4:00 PM
CustomerPhone or emailAddressLast job
Customer 1(555) 555-0187123 Example StWater heater
Customer 2[email protected]48 Maple AveKitchen sink
Customer 3[email protected]9 Cedar CtCamera inspection
Customer 4[email protected]Units 4B and 2CToilet and tub
Customer 6(555) 555-0163Not given yetNew caller

Not in this copy: any change made to the file between 4:00 and 4:32 PM. The office manager hadn’t touched it that afternoon.

Test restore logged: the office manager opened the file and it looked right.

In this demo a restore takes seconds. A real one depends on how much data there is and on the internet connection: one file comes back quickly, a whole computer can take hours.

Backup monitor

The 11 PM nightly backup, last 14 nights. The hourly copies are watched the same way.

13 of 14 ran
  1. 1Tuesday the 1st: ran
  2. 2Wednesday the 2nd: ran
  3. 3Thursday the 3rd: ran
  4. 4Friday the 4th: ran
  5. 5Saturday the 5th: ran
  6. 6Sunday the 6th: ran
  7. 7Monday the 7th: ran
  8. 8Tuesday the 8th: ran
  9. 9Wednesday the 9th: didn’t run
  10. 10Thursday the 10th: ran
  11. 11Friday the 11th: ran
  12. 12Saturday the 12th: ran
  13. 13Sunday the 13th: ran
  14. 14Monday the 14th: ran

Night of the 9th, WednesdayDidn’t run

  1. Didn’t run. FRONT-DESK was switched off.
  2. An alert email went to the owner.

    Missed backup: FRONT-DESK, night of the 9th

    From Backup monitor · To the owner

    Last night’s 11 PM backup of FRONT-DESK didn’t run because the PC was switched off. The laptops and the shared Office folder backed up as usual. Please leave FRONT-DESK on tonight so it can catch up.

  3. Ran, and caught up on both days’ changes.

3-2-1: where the copies live

The simple rule the backup follows.

At the office

Working filesOn the computers and laptopsCopy 1
Backup driveLocked in the office closetCopy 2

Off-site

Cloud backupIn a separate accountCopy 3
  • 3copies The working files and two backups.
  • 2kinds of storage A drive in the office and the cloud.
  • 1off-site The cloud copy, out of reach of a fire, flood or break-in at the office.

Check your own setup with the free Backup health check Seven quick questions, about a minute.

In real use

What’s real, and what’s made up.

The same in real use

Backups that run by themselves on a schedule, older versions kept, an alert when a run fails, every restore opened by a person and logged, and a written recovery plan you can follow without us.

Made up for this demo

Example Drain Co., its files and all three bad days. Here a restore takes seconds. A real one depends on how much data there is and on your internet connection, and we tell you what to expect before you need it.

What stays with you

You choose what gets backed up, how often, how long older versions are kept and who gets the alerts. No backup brings back work saved after its last copy, so your plan says what could be lost. The work is scoped and quoted in writing.

Would your backup bring it back?

Tell us what you have today. We’ll say what we’d back up, where the copies would live, how a restore would work and what it would cost, in writing, before anything changes.