# Backup and disaster recovery | Eightstep > Backups kept locally and in Azure, checked every day and tested every month, with your servers ready to run in Azure to agreed recovery targets. Source: https://eightstep.com.au/backup-and-disaster-recovery # Backup and disaster recovery **Back at work in hours, not weeks** Your servers and data backed up locally and in Azure, checked every day, tested every month, and ready to run in Azure to the recovery targets you set. [Get started](https://eightstep.com.au/contact) [See how it works](https://eightstep.com.au/backup-and-disaster-recovery#backup) ## Trusted by Australian organisations ## Backup ### Backups in more than one place Every protected server and its data backed up where it runs, then copied over a secure link to Azure, so a lost file is back in minutes and nothing depends on a single copy. ### Quick file restores Recent recovery points close at hand, so a deleted or overwritten file is back in minutes. ### No tapes or USB drives Backups run on their own and land in Azure, with nothing to swap, carry or store. ### Light on your servers The backup does the heavy lifting itself, so your servers keep working at full speed while it runs. ### Light on your links Only what's changed is sent, so storage and data links cost less. ### Kept in Australia Copies held in Microsoft's Azure datacentres in Australia, in a separate region from your own systems. ### Microsoft 365 alongside Email, files and Teams can join the same design through our Microsoft 365 backup service. ## Disaster recovery ### Recovery in Azure Your servers replicated to Azure in near real time, ready to run there to the recovery targets you've agreed, so your people are working again in hours, not weeks. ### Targets you set How quickly each server must be back, and how much recent work could be lost, agreed server by server and written into your policy. ### A policy that keeps up Your backup and DR policy changes as your business does, and our engineers work from it day to day. ### A separate region Recovery runs in Azure, away from your production systems, so one site's trouble never takes both. ### Tested every year A full recovery test each year, worked through your recovery checklist. ### A written recovery process Step-by-step recovery and test procedures, and checklists to confirm everything works afterwards. ### Servers that match Recovery servers are specified to mirror your production servers. ## Managed for you ### Checked every day A person reviews every backup each weekday and fixes anything that needs it, so you can trust that a restore will work when you need one. ### Monthly restore tests Every month we restore a random sample of your data, to prove backups can be recovered. ### Annual recovery test Once a year we recover your servers in Azure, confirm they work, then remove the test servers to keep costs down. ### Policies maintained We look after the backup and replication policies, and make routine changes as your needs shift. ### Software included The backup software is part of the service, kept up to date by us. ### Documented Your backup configuration, recovery process and diagrams kept current alongside the rest of your IT documentation. ### Targets we answer to We're accountable for restoring to the recovery targets in your policy. ## However your servers run On premises, in the cloud or both, the design follows your servers and brings recovery together in Azure. ### Already in the cloud Servers running in the cloud are backed up where they run, then replicated over a secure link to Azure in a geographically separate region. - Backups taken where your servers already run - A second copy in a separate region - Spread across three datacentres in Azure ### In your own server room Backups land on a local storage device first, for the fastest restores, then replicate over a secure link to Azure. - A local copy for quick restores - A second copy in Azure - Recovery in Azure if your server room is out of action ### A bit of both Servers on premises back up locally first; servers in the cloud back up to a separate region. Everything comes together in Azure. - One design across both - Each server backed up where it runs - Recovery for all of them in Azure ## Proven, not assumed Every backup checked, every month restored, every year recovered in full. Daily human checks of every backup, with anything that fails fixed 12 restore tests a year, on a random sample of your data 1 full disaster recovery test a year, through your checklist Hours to have your people working again, not weeks ## Set up in four stages A short project puts everything in place and proves it works before the managed service begins. Step 1 ### Plan We agree a recovery time and a recovery point for each server, and write them into your backup and DR policy for sign-off. Step 2 ### Build We set up the backup platform, storage in Azure, a local storage device if you need one, and the policies to meet your targets. Step 3 ### Test and document We restore files and whole servers, start every protected server in Azure, and write up the recovery process and checklist. Step 4 ### Review You review the results and sign off, and the managed service begins. ## Works well with Services that round out backup and disaster recovery. ### [Microsoft 365 backup](https://eightstep.com.au/microsoft-365-backup) Email, files and Teams, backed up and easy to restore. ### [Essential 8](https://eightstep.com.au/essential-8) See how your environment lines up with the ACSC Essential Eight. ### [Internet and data](https://eightstep.com.au/internet-and-data) Internet and links between your sites, managed with the carrier. ## Questions, answered Anything else? [Ask us directly](https://eightstep.com.au/contact). **How is it priced?** A one-off setup project, then a fixed monthly fee for the managed service, which includes the backup software. Azure storage and recovery resources are billed each month on what you use, so that part grows with your data. If you keep servers on premises, you'll also buy a local storage device for the first copy. **What are recovery time and recovery point?** Recovery time is how quickly a server must be running again. Recovery point is how much recent work you could afford to lose, measured in time. We agree both for each server and write them into your backup and DR policy. **What happens in a disaster?** We restore your servers and data in Azure to the targets in your policy, following your written recovery process. The recovery work itself is charged as time and materials unless we've agreed otherwise. **Is Microsoft 365 included?** Microsoft 365 can be part of the same design, through our [Microsoft 365 backup](https://eightstep.com.au/microsoft-365-backup) service, which is a separate agreement. **Does this keep the whole business running?** It gets your servers and data running in Azure. Business continuity goes further: where your people work from, how they connect, how regional sites and vendors reach the recovered systems, and how everyone stays in touch. We'll point those out as we plan, but they sit outside this service. **How does it fit with Managed IT Services?** Managed IT Services checks backups and tests restores wherever a backup solution is in place. This service provides that backup, plus disaster recovery: the recovery targets, the replication to Azure and the annual recovery test.