Managed Disaster Recovery | Business Continuity

Don’t leave your most valuable assets – your corporate data and systems – without a plan to recover from in the event of an outage or disaster.

We’ll map out BC (Business Continuity) plan to be taken to continue your business operations

And a DR (Disaster Recovery) plan to document step-by-step needed to be made to safeguard data when an incident such as drive failure, natural disaster or user error has taken place

Count on Poinvitity Managed DR and BC for:

  • Keeping your business and employees going even when disaster strikes.
  • Storing backups of your data to ensure your company’s future.
  • Reducing the cost of downtime and data loss.

Pointivity creates cost-effective and adaptable DR solutions for you without the overhead cost associated with traditional DR. We customize the configuration for your specific requirements to meet your needs by:

  • Understanding your company’s business and IT environment: what systems does your business need to function?
  • Performing risk assessment: where are the weaknesses in your protocols and processes?
  • Evaluate IT resource requirements: who and what resources are needed for the business to resume operations?
  • Testing and maintenance: let’s put the plan into action.

The Cost of Downtime

See how Pointivity helped economic research and consulting firm Laffer Associates reduce data risk and downtime with a simple and secure Microsoft-based solution.

null

Loss of Revenue

It may be impossible to predict future revenue. So, obtain revenue figures from the previous year, and divide that by the number of business hours in the year. Yes, revenue will vary month to month, but this gives you at least a rough estimate.
null

Loss of Productivity

This is a cost that some organizations may choose to exclude, since labor costs are sunk costs. However, consider the effect of a backlog (e.g. overtime costs) and delays in meeting deadlines. Make a rough estimate based on employee salaries: determine the average salary (total salary for all staff divided by the number of staff), and from there, determine hourly wages.
null

Increased Operating Costs

Isolate this to known additional costs resulting from a disruption. For example, is there an extra cost to working out of alternative locations, including additional travel costs? Does the interruption itself increase operating costs (e.g. if using timesheets for hourly/contract employees and that information is lost or unavailable, do you assume a full work week)?
null

Financial Penalties

If there are known financial penalties (e.g. due to failure to meet SLAs or other contractual obligations), include those values in your cost estimates.
null

Impact on Goodwill

This is an area where even a rough dollar estimate may not be possible. If so, use a high-low scale.

Building DR with Azure

Be prepared with a business continuity plan that includes disaster recovery for all your major IT systems — without the expense of secondary infrastructure through Microsoft Azure.

  • Achieve low recovery point objective (RPO) and recovery time objective (RTO) targets for every major system in your organization, simply and cost-effectively.
  • Eliminate the hassle and cost of secondary datacenters and tap into a cloud-based data recovery solution.
  • Achieve your goals for continuity and compliance and help secure your data with industry-leading protection offered by encryption features.
  • Utilize automated recovery plans to get your apps and datacenter back up in a matter of hours instead of weeks or months.
  • Test your business continuity plans, or run dev-test copies of production workloads in Azure whenever you need to, without impacting users.
  • Test new versions of applications with copies of live data, and then seamlessly put the new version into production in your datacenter.

How to Determine Recovery Objectives

null

Record Applications and Dependencies

Utilize your asset management records and document the applications and systems that IT is responsible for managing and recovering during a disaster.
null

Define Impact Scoring Scale

Ensure an objective analysis of application criticality by establishing a business impact scale that applies to all applications.
null

Estimate Impact of Downtime

Leverage the scoring criteria from the previous step and establish an estimated impact of downtime for each application.
null

Identify Desired RTO and RPO

Define what the RTOs/RPOs should be based on the impact of a business interruption and the tolerance for downtime and data loss.
null

Determine Current RTO/RPO

Conduct tabletop planning and create a flowchart of your current capabilities. Compare your current state to the desired state from the previous step.

Need to Chat?

Click or call to talk to one of our experts.