Backup Setup & Disaster Recovery
Disaster recovery plan and runbook, on site
If our server died tomorrow, nobody knows what we would do.
If our server died tomorrow, nobody knows what we would do.
A backup gives you the data; a recovery plan tells you what to do with it. When a server fails or ransomware hits, people need to know which system comes back first, where the backups are, who has the passwords and who to call. Working that out under pressure costs time and leads to mistakes. It also helps answer questions from insurers and clients.
What the technician does
- List critical systems, data and who depends on them
- Agree recovery priorities and test the key restore steps
- Write a plain-English runbook with contacts and logins
Keep a printed copy of the runbook offsite - it is no use if it is only on the server that failed.
About disaster recovery plan and runbook
We list your critical systems, agree recovery priorities and acceptable downtime, and test the key restore steps so the plan reflects reality. The runbook covers backup locations, restore procedures, vendor contacts, licence details and how to notify staff and clients. It is written for a manager to follow, not just a technician, and kept somewhere safe. We review it with you so the people named in it know their part.
What usually causes it
- A near-miss with a failed server or drive
- Insurance or client requirements
- IT knowledge held by one person
- Ransomware incidents in the same industry
Before we arrive
- A list of the systems and software the business cannot run without
- Admin access to servers, NAS units and Microsoft 365
- Details of any existing backup software or cloud storage account
- Who should receive backup alerts and keep the recovery plan
What a visit looks like
When you book disaster recovery plan and runbook, you tell us what's going on and we reply with a time that suits you and a price. Nothing starts until you're happy with both.
On the day, the technician arrives, looks at the problem in person and confirms the plan with you before starting. If something turns out different from what was expected - a part is needed, or the cause is somewhere else - we stop and agree the change with you first.
When the work is done we test it with you, show you what was changed, and leave the area tidy. For business jobs we note what we did, so there is a record for whoever looks after your IT next.
Pricing
Each disaster recovery plan and runbook job is priced before work starts. The price depends on what's involved - the size of the site, the equipment, and whether parts are needed - so the quickest way to a number is to tell us about the job on the booking form.
There is no contract and no monthly fee. You book the job you need and pay for that job.
Disaster recovery plan and runbook: questions
Do we need a recovery plan if everything is in the cloud?
Yes. You still need to know how to recover deleted data, regain access to a compromised account and keep working if the internet or a key service is unavailable.
How often should the plan be reviewed?
Whenever systems change significantly, such as a new server, software or office. A quick yearly review keeps contacts and steps up to date. A short test of one restore step is worth doing at the same time.
Do you do disaster recovery plan and runbook on site?
Yes. We come to businesses and homes across Auckland and Hamilton and do the work where the equipment is.
How much does disaster recovery plan and runbook cost?
It depends on what's involved. Tell us about the job on the form and we'll confirm the price before any work starts.