Local IT for Lake Macquarie, Newcastle, the Central Coast & the Hunter
Mon–Fri, 9am–5pm
Get remote support now
Local IT for Lake Macquarie, Newcastle, the Central Coast & the Hunter
Keep it safe
Backup and Recovery
We back up files, email and servers, then rehearse and time the restore. That way ‘how long until we’re back’ has an answer before the bad day comes.
Keep it safe
Backup and Recovery
We back up files, email and servers, then rehearse and time the restore. That way ‘how long until we’re back’ has an answer before the bad day comes.
Keep it safe
Backup and Recovery
We back up files, email and servers, then rehearse and time the restore. That way ‘how long until we’re back’ has an answer before the bad day comes.
The problem
The risk in backups that have never been restored
Most businesses have something running. A NAS in the comms cupboard, a sync that came with the laptops, a job someone set up years ago. It reports success every night, and success only means the copy was made. It doesn’t mean the copy opens.
The questions that matter only get asked on the worst morning: how far back does this go, what comes up first, who holds the credentials, and how long until people can work again. We would rather answer those on a quiet Tuesday.
The problem
The risk in backups that have never been restored
Most businesses have something running. A NAS in the comms cupboard, a sync that came with the laptops, a job someone set up years ago. It reports success every night, and success only means the copy was made. It doesn’t mean the copy opens.
The questions that matter only get asked on the worst morning: how far back does this go, what comes up first, who holds the credentials, and how long until people can work again. We would rather answer those on a quiet Tuesday.
The problem
The risk in backups that have never been restored
Most businesses have something running. A NAS in the comms cupboard, a sync that came with the laptops, a job someone set up years ago. It reports success every night, and success only means the copy was made. It doesn’t mean the copy opens.
The questions that matter only get asked on the worst morning: how far back does this go, what comes up first, who holds the credentials, and how long until people can work again. We would rather answer those on a quiet Tuesday.
What’s included
Everything we do to make restores work
We recheck every item on this list on a set schedule after setup.
Current backup audit
What’s covered, what quietly isn’t
Scheduled test restores
We open the restored files
Documented recovery order
What comes back first, and why
Recovery time estimate
In hours, measured not guessed
Microsoft 365 backup
Microsoft doesn’t keep it for you
Offsite copy
One fire can’t take both
Immutable retention
Ransomware can’t delete it either
Server image backups
Captures the whole machine
Monitored failure alerts
A person reads them
Annual recovery drill
Timed, with your staff involved
What’s included
Everything we do to make restores work
We recheck every item on this list on a set schedule after setup.
Current backup audit
What’s covered, what quietly isn’t
Scheduled test restores
We open the restored files
Documented recovery order
What comes back first, and why
Recovery time estimate
In hours, measured not guessed
Microsoft 365 backup
Microsoft doesn’t keep it for you
Offsite copy
One fire can’t take both
Immutable retention
Ransomware can’t delete it either
Server image backups
Captures the whole machine
Monitored failure alerts
A person reads them
Annual recovery drill
Timed, with your staff involved
What’s included
Everything we do to make restores work
We recheck every item on this list on a set schedule after setup.
Current backup audit
What’s covered, what quietly isn’t
Scheduled test restores
We open the restored files
Documented recovery order
What comes back first, and why
Recovery time estimate
In hours, measured not guessed
Microsoft 365 backup
Microsoft doesn’t keep it for you
Offsite copy
One fire can’t take both
Immutable retention
Ransomware can’t delete it either
Server image backups
Captures the whole machine
Monitored failure alerts
A person reads them
Annual recovery drill
Timed, with your staff involved
When it happens
How a recovery runs, step by step
We agree the recovery order well before anything goes wrong, and write it down.
01
Contain, then assess
Nothing gets restored until we know what happened and when. Restoring into a network that’s still compromised just hands the new copies over too. We find the last clean point, and the way in, before anything comes back.
02
Follow the order
The runbook written on a quiet day decides what returns first. That’s usually whatever invoicing and payroll run on, then shared files, then everything else. The worst time to debate priorities is with the whole staff standing around.
03
Get people working
Staff go back to work before the restore finishes. Critical systems come up first while the bulk of the data copies behind them. The slow part is the volume of data, and your last drill tells us how long that takes.
04
Close the gaps
Afterwards we write up what dragged and what was missing, fix both, and update the runbook. Then the next test restore runs against the new version. Every recovery finds something the last drill missed, and the runbook improves because of it.
When it happens
How a recovery runs, step by step
We agree the recovery order well before anything goes wrong, and write it down.
01
Contain, then assess
Nothing gets restored until we know what happened and when. Restoring into a network that’s still compromised just hands the new copies over too. We find the last clean point, and the way in, before anything comes back.
02
Follow the order
The runbook written on a quiet day decides what returns first. That’s usually whatever invoicing and payroll run on, then shared files, then everything else. The worst time to debate priorities is with the whole staff standing around.
03
Get people working
Staff go back to work before the restore finishes. Critical systems come up first while the bulk of the data copies behind them. The slow part is the volume of data, and your last drill tells us how long that takes.
04
Close the gaps
Afterwards we write up what dragged and what was missing, fix both, and update the runbook. Then the next test restore runs against the new version. Every recovery finds something the last drill missed, and the runbook improves because of it.
When it happens
How a recovery runs, step by step
We agree the recovery order well before anything goes wrong, and write it down.
01
Contain, then assess
Nothing gets restored until we know what happened and when. Restoring into a network that’s still compromised just hands the new copies over too. We find the last clean point, and the way in, before anything comes back.
02
Follow the order
The runbook written on a quiet day decides what returns first. That’s usually whatever invoicing and payroll run on, then shared files, then everything else. The worst time to debate priorities is with the whole staff standing around.
03
Get people working
Staff go back to work before the restore finishes. Critical systems come up first while the bulk of the data copies behind them. The slow part is the volume of data, and your last drill tells us how long that takes.
04
Close the gaps
Afterwards we write up what dragged and what was missing, fix both, and update the runbook. Then the next test restore runs against the new version. Every recovery finds something the last drill missed, and the runbook improves because of it.
Often paired with
Cyber Security
Ransomware is what most restores are for. Stopping it reaching the backup is cheaper than using one.
Learn more →
Managed IT
Under a Managed IT agreement we run the backup checks every month, so nobody has to remember.
Learn more →
Cloud Services
Moving into Microsoft 365 changes what needs backing up, and what Microsoft won’t keep for you.
Learn more →
Often paired with
Cyber Security
Ransomware is what most restores are for. Stopping it reaching the backup is cheaper than using one.
Learn more →
Managed IT
Under a Managed IT agreement we run the backup checks every month, so nobody has to remember.
Learn more →
Cloud Services
Moving into Microsoft 365 changes what needs backing up, and what Microsoft won’t keep for you.
Learn more →
Often paired with
Cyber Security
Ransomware is what most restores are for. Stopping it reaching the backup is cheaper than using one.
Learn more →
Managed IT
Under a Managed IT agreement we run the backup checks every month, so nobody has to remember.
Learn more →
Cloud Services
Moving into Microsoft 365 changes what needs backing up, and what Microsoft won’t keep for you.
Learn more →
We use Microsoft 365 and OneDrive. Isn’t that already backed up?
Not in the way most people mean. Microsoft keeps the service running, and what happens to your data inside it is your responsibility. Sync also copies deletions and encryption straight up to the cloud, and the recycle bin empties on a timer. A separate backup with its own retention is what covers that. Microsoft 365 and Google Workspace backup comes with Cloud Protect.
What does it cost?
It follows how much data you hold and how far back you want to be able to go, so we look first and then quote. A server with seven years of records costs more than a dozen laptops. Backup for Microsoft 365 or Google Workspace comes with Cloud Protect, from $20 per user a month. For servers and local data, we’ll put a real number against your volumes.
What happens if a restore fails on the day we need it?
Most failures show up in a test restore and get fixed there, which is why we run them. If one still fails on the day, we move to the second copy and tell you straight away what’s recoverable and what isn’t. Nobody can promise a restore never fails, and anyone who does is guessing.
What don’t you cover?
Anything we can’t get access to. Line-of-business systems a vendor hosts and won’t hand over, data sitting in someone’s personal account, and cloud apps with no export sit outside what we can protect until that changes. We put those gaps in writing during the audit, so you can decide what to do about them.
Are we locked in, and do we have to replace our hardware?
A 3-month minimum, then month to month. Existing gear stays if it’s sound. If your NAS works, we add an offsite copy to it and keep using it. The audit, the recovery order and the runbook are yours to keep, so if you leave, they go with you.
We use Microsoft 365 and OneDrive. Isn’t that already backed up?
Not in the way most people mean. Microsoft keeps the service running, and what happens to your data inside it is your responsibility. Sync also copies deletions and encryption straight up to the cloud, and the recycle bin empties on a timer. A separate backup with its own retention is what covers that. Microsoft 365 and Google Workspace backup comes with Cloud Protect.
What does it cost?
It follows how much data you hold and how far back you want to be able to go, so we look first and then quote. A server with seven years of records costs more than a dozen laptops. Backup for Microsoft 365 or Google Workspace comes with Cloud Protect, from $20 per user a month. For servers and local data, we’ll put a real number against your volumes.
What happens if a restore fails on the day we need it?
Most failures show up in a test restore and get fixed there, which is why we run them. If one still fails on the day, we move to the second copy and tell you straight away what’s recoverable and what isn’t. Nobody can promise a restore never fails, and anyone who does is guessing.
What don’t you cover?
Anything we can’t get access to. Line-of-business systems a vendor hosts and won’t hand over, data sitting in someone’s personal account, and cloud apps with no export sit outside what we can protect until that changes. We put those gaps in writing during the audit, so you can decide what to do about them.
Are we locked in, and do we have to replace our hardware?
A 3-month minimum, then month to month. Existing gear stays if it’s sound. If your NAS works, we add an offsite copy to it and keep using it. The audit, the recovery order and the runbook are yours to keep, so if you leave, they go with you.
We use Microsoft 365 and OneDrive. Isn’t that already backed up?
Not in the way most people mean. Microsoft keeps the service running, and what happens to your data inside it is your responsibility. Sync also copies deletions and encryption straight up to the cloud, and the recycle bin empties on a timer. A separate backup with its own retention is what covers that. Microsoft 365 and Google Workspace backup comes with Cloud Protect.
What does it cost?
It follows how much data you hold and how far back you want to be able to go, so we look first and then quote. A server with seven years of records costs more than a dozen laptops. Backup for Microsoft 365 or Google Workspace comes with Cloud Protect, from $20 per user a month. For servers and local data, we’ll put a real number against your volumes.
What happens if a restore fails on the day we need it?
Most failures show up in a test restore and get fixed there, which is why we run them. If one still fails on the day, we move to the second copy and tell you straight away what’s recoverable and what isn’t. Nobody can promise a restore never fails, and anyone who does is guessing.
What don’t you cover?
Anything we can’t get access to. Line-of-business systems a vendor hosts and won’t hand over, data sitting in someone’s personal account, and cloud apps with no export sit outside what we can protect until that changes. We put those gaps in writing during the audit, so you can decide what to do about them.
Are we locked in, and do we have to replace our hardware?
A 3-month minimum, then month to month. Existing gear stays if it’s sound. If your NAS works, we add an offsite copy to it and keep using it. The audit, the recovery order and the runbook are yours to keep, so if you leave, they go with you.
Get a quote for backup and recovery
Thirty minutes, onsite or remote. You keep the written summary whether or not you go ahead.
Get a quote for backup and recovery
Thirty minutes, onsite or remote. You keep the written summary whether or not you go ahead.
Get a quote for backup and recovery
Thirty minutes, onsite or remote. You keep the written summary whether or not you go ahead.