Questions For The Cloud Provider In Cases Of Disaster Recovery

Disaster Recovery as a Service (draas) is a growing sport. How is the initial phase? Many organizations still do not know exactly what to look for when seeking a provider model. Analyst of disaster recovery (DR) research institute Gartner’s John Morency list a series of tips for customers looking for the right questions to address the future draas provider. Here are some of them.

What to look for in a Cloud Service Provider? Understand the position of the provider in the market, its portfolio of services and financial stability.

Service-Level Agreement (SLA) is customized or generic? Size of the installed base. Number of recoveries made.

How long is the business and the number of offices (local and international), names of the five largest customers, the length of relationship with each and contact information to serve as reference. Key Personnel associated directed to your account and contacts. Experiment with customers of companies in the same line of business. SLAs To observe the performance of the virtual machines that run in the cloud to ensure that they meet the needs of the organization.

Geographical location of centers, provider support to ensure that they can meet requests for service delivery. Statement processes in cases of disaster and incident management process of screening. recovery time for 0-2 hours: communication, airlines, financial services 2-8 hours: defense, insurance, biotechnology, health, manufacturing, utilities 8-24 hours: consumer goods, distribution, retail, government, company that does not operate with airlift More than 24 hours: construction, distribution, food / beverage, media in data center provider’s Statement on Standards for Attestation Engagements (SSAE) 16, Service Organization Control (SOC), formal certifications 1, 2 and 3. Or certification Statements on Auditing Standards (SAS) 70 Type II.

The SSAE 70 replaces the SAS. Data Center must meet the requirements of the Uptime. Guaranteed uptime of 99.995%. Number of clients per virtual machine. Personnel available. Tests allowed to users. Prices Detailed review of the pricing structure. Value draas by layer. Maintenance fees. Additional equipment costs. Exchange support. Cost per day with consulting services, training, including travel costs. Cups with software licenses. Any other fees or charges that the customer will have to pay.