Posts Tagged ‘resilient computing’

Are More Applications Mission-Critical Than Your Realize?

Some applications are obviously mission-critical—the website of an e-tailer or the ATM machine at a bank.  However, the criticality of some application can go unrecognized unless you do a systematic qualify of each application.

To qualify applications, check these metrics for each:

  • Recovery point objective – how much data loss is tolerable?  All of today’s data entries?  The entire database, because restoring the database is easy?
  • Recovery time objective – how long can the business go without access to the application before customer service, sales, accounting, etc., suffer?  How much data can be rebuilt and verified inside that time window—a few day’s worth, a few hour’s worth?
  • Recovery resources – what space, equipment and staffing are needed to replicate the data?  Would those resources be available if other mission-critical systems were down, too?  If not, how much

Once each application is evaluated, determine whether all the mission-critical applications can be recovered simultaneously, as would be needed with a data center incident caused by a flood, hurricane or tornado.  If the recovery requirements exceed current equipment, network and staff resources, consideration of a cloud-based recovery solution is in order.

Cloud-based recovery solutions offer access to low-cost or pay-as-you-use recovery infrastructure.  They can be provisioned on demand in the wake of failure events, with sufficient security and guaranteed performance.

Could unrecognized mission-critical application be lurking in your data center?

Visit our Cloud Solutions Center for videos, white papers and case studies about SunGard’s Enterprise Cloud Services.

Recovery In the Cloud, Part 2 – What CIOs Should Ask

Recovery In the Cloud, Part 2 – What CIOs Should Ask

Ram Shanmugan, our  Senior Director of Product Management for Recovery Services, offered the important points below in an interview recently with Smart Business Philly.  –Carl M.

Evaluating cloud providers is time-consuming and can be a nerve-racing task.  You don’t do it often enough to become expert at it and sometimes its hard to separate reality from hype.  Here are a few questions that go to the crux of most CIO concerns.

  1. Does the  provider offer meaningful service level guarantees for recovery of mission-critical applications?  Can it reliably recover mission-critical applications in the wake of failure?
  2. Does it support heterogeneous computing platforms (e.g., Windows, Linux) and hybrid architectures that meet the recovery needs of the entire IT portfolio?
  3. Does the staff have hands-on disaster recovery experience?  Has it recovered from a disaster?  Does it understand the entire disaster recovery lifecycle?  Can it provide audit-ready test reports?
  4. Does it provide options for high availability, as well as less crucial applications in a heterogeneous environment?  More specifically, can this partner support a broad portfolio of Recovery Point Objectives (i.e., for each application, the amount of downtime and data loss your business can sustain after a disaster) and Recovery Time Objectives (i.e., the recovery timelines and priorities your business requires for mission-critical applications and processes).
  5. What is the range of options supported for moving data to the cloud?  Does it use monitoring and automation tools to ensure rapid and effective response to failures?
  6. Can the cloud partner handle your current and future needs?  Can it expand and contract on demand, handle sudden growth or support large amounts of application data?
  7. Can clients pay as they go?
  8. Does the provider offer multiple levels of security and service options?  If some data is too sensitive for the cloud, will the provider use a private cloud for that data but use a shared cloud for everything else?

One size does not fit all, so cloud partners should offer a range of private, hybrid and physical environments to make sure your data is secure and can be recovered after a disasters.

What combination of shared, hybrid and private cloud makes the best economic sense for your company?

Visit our Cloud Solutions Center for videos, white papers and case studies about SunGard’s Enterprise Cloud Services.

Recovery in the Cloud – Part I, CEO Decision Drivers

Ram Shanmugan, our  Senior Director of Product Management for Recovery Services, was recently interviewed by Smart Business Philly magazine.  Below are some of the important points he discussed.  We’ll have more next week.  – Carl M.

“Weathering a storm” is more than just an off-hand comment these day. The U.S. experienced eight disasters costing over $1B in the first 6-months of 2011.  Few areas of the U.S were shared the business complications caused by tornado, blizzard, wildfires and floods.

Planning for erratic weather can be tricky.  Of course, you want secure data, redundant infrastructure and business continuity processes, but balancing those needs against the needs for revenue-generating IT projects is difficult.

Fortunately, “recovery in the  cloud” offers a cost-effective, reliable option.  It lets you formulate the right availability service for your applications, from mission-critical to important but infrequently used applications.

Four elements drive the decision to move to a cloud-based recovery service:

  1. Cost savings.  The ability to fulfill recovery needs and lower costs is the most significant driver,
  2. RPO/RTO.  The Recovery point objectives (how long you can tolerate an application being down) and the recovery time objectives (how long it takes to recover the application) determine the level of resources your need to avoid serious impact to your business.
  3. Reliability. The true value of a recovery environment comes during a time of disaster, and managed cloud-based solutions offer higher reliability in recovery of mission-critical applications than do in-house solutions.
  4. Skilled Resources.  In-house recovery solutions require an investment in specialized skills to support the recovery infrastructure.  Cloud-based recovery eliminates that need.

Can your IT department recover from an outage without incurring emergency resources and costs?

Visit our Cloud Solutions Center for videos, white papers and case studies about SunGard’s Enterprise Cloud Services.

The Cloud and the Availability Continuum – PART 2

Like dedicated hosting, cloud computing has to address availability.  Continued cloud outages, and the corresponding publicity, remind us of the importance of resiliency and availability.  One of the major benefits of cloud computing is scalability and efficiency of multi-tenant infrastructure.  However, even cloud infrastructures have to run in a physical data center somewhere, bringing us back to the critical nature of infrastructure availability.

Fortunately, the same availability you are accustomed to as part of a dedicated environment can be found in cloud computing.  Availability can be viewed in a continuum that ranges from high availability to failover and recovery, with many nuances in-between.  This continuum of  availability enables clouds to fulfill enterprise application and business needs at many different price points.

Platform Resiliency for Continuous Uptime

The first area to address availability is the resiliency of the platform itself.  Businesses requiring enterprise-class infrastructure need to look under the hood to determine how the infrastructure is architected and how resiliency is addressed.  A highly resilient environment should automatically
detect and address the failure of a system component—whether it is a server, network, a full blade or the VM —to quickly shift to a redundant component in order to keep the application running in the current site.

Failover

Failover is the capability to switch to a redundant or standby computer server, system, or network upon the failure or interruption of the primary environment.  Cloud computing has allowed failover practices to become less reliant on physical hardware and therefore more
available and less costly.  Service providers vary in the type of fail-over they provide as well as the time to respond, depending on the customers’ RPO and RTO needs.

A failover, or warm failover can be used for applications that require slightly less than real-time (e.g. hours VS. seconds).  In warm failover, a second site stands ready to be activated and made current as quickly as required.  Depending on the need, the time to failover depends on the Customer’s recovery time objective.  Sometimes the options can include the secondary site begin brought on line using a previous copy of the primary site.  Usually the copy is from the previous day, but it can be older depending on the business need.

High Availability for Mission-critical Apps

High availability addresses mission-critical production systems that require immediate, continuous, 24/7 access to data.  More technically, it means data must be duplicated at another location, usually in a different geographic area.   Essentially you are renting resources at one location and identical resources at another location, so costs are higher.

The communication method used between the systems also affects availability and costs.  Synchronous near real-time communication  pdates data from the primary system immediately  to the secondary system.  The secondary system mirrors the first and is ready to go into operation if the first system fails for any reason.

Asynchronous communications is where data waits in queue until the second system is free to accept it, so by its nature is less real-time.  Again, the business need determines which communications method is better.
Recovery for Availability

Recovery represents the other end of the availability continuum.  Cloud computing is changing the disaster recovery landscape.  The scalability and
flexibility of cloud computing platforms enable higher application availability.  Recovery can be used as a back-up to a production system already in the cloud or as a recovery solution to  another data center.  Further, the back-up can be on-line, ready to operate at the cloud site (like a warm failover) or off-line at a cloud site, as done in traditional recovery scenarios, since the cloud is a cost-effective recovery site for legacy systems.

As is obvious, different applications require different levels of availability, and applications should not be shoehorned into a “one size fits all” cloud
environment.  The best cloud providers will work closely with you to understand the business requirements of your business  applications  and devise the appropriate level of availability for each application you want to move to the cloud, along with any need for cloud resources to facilitate recovery of applications you do not move to the cloud.

Click here to view the SunGard Recover2Cloud Overview

The Cloud and its Continuum of Availability -PART 1

One of the major benefits of  cloud computing is availability and that availability comes in a continuum that ranges from high availability to high resilient, warm failover, failover and recoverable, with many nuances in-between.   This continuum of availability enables clouds to fulfill  application and business needs at many different price points.

High Availability for Mission-critical Apps

High availability is used for mission-critical production systems that require immediate, continuous, 24/7 access to data.  More technically, it means data must be duplicated at another location, usually in a different geographic area.   Essentially you are renting resources at one location and identical resources at another location, so costs are higher.

The communication method used between the systems also affects availability and costs.  Synchronous communication replicates the data in near real-time.  That is, data from the first system immediately updates the second system.  The second system mirrors the first and is ready to go into operation if the first system fails for any reason.

Asynchronous communications sends data from the first system to the second, where it waits in queue until the second system is free to accept it.  Again, the business need determines which communications method is better.

High Resiliency for Continuous Uptime

High resiliency is used for applications that do not require high availability.  In a highly resilient environment, automatic systems detect the failure of a system component—whether it is a server, a full blade or the VM software—to quickly shift to an alternate component to keep the application running in the current site.

Warm failover and failover are used for less critical applications.  In warm failover, a second site stands ready to be activated and made current as quickly as possible.  In failover, a second site is brought up using a previous copy of the primary site.  Usually the copy is from the previous day, but it can be old depending on the business need.

Recovery for Back-up.

Recovery represents the other end of the continuum.  Recovery is used as a back-up to a production system already in the cloud or as a back-up to another data center.  Further, the back-up can be on-line, ready to operate at the cloud site (like a warm failover) or off-line at a cloud site, as done in traditional recovery scenarios, since the cloud is a cost-effective recovery site for legacy systems.

As is obvious, different applications require different levels of available, and applications should not be shoehorned into a “one size fits all” cloud environment.  The best cloud providers will work closely with you to  understand the importance of your applications to your business and devise the appropriate level of availability for each application you move to the cloud, along with any need for cloud resources to facilitate recovery of applications you do not move to the cloud.

How does the continuum of availability fit with your move to the cloud?

Visit our Cloud Solutions Center for videos, white papers and case studies about SunGard’s Enterprise Cloud Services.