Skip to content

Local engineers in Perth, WA. Zero offshoring.

Menu

Backup & disaster recovery · Perth

Backups you’ve actually seen work.

Plenty of businesses find out their backups don’t work on the day they need them. We validate yours every business day, test a full recovery every year and write down how long getting back up takes. A failure becomes an inconvenience, not a crisis.

  • Daily Backups validated every business day
  • Yearly A full disaster recovery test, on record
  • In writing Recovery times for each system
A four-bay backup storage unit with green status lights on a shelf in an office comms cupboard.
Example test restore Passed
Accounts file server
Restored
Microsoft 365 mailboxes
Restored
Time to restore
42 min
Checked by
Sam

When something goes wrong

Same disaster. Very different outcome.

Everyone has backups until they need one. Pick a situation and see the difference testing makes.

Staff arrive on Monday to encrypted files and a ransom note.

Backed up, never tested

  1. 1 Backups encrypted tooThey sat on the same network as everything else.
  2. 2 Cloud copy is weeks oldThe sync stopped months ago. Nobody noticed.
  3. 3 Pressure to payWith no guarantee of getting anything back.
  4. 4 Weeks of rebuildingFrom email attachments, paper and memory.

Weeks lost, maybe more.

Tested with CCP

  1. 1 Offsite copy untouchedStored away from the network the ransomware reached.
  2. 2 Restore order agreedThe plan says what comes back first.
  3. 3 Critical systems firstPractice software and client files, then the rest.
  4. 4 Way in closedWe find how they got in and shut it.

Back in business. No ransom.

A client folder was deleted three weeks ago. Someone needs it today.

Backed up, never tested

  1. 1 Check the recycle binAlready emptied.
  2. 2 Retention too shortBackups only go back 14 days.
  3. 3 Ask MicrosoftBuilt-in retention isn’t a backup.
  4. 4 GoneRecreate it from email attachments.

Rebuilt from scratch.

Tested with CCP

  1. 1 Call usAn engineer finds it in the backup history.
  2. 2 Point-in-time restoreFrom before it was deleted, permissions intact.
  3. 3 Back where it wasOften within the hour.
  4. 4 Why it happenedWe check it was an accident, not an account problem.

Restored before lunch.

The server dies at 9:30am on a busy Tuesday.

Backed up, never tested

  1. 1 Order a replacementTwo-week lead time.
  2. 2 Restore never testedNobody knows how long it takes, or if it works.
  3. 3 Staff sent homeNothing to work on.
  4. 4 Partial recoverySome data comes back. Some doesn’t.

Two weeks, partly recovered.

Tested with CCP

  1. 1 Restore from backupCritical files brought back while hardware is sorted.
  2. 2 Known restore timeBecause the yearly test measured it.
  3. 3 Files deliveredAn engineer can bring a copy on-site.
  4. 4 Replaced properlyNew hardware quoted, set up and documented.

Working again the same morning.

A burst pipe floods the office overnight.

Backed up, never tested

  1. 1 Server in the comms cupboardNext to the only backup drive.
  2. 2 Files saved locallyOn laptops left on desks.
  3. 3 Insurance claimCovers the hardware, not the lost work.
  4. 4 Starting overClient records gone.

Hardware replaced. Data isn’t.

Tested with CCP

  1. 1 Offsite copy safeStored well away from the building.
  2. 2 Work from homeStaff sign in to cloud-backed files.
  3. 3 Laptops replacedNew devices set up and ready to sign in.
  4. 4 Plan followedEveryone knows their role. It’s written down.

Working from home by afternoon.

Your recovery plan, in writing

Four questions you should be able to answer today.

If your IT provider can’t answer these in writing, your backups are a hope, not a plan. Every CCP client gets them answered, and re-checked at every review.

  • 01

    What’s backed up?

    Servers, plus Microsoft 365 mail, OneDrive, SharePoint and Teams. Listed, not assumed.

  • 02

    Where are the copies?

    Offsite, away from your office and your network. We’ll tell you exactly where.

  • 03

    When was it last tested?

    Backups are validated every business day. The full recovery test date and result are on record.

  • 04

    How long to get back up?

    Recovery times for each system, measured in the yearly test. You know what a bad day costs.

What’s included

Backups that are watched, tested and written down.

Included in every managed IT plan. Server backups need suitable onsite storage, which we size with you.

  • Microsoft 365 backup

    Mail, OneDrive, SharePoint and Teams backed up separately. Built-in retention isn’t a backup.

  • Server backup

    Servers backed up offsite on a daily or agreed schedule.

  • Long retention

    Microsoft 365 data kept for up to seven years. Server retention agreed with you.

  • Daily validation

    Backups are checked automatically every business day. Failures get fixed, not filed.

  • Yearly recovery test

    A full disaster recovery test once a year, with the result recorded.

  • Recovery times in writing

    Real restore times for each system, reported after the first yearly test.

  • Point-in-time restore

    Bring back a file, mailbox or site as it was before it went wrong.

  • Search the history

    Find a lost email or document across the backup history.

  • Restores on request

    Deleted something? Call us and an engineer restores it.

  • Stop them getting in first

    Backups are the last line of defence. Our layered security is there to prevent the attack.

In our clients’ words

The day it matters, it works.

“Our primary server failed at 9:30am… Alex identified the problem, fixed it and personally delivered me a file backup by 11am.”

JC James Clough · property management

“Went into a panic today over a document that hadn't been updating and Sam spent time and managed to recover it.”

JS Jacqui & Steve Wood · Google review

Find out before you need to.

A short check tells you whether your backups would actually get you through a bad day.

  1. Step 1 · Free

    Backup check

    We look at what’s backed up, where it goes and when it was last tested.

  2. Step 2 · Within a week

    Written findings and a fixed quote

    Including any gaps you’d want to know about today, not after an incident.

  3. Step 3 · Ongoing

    Check, test, report

    Daily validation, a yearly recovery test and results at every review.

Doesn’t Microsoft 365 already back up our data?
How often do you test backups?
Would we survive a ransomware attack?
Are laptops backed up?
Where is our backup data stored?
What’s the difference between backup and disaster recovery?

Test your backups before a disaster does.

Book a free backup check with a Perth engineer. We’ll tell you what’s covered, what isn’t and how long a restore would really take. It’s yours to keep either way.

Or call (08) 9467 2269

What’s bugging you
Staff

A Perth engineer, not a salesperson, replies within one business day.