The worst time to discover that your backup and disaster recovery plan is inadequate is after the disaster has occurred. Companies may think they have a strong backup with redundancy only to find out it hasn't been operational for months. Others find out the hard way that staff have not been properly saving data to the server to be backed up daily. When their PC or notebook crashes, suddenly panic sets in.
There are several key questions to consider when developing your backup and disaster recovery strategies.
“Should we maintain our premise based backup or go totally to the cloud?”
“How much data can we afford to lose in a disaster?”
“How quickly do we need to be back up and fully operational?”
Boston Systems will walk you through the “pros and cons” of cloud vs. premise based backup and disaster recovery solutions. There are a number of things to consider. Ultimately, the decision rests on the level of risk you are willing to assume and your budget.
Recovery Point Objective (RPO) is the maximum targeted period in which data might be lost due to a major incident. It represents the period in time that the last backup was completed and successful. All data subsequent to that backup needs to be input again. The smaller the RPO, the least amount of potential data loss will be experienced.
Recovery Time Objective (RTO) is the amount of time the business can be without their server, without incurring significant risks or significant losses. The RTO is typically stated as “How long can your server be down before your day to day business is negatively impacted.” The shorter the RTO, the quickest recovery time. What you decide your RPO and RTO to be will directly impact your company’s IT budget. The smaller your RPO and RTO the more you will need to allocate out of your budget.
BSS can evaluate and test your plan, present backup system solutions and daily procedures to ensure your data is safe with minimal downtime without breaking your budget.