Case Study

Provision of Backup and Disaster Recovery Solution

Client Details
  • Multiple Councils and Corporate clients
The Challenge(s)
  • Ensure that all services, applications, and data is being backed up and can be recovered within an acceptable timeframe
  • Meeting BCP requirements
  • Keeping the costs down while making sure that the solution deployed is effective
  • Ongoing management and testing of backup and DR processes
The Solution
  • Carry out a baseline health check on the critical systems, infrastructure, and baseline core business applications. Consider cloud services (SaaS and M365)
  • Review BCP requirements, backup and DR processes and associated risks
  • Our approach is to ensure that backup and DR systems are upgraded with every production server compute and storage refresh.
  • Carry out workshop to review design considerations and provide specifications for required equipment (switching, WLAN and firewall); ensure that business continuity requirements are addressed to minimise any disruption to operations. Decide on long term archive management.
  • Consider the cloud-to-cloud options as well as on premise solutions. Identify limitations in the proposed solutions (capacity, link speeds, Internet service and WAN speeds etc)
  • We have deployed DR solutions utilising old production server compute and storage for DR as well as public or private cloud. In some cases, the backup and DR equipment is also refreshed with the production environment.
  • Configure the backup and relocation (and SAN level snapshotting) to meet BCP RPO, RTO and MAO requirements.
  • Provide detailed as-built documentation and training to staff including a maintenance and testing program.
  • Conduct annual Backup and DR Reviews as well as full BCP testing with the client’s IT team.
What did we learn?
  • Daily monitoring of backup and replication procedures is critical. Ensure that all backup processes are completing successfully. If neglected this can lead to a high-risk situation where a backup is not available when required leading to large data losses.
  • Regular recovery testing should be carried out at least quarterly and we recommend a full review of the processes annually.