By Richard Seroter, Senior Product Manager. Find Richard on Twitter
Are you an MSP, VAR, or systems integrator? Do you want to start offering cloud services to upsell existing customers, while attracting new ones? Tier 3 is here to help. Last week, we announced a Reseller Edition of our cloud and we offer unique expertise in partnering with companies that want to quickly add cloud services to their product portfolio. In this blog post, we’ll walk through 8 quick steps to follow in order to get up and running as a cloud reseller.
1. Investigate the market and select a reseller.
We recently did a reseller-focused webcast with the folks at Talkin’ Cloud and a spot survey showed that over 75% of attendees were actively looking for a cloud partner. Clearly, a large number of telcos, SIs, and regional service providers are scouring the market and aggressively assessing whom to partner with.
If you are looking for a partner, what should you be asking each vendor? How can you ensure you are partnering with an innovative, differentiated provider that can bring you new revenue over the long-haul? Here’s a great starting point:
Does the provider have a global set of data centers?
WHY THIS IS IMPORTANT: Your customers are more global than ever, and physical locations close to users and customers matter. Also, data sovereignty regulations impact where the physical “host” servers need to be.
Can the provider support the complex infrastructure and networking needs of your managed customers?
WHY THIS IS IMPORTANT: If not, there’s a good chance your customers won’t find your new cloud services attractive for their enterprise workloads.
How often to legacy systems need to be re-architected to fit the provider’s cloud?
WHY THIS IS IMPORTANT: Agility and immediate access to resources are key drivers to move to the cloud in the first place. But this doesn’t need to be at odds with legacy applications - even complex environments can be migrated cleanly to the cloud if you choose the right provider.
What controls do you have in place to protect data sovereignty?
WHY THIS IS IMPORTANT: Larger businesses need peace of mind to know their data is securely stored in isolation, in a physical location they can specify.
Which 3rd party products are commonly added by the provider’s customers, if any?
WHY THIS IS IMPORTANT: Add-on services can be helpful for specific scenarios, but when it comes to the core scenarios of cloud management and automation, you should look for a provider that has significant capabilities built-in. Bringing in extra modules just adds cost and complexity for you and your customers.
How does the partner manage customer accounts and billing processes?
WHY THIS IS IMPORTANT: These back-office functions are vital when it comes to quickly monetizing the service. Sure, it’s not a sexy set of features, but it will make invoicing a breeze.
Can I rebrand the provider’s offering and make it look and feel like something from us? Does this feature cost extra?
WHY THIS IS IMPORTANT: This is key to customer loyalty and building brand equity.
How do I make money with your cloud?
WHY THIS IS IMPORTANT: Powerful features and a highly capable global cloud platform don’t mean anything without a competitive partner program, and a spirit of partnership with your selected vendor.
How can I extend my business model of value-added services to the provider’s cloud?
WHY THIS IS IMPORTANT: This last question is key. How can you make sure that customers don’t just use a commodity cloud offering, eliminating your unique expertise? Among other things, Tier 3 encourages customers to differentiate on price and by offering exclusive intellectual property through Blueprints that encapsulate best practices on building highly-available, tuned application environments.
2. Evaluate Tier 3 - sign up for an account.
This one’s easy! Just visit the self-service sign up page and register for a new Tier 3 account. Within moments, you will receive an email with temporary credentials and a link to the easy-to-use Tier 3 Control Portal.
3. Change the site aesthetics to fit your brand.
Once you’ve logged in, the first thing to do is customize the Control Portal UI to match your brand. Tier 3 offers a variety of settings that allow you to rename the interface, modify logos and shortcut icons, and alter the color scheme of the site. These superficial – but important – changes go a long way to maintaining a brand identity with your customers.
4. Update the support-related hyperlinks.
Your will likely want your customers to take advantage of the support experience that you currently offer. Fortunately, you can easily override existing support links and point to your own online assets. For instance, you can change the default support email address, phone number, knowledge base URL, chat service URL, and much more.
5. Update outbound email templates.
Each email that comes from the cloud platform should reflect your brand and message. To achieve this, Tier 3 added configurable settings that let you change the email addresses, signature, subject lines, and message body of the most common system alerts.
6. Integrate with your existing billing, configuration management, and identity systems.
Unless you want to build a silo cloud service that doesn’t integrate with the rest of your back office systems, you’ll want to pay careful attention to this step! To integrate your billing systems with Tier 3, consider using our helpful Billing API that gives you access to usage estimates and monthly invoices. While you can easily access and download invoices from the Tier 3 Control Portal, the Billing API gives you a way to directly integrate our cloud with your financial systems.
Many organizations have investments in change management or support systems that track assets throughout their lifecycle. How can you ensure that servers in the Tier 3 cloud are properly “tagged” and linked to a configuration management database? One useful option is to add account-level “custom fields” that are populated whenever servers are added to the Tier 3 cloud.
You can access these custom field values through the Tier 3 API as well. If you chose to provision servers from within your own custom portal, you could call the Create Server API and tag the server with an identifier from your own system. This makes it simple to reconcile changes to servers in the Tier 3 cloud with the entries in your local systems.
Finally, if you offer a centralized identity directory to authenticate users of your existing platform, you may want to reuse that with the Tier 3 cloud. Tier 3 supports the SAML identity protocol for single sign-on between external identity directories and the Tier 3 Control Portal. Consider SAML and SSO if you want to make it simple for customers to reuse their existing credentials to log into the Tier 3 Control Portal.
7. Choose your preferred data centers.
You’re nearly ready to open the doors of your new cloud offering! In this step, assess which data centers you want customers to deploy servers into. The “Preferred Data Centers” settings let you choose which data centers show up for users who provision and manage servers.
8. Establish cloud costs and promotions.
While you likely established contractual settings early on, this final step involves configuring pricing details in the platform. We offer a very competitive pricing plan that ensures that you can generate a strong recurring revenue stream while giving customers a cost-effective cloud solution. Contract terms and promotion codes are managed by Tier 3 but we work closely with you to rapidly apply pricing parameters to your account.
Summary
The cloud offers a compelling and lucrative opportunity for existing managed service providers and systems integrators. Instead of building and maintaining your own cloud, consider partnering with Tier 3 and bringing cloud services online in a matter of days or weeks!
By Richard Seroter, Senior Product Manager. Find Richard on Twitter
Just a couple weeks ago, we looked at how Platform-as-a-Service (PaaS) helps developers rapidly build and deploy applications to the cloud. We also covered a new breed of cloud-based development environments (IDE) that developers can use to create and publish their web applications. Since then, the cloud-based IDE we featured – called Codenvy – has updated their product to support the Tier 3 Web Fabric. In this post, we’ll walk through how to quickly and easily deploy and manage Web Fabric applications from your web browser.
To start with, when users of Codenvy start a new web application project, they are asked which technology they want to use, and then which PaaS to deploy to. At this moment, the Tier 3 Web Fabric is available for Java Web Application (WAR), Java Spring, and Ruby on Rails projects. Note that Web Fabric works with more environments than these three, but these are the technologies supported via Codenvy.
Once the user chooses the technology and corresponding PaaS, they choose a simple project template (if one exists for that technology), and are then asked for the management API endpoint of the Web Fabric environment.
The project framework is then created, and the user is prompted for their Web Fabric credentials. After providing a valid username and password, the application is deployed and Internet-accessible. All of this in matter of seconds! To update the application, developers visit the PaaS menu option and choose Tier 3 Web Fabric.
From the subsequent window, developers can modify the name, URL, and memory allocation of the application. Additionally, the application can be started, stopped, deleted, and updated. It’s also possible to add Web Fabric application services – such as RabbitMQ for messaging or Microsoft SQL Server for relational database storage – to a project.
Codenvy can also be used as a simple management interface for any applications running in Web Fabric. This can come in handy if you’re on a shared machine without the typical Cloud Foundry management tools available!
This interface shows you each application running in your Web Fabric environment, and lets you start, stop, restart, or delete it.
Summary
We’re excited to be a supported part of the innovative Codenvy platform and think that this lowers the barrier to entry for our customers while making it simpler for developers to build amazing applications in any language of their choice. Want to try it out? Sign up for a free Codenvy account and then take Web Fabric for a spin!
By Richard Seroter, Senior Product Manager. Find Richard on Twitter
Web applications are a dominant part of most enterprise IT portfolios and Platform-as-a-Service (PaaS) products offer a compelling way to easily deploy and manage these applications. However, PaaS have proven tricky for vendors to explain, and therefore difficult for customers to understand. In this post, we’ll discuss the reason you should consider using PaaS products, what Tier 3 has to offer, and how you can deploy a web application to a PaaS in a matter of minutes.
Benefits of PaaS
What exactly is PaaS? Basically, it’s a way of delivering an application platform as a service. Developers don’t interface directly with infrastructure (e.g. servers, networks, load balancers) but rather, focus on building and deployment applications through a set of exposed services in a managed fabric. PaaS simplifies the deployment and management of modern web applications while making those applications more resilient and functional. How can PaaS add value to your organization? Let’s drill into some specifics:
- Reduce server sprawl with a centralized host for web applications. How many web servers are sitting relatively idle in your data center because they are only running a handful of applications? Server sprawl can be a major issue as each IT project requisitions its own hardware for application development/staging/QA/production. What about all your websites for customers and marketing campaigns? It’s possible that you’re using many different servers (and even providers!) to host all of those individual websites. PaaS can offer a centralized fabric that can be sized and optimized for hundreds of internal or external web applications.
- Save money by adding resources only when you need them. Many PaaS products have a concept of automatic scale or user-driven resizing to account for spikes or dips in utilization. Before cloud computing, organizations typically sized their infrastructure for peaks and accepted that their environment would be underutilized the majority of the time. Now, it’s possible to deploy a web application with a 128MB memory allocation, and instantly double it when needed. Need to spread the workload across multiple machines? Simply issue a command to add the application to another node in the PaaS fabric. No calls to the operations team, no formal “deployment” exercises. PaaS makes it possible to size and scale applications on demand, which makes it easier for you to manage the overall environment.
- Focus on your application, and don’t sweat the infrastructure. One of the most important benefits of PaaS is that it abstracts the infrastructure away from the application, and the developer. Developers deploy to a fabric, not a server. There’s no need for the IT project team to provision web or database servers. Simply push applications to the existing PaaS environment. The infrastructure itself is managed closely by an operations team and automation is included at all levels to deliver automatic patching, scaling, monitoring and more.
- Multi-tenancy and high-availability baked in. PaaS products are designed to deliver high-availability to multiple applications (or “tenants”) and are therefore scaled out to provide significant compute capacity. As such, you’ll find many PaaS products with built-in load balancing services, failover when servers fail, concurrency management, and more. All of these features boost reliability and performance for each application hosted in the PaaS. Even applications not specifically designed for PaaS can conceivably be deployed to a PaaS with little to no code refactoring.
- Avoid unnecessary duplication by using consolidated application services. When most people think of PaaS they think of hosting web applications, but some of the best capabilities are those offered by complimentary services. Most PaaS products offer add-on services like databases, storage, identity management, messaging, caching and more. You’ll also find some PaaS products that offer business services such as service catalogs, and API management and monitoring. Developers can use these services when building their web applications and not have to provision or locate hardware to host those services at runtime. These services simply exist inside the PaaS and are available to all applications deployed there.
- Deliver “IT as a Service” through measured usage for easy chargebacks. A core tenet of cloud computing is “pay as you go” and measured usage. A true PaaS is built upon a “cloudy” foundation that tracks utilization and delivers an all-up cost to the user at the end of the month (or whenever the user checks their charges). Because of this cost transparency, it’s easy for organizations to deliver “IT as a service” by offering a PaaS for internal/external websites and passing along the usage-based invoices to each department.
All of this helps developers produce faster deployments while giving system administrators a more streamlined operations responsibility.
Why Tier 3 Web Fabric?
Tier 3 has its own PaaS product – called Web Fabric – that is based on Pivotal’s Cloud Foundry project. We’ve added the open-source Iron Foundry extensions so that we can offer some of the best language and framework support in the industry. Unlike the shared PaaS services offered by others, Web Fabric is provisioned uniquely for each customer. This gives you the isolation you need, while still offering a robust platform for all the custom applications used by your organization. The default Web Fabric environment consists of five total servers and can support dozens of web applications.
Why might you choose to use the Tier 3 Web Fabric to host your modern web applications? We like to point out at least five reasons:
- Support for the programming languages you already use. Most IT shops are heterogeneous and use technologies from multiple vendors. You may have written a number of enterprise-class web applications in .NET or Java, but also have departments that make use of Ruby or PHP. If you’re doing more mobile development, you might have started looking at Node.js for high performing web applications. Tier 3’s Web Fabric supports all those programming languages and more. Instead of using multiple PaaS products or infrastructure clouds to host your diverse application portfolio, use a single fabric for all of them!
- Application services to cover your scenarios. Need a relational database? We offer MySQL, PostgreSQL, and Microsoft SQL Server. Looking for a NoSQL repository? Web Fabric has Redis and MongoDB. RabbitMQ is also available when you want to add a durable message queue to your solution. In addition, each Web Fabric comes with New Relic monitoring for web applications. This excellent application performance management tool gives you deep insight that helps identify bottlenecks and monitor application health.
- Cloud Foundry ecosystem. There’s no doubting the impact of Cloud Foundry on the PaaS industry. This open source project was launched in 2010 and has been adopted by multiple PaaS vendors. Not only does this make it straightforward to move applications between Cloud Foundry-compliant clouds, but also means that there are multiple parties creating tools that work for any Cloud Foundry environment. From the Windows-based Cloud Foundry Explorer, to the OSX-friendly Project Thor, to web-based development environments, there’s a growing ecosystem of vendors and tools to help you be successful with Cloud Foundry.
- Enterprise-class infrastructure. Tier 3’s network of highly resilient, globally distributed infrastructure is optimized for performance throughout the stack. And since Web Fabric runs on the Tier 3 enterprise cloud, your applications will be powered by high performing storage, multiple VPN options, security services, and much more.
- IaaS and PaaS, better together. Not all workloads fit into a PaaS platform, and not all applications require dedicated infrastructure. By offering our customers enterprise-class infrastructure in addition to Web Fabric, we’ve provided two useful hosting mechanisms in the same cloud. Keep your PaaS applications geographically close to your IaaS applications and data, and share the same management tools, security profile, and networking configuration.
Deploying to Web Fabric from a Cloud-based Development Environment
Developers can push their application to Web Fabric in a number of ways. While most developers are familiar with command line interfaces and GUI tools that run on their desktop, a new crop of cloud-based integrated development environments (IDEs) can make PaaS deployments even simpler. Cloud IDEs offer excellent collaboration capabilities, easy accessibility, and “no-touch” setup.
One such cloud IDE is Codenvy. This tool works natively with Cloud Foundry, making it easy to build Java/Ruby/Python/PHP applications and then push them to Web Fabric. After signing up for a free account, the developer is presented with the option to link to GitHub or any Git repository.
Codenvy uses a handy “new project” wizard experience to help the developer choose which programming language to use, and then which (supported) PaaS to push to. In the short animation below, observe how I created a new Java Spring project, chose Cloud Foundry (Web Fabric) as a destination, finish the wizard and publish the application to Web Fabric.
The Codenvy IDE includes many developer productivity features including type-ahead coding (i.e. “intellisense”), code generation, formatting tools, and much more. Changing the application code and re-publishing the application to Web Fabric is simple. Notice how easy it is to resize my application (e.g. memory, instance count) at any time!
Besides simply deploying applications, Codenvy supports simple management of existing applications. From the PaaS –> Cloud Foundry –> Applications menu, I can see all the applications that I’ve deployed to Web Fabric and stop/start/restart/delete any of them.
Developers using cloud-based IDEs don’t get all the features of desktop IDEs (like access to local resources, plug-ins), but they are an increasingly viable choice for developers who are trying new technologies or need access to their IDE from any computer.
Summary
With our enterprise-class infrastructure and platform cloud, Tier 3 is uniquely positioned to address your cloud needs. Web Fabric is an ideal host for your modern web applications and its Cloud Foundry heritage makes it compatible with a wide array of tools including cloud-based IDEs like Codenvy.
Interested in taking a look at Web Fabric? Contact us for a demonstration and free trial!
Jared Ruckle
Cloud Connect, last week in Santa Clara, offered an insightful look on the state of the industry, with perspectives from analysts, big name vendors, and startups. Here are a few things that caught our eye in the week that was.
The Enterprise Cloud Adoption Survey Summary from Everest Group. Done in conjunction with the organizers of Cloud Connect, the survey of 3 segments (cloud buyers, cloud service providers, and cloud advisors) offers a reality check on where the market is today, compared to the future-looking perspectives that are common in emerging spaces like this one. One of the more interesting highlights that mirrors our experience:
Public cloud providers may need to modify their communication on the cost benefits of adoption from a pure cost/unit conversation to one that is more focused around lower TCO and ROI
The findings also paint a positive picture for platform-as-a-service (PaaS), indicating that a strong majority of survey respondents are already using PaaS, or plan to in the near future. Check out the whole survey here.
Q&A with Joe Weinman of Telx. Against conventional wisdom, Joe has long predicted that hybrid clouds will be the eventual end state of cloud computing. Our own Richard Seroter catches up with Joe, and discusses the finer points of hybrid cloud and something called the Backseat Airline Magazine Bias.
PEER 1 Launches the Mission Critical Cloud, powered by Tier 3. I didn’t see too many product launches at Cloud Connect, so this one (albeit self-servingly) makes the list. There are many white-label products of this sort in the market today, but very few that are targeted upstream at businesses with more complex requirements. This partnership helps Tier 3 scale, while complementing PEER 1’s product portfolio. The product announcement is here.
6fusion, utility-metering of cloud services for the enterprise. ROI and TCO calculations for enterprises considering the public cloud can be complicated, even for small workloads. This complexity grows as hybrid cloud and additional vendors are thrown into the mix. Solving this problem of cost transparency, and ultimately delivering “apples to apples” comparisons across multiple cloud, based on historical and real-time data, is the aim of 6fusion.
I saw a demo of their app, and it is very cool. There are commodities trading overtones to their approach and the UI. In fact, CEO John Cowan wrote a few weeks back:
“When the modern enterprise or resource supplier can apply the principles of financial trading to the IT industry we are going to see a force capable of completely redefining everything we currently think we know about the business of technology delivery.”
There will be a range of cloud services: vanilla commodity services for low-end deployments, other more differentiated offerings for mission-critical scenarios, and other tiers in between. 6fusion aims to help IT quantify the value difference between the inevitable layers of cloud services. It will be interesting to watch their progress, and see how the industry in general grapples with delivering better cost transparency as complexity of cloud deployments grows.
Cloudmunch. This startup launched its DevOps platform, a “first-of-its-kind full-stack continuous delivery platform”, at DeployCon. With this service, developers can leverage full-stack continuous delivery for applications and infrastructure, with integrations to GitHub and support for Chef. It is a little surprising that this hasn’t been thought of before—there is a lot of flexibility and efficiency for all the devs out there. Read the news of their launch here.
Flexiant receives funding for cloud orchestration. This wasn’t anything specific to Cloud Connect, but the timing was apt. Cloud orchestration remains a little mysterious to most enterprises (as well as the reseller channel), so traction in the category is encouraging (Tier 3 for our part, has built Blueprints). Flexiant seems keen to use orchestration on a larger scale, actually helping with greenfield reseller cloud build outs, instead of targeted templates to assist end-user IT pros. Sounds like a US expansion is in the works. They will be one to watch in the States.
By Richard Seroter, Senior Product Manager. Find Richard on Twitter
It’s easy for cloud customers to get confused about the roles and responsibilities of their internal team and their cloud vendor. That confusion is especially evident when it comes to application availability and business continuity planning. How does disaster recovery differ from high availability? Does my cloud provider automatically load balance my application servers? The answers to these questions are critical, but sometimes overlooked until a crisis occurs. In this post, we’ll talk about load balancing, high availability, and disaster recovery in the cloud, and what the Tier 3’s cloud infrastructure has to offer.
Load Balancing
What is it?
Wikipedia describes load balancing as:
Load balancing is a computer networking method to distribute workload across multiple computers or a computer cluster, network links, central processing units, disk drives, or other resources, to achieve optimal resource utilization, maximize throughput, minimize response time, and avoid overload. Using multiple components with load balancing, instead of a single component, may increase reliability through redundancy.
You commonly see this technique employed in web applications where multiple web servers work together to handle inbound traffic. 
There are at least two reasons why load balancing is employed:
- The required capacity is too large for a single machine. When running processes that consume a large amount of system resources (e.g. CPU and memory), it often makes sense to employ multiple servers to distribute the work instead of constantly adding capacity to a single server. In plenty of cases, it’s not even possible to allocate enough memory or CPU to a single machine to handle all of the work! Load balancing across multiple servers makes it possible to host high traffic websites or run complex data processing jobs that demand more resources than a single server can deliver.
- Looking for more reliability and flexibility in a solution deployment. Even if you *could* run an entire server application on a single server, it may not be a good idea. Load balancing can increase reliability by providing many servers able to do the same job. If one server becomes unavailable, the others can simply pick up the additional work until a new server comes online. Software updates become easier since a server can simply be taken out of the load balancing pool when a patch or reboot is necessary. Load balancing gives system administrators more flexibility in maintaining servers without negatively impacting the application as a whole.
Load balancing can be accomplished using either a “push” or a “pull” model. For web applications or database clusters that sit behind a load balancer, inbound requests are pushed to the pool of servers based on an algorithm such as round-robin. In this scenario, servers await traffic sent to them by the load balancer. It’s also possible to use a “pull” model where work requests are added to a centralized “queue” and a collection of servers retrieve those requests from that queue when they are available. For instance, consider big data processing scenarios where many servers work to analyze data and return results. Each server takes a chunk of work and the overall processing load is distributed across many machines.
How can Tier 3 help?
Tier 3 offers multiple load balancing options to our customers. All customers have access to a free, shared load balancer. This load balancer service – based on the powerful Citrix Netscaler product – provides a range of capabilities including SSL offloading for higher performance, session persistence (known as “sticky sessions”), and routing of TCP, HTTP and HTTPS traffic for up to three servers. To use this service today, send a request to noc@tier3.com. We plan to launch a self-service version of this capability in the very near future.
If you’re looking for more control over the load balancing configuration or have higher bandwidth needs, you can deploy a dedicated load balancer (virtual appliance) into the Tier 3 cloud. This “bring your own load balancer” option leverage internal expertise you may have with a particular vendor. It also gives you complete control over the load balancer setup so that you can modify the routing algorithm or enable/disable features that matter to your business.
High Availability
What is it?
Returning to Wikipedia, high availability is defined as:
High availability is a system design approach and associated service implementation that ensures a prearranged level of operational performance will be met during a contractual measurement period.
High availability is described through service level agreements and achieved through an architecture that focuses on constant availability even in the face of failures at any level of the system. While load balancing introduces redundancy, it’s not a strategy that alone can provide high availability. Servers sitting behind a load balancer may be running, but that doesn’t mean that they are available!
Availability addresses the ability to withstand failure from all angles including the network, storage, and even the data center itself. Enterprise cloud services like those from Tier 3 are built on a highly available architecture that uses redundancy at all levels to ensure that no single component failure in a data center impacts overall system availability. This includes “passive” redundancy built into data centers to overcome power or internet provider failures, as well as “active” redundancy that leverages sophisticated monitoring to detect issues and initiate failover procedures.
All of our customers get platform-level high availability when they use the Tier 3 cloud “out of the box.”
That means that you can rely on us for your workloads knowing that our architecture is well-designed and highly redundant. However – back to the introductory paragraph – it’s the customer’s responsibility to design a highly-available application architecture. Simply deploying an application to our cloud doesn’t make it highly available. For example, if you deploy a single Microsoft SQL Server instance in the Tier 3 cloud, you do not have a highly available database. If that database server goes offline or network access is interrupted, your application’s availability will be impacted. To design a highly available Microsoft SQL Server solution, you have multiple options. One choice is to create a cluster of database servers (where all nodes are active at the same time, or, nodes sit passively by waiting to be engaged) that access data from a shared disk. When a failure in the active node is detected, the alternate node is automatically called into action.
How can Tier 3 help?
Designing highly available systems is complex. Unfortunately, no cloud provider can offer a checkbox labeled “Make this application highly available!” in their cloud management portal. Crafting a highly available system involves a methodical approach that navigates through every single layer of the system and identifies single points of failure that should be made redundant. For components that cannot be made redundant, it’s important to make sure that the application can continue to run even if that component becomes unavailable.
The Tier 3 professional services team consists of skilled, experienced architects who have designed and built cloud-scale solutions for customers. They can sit with your team and make sure that you’ve taken advantage of every relevant feature that Tier 3 has to offer, while helping you make sure that your system landscape is constructed in a way that will ensure continual availability.
Don’t forget to regularly test your high availability design in order to uncover weak points or ensure that configurations remain valid.
Disaster Recovery
What is it?
Once more we turn to Wikipedia which defines disaster recovery as:
Disaster recovery (DR) is the process, policies and procedures that are related to preparing for recovery or continuation of technology infrastructure which are vital to an organization after a natural or human-induced disaster. Disaster recovery is a subset of business continuity. While business continuity involves planning for keeping all aspects of a business functioning in the midst of disruptive events, disaster recovery focuses on the IT or technology systems that support business functions.
DR is all about how you handle unexpected events. Typically, your cloud provider has to declare a disaster before explicitly initiating DR procedures. A brief network outage or storage failure in a data center is usually not enough to trigger a disaster response. There are two phrases that you often hear when defining a DR plan. A recovery point objective (RPO) describes the maximum window of data that can be lost because of a disaster. For example, an RPO of 12 hours means that it is possible that when you get back online after a disaster, you may have lost the most recent 12 hours of data collected by your systems. A recovery time objective (RTO) identifies how long the IT systems (and processes) can be offline before being restored. For example, an RTO of 48 hours means that it may take two days before the systems lost in the disaster are brought back online and becoming usable again.
How can Tier 3 help?
Tier 3 customers have disaster protection natively in the platform. We offer two classes of storage: standard and premium. 
The major difference is that standard storage get five days of rolling backups within a given data center, while premium storage users get fourteen days of rolling backups including replication to an in-country data center. Tier 3 is powered by global data centers in multiple countries and we use storage replication to enable you to get back online within 8 hours (RTO) and with a maximum RPO of 24 hours.
While this provides assurances against losing all of your data in the event of a disaster, it still may not provide the level of business continuity that you need. If your business cannot tolerate more than a few moments of downtime, even in the event of a disaster, then it’s critical to architect a solution that can withstand the loss of an entire data center. Returning to our earlier Microsoft SQL Server example, consider the ways to construct a highly available database that remains online with minimal data loss, even during a disaster. SQL Server offers replication technologies like database mirroring and AlwaysOn that make it possible to do near-real time replication across geographies.
The experts in the Tier 3 services team can help you identify all the DNS, networking, compute and storage considerations for building systems that are not only highly available within a data center, but across data centers.
Summary
It’s often the case that load balancing, high availability and disaster recovery lapses don’t surface until it’s too late. While Tier 3 does everything we can to architect our platform for maximum availability and resiliency, our customers still retain responsibility for deploying their systems in a manner that meets their performance and business continuity needs. We are eager to talk to you about how to validate your existing cloud applications or design new solutions that can function at cloud scale. Contact our services team today!
