Smart SLA Design for Your SaaS

Service Level Agreements (SLA’s) assure potential customers that your Software as a Service company will live up to your client acquisition team’s promises; however, it is also important to make promises that you can keep, and avoid making promises that are not in anyone’s best interest. Ultimately, you want your new customer to have a long and happy life on your SaaS, and trust is a key component of long-term relationships. Don’t sabotage that with a poor SLA.

Read the full post »

Ten steps to keep your site online during a rush of traffic.

Trying to go viral? Planning on a lot of site traffic? Our techs have helped sites stay online during Super Bowl ad campaigns and opening weekend movie premiers. And along the way, they’ve learned what it takes to stay online during a massive flood of traffic.

So before going live with the next greatest Internet meme, here’s a checklist of what to do to keep your site alive:

  • Understand the scope of the project. How many people will be exposed to your campaign? What is the expected turnover rate? What time of day do you expect traffic to hit your site? How will your site’s application handle a dramatic increase in visitors?
  • Allocate enough time for planning. The right amount of prep time depends on the scope of the project. Is one week really enough time to bring everything together? One month? The bigger the project, the more time you will want in advance to make sure everything goes smoothly.
  • Be prepared for all the what-ifs. Expect the unexpected; people, especially visitors to your site, never behave exactly the way you expect them to. Map out all of the scenarios and have a plan ready for them.
  • Have a back-up and back-out plan. As much as you prepare for success, never assume that failure is impossible. Failing gracefully can make a big impact on retaining the trust of your visitors. Also, you don’t want to lose valuable data. If your site crashes under the load, make sure you can retrieve the data gathered before the crash.
  • Make sure your configuration is scalable. Being able to add an additional web server without downtime means that you won’t interrupt the traffic surge in order to accommodate an unexpected volume of visitors. If your site relies on a database or dedicated application server, make sure you can add more power to these areas, as well.

Read the full post »

5 Easy Steps to Move Your Site to a New Host – Without Downtime or Data Loss!

Minimizing traffic loss and preventing downtime in a server migration comes down to planning. If you do not take care when you move your website, significant outages can take place. This translates to a number of potential negative consequences for your business including revenue loss, impact on search engine rankings, and damaged customer relationships.

Most failed server migrations can be traced back to poor planning and/or a lack of careful execution of a plan. If planned and executed right, successful migrations can result in no downtime or data loss. At minimum, you can severely reduce the impact of a server transfer by following this easy 5 step approach.

What you need to pull this off:

  • Server environments running parallel at your current host and new host. This is a minimum requirement to transition smoothly because taking your old servers down before uploading your data on new servers equals major downtime.
  • The ability to control DNS transfer at the record level with the ability to control Time to Live (TTL) – either through a control panel or via helpful hosting company admins. This is critical in minimizing the time it takes the rest of the Internet to recognize your DNS changes.
  • Attention to detail, because without it you may lose critical data.

Step 1: Setup DNS at your new host before the cutover.

A great way to execute this transfer is to set up DNS at your new host before the “real” DNS cutover. In the new host’s name servers, point the appropriate DNS records related to what you are moving (http, etc.) to your current servers at your current host and set TTL reasonably low (about 10-60 minutes). Most networks on the Internet will recognize DNS changes based on Time to Live, which means if you set this up right, once you make that real cutover traffic will flow to the new servers much quicker. By default, this type of transfer would take anywhere from 12-24 hours to be recognized. That is a lot of time to have customers visiting both sets of servers.

Step 2: At the registrar, point your name servers to the new host.

Read the full post »

Three Reasons for Web Site FAIL.

Today’s websites are expected to be available 100% of the time. The Internet has connected a global marketplace of consumers and businesses where any amount of unplanned downtime can be disastrous for retail orders and/or reputation. If you desire to have a highly available website, study this list of the three reasons websites fail:

1. Management, developers and administrators aren’t invested in disciplined change management.

If you want high availability, you must manage your changes. A stack of shiny hardware alone does not provide uptime. So the last time you suffered a web site outage and during the problem your developers and admins were all claiming innocence that nothing changed, well, odds are they are lying. After you discover the cause, you get the same song and dance, “Oh, well that shouldn’t have caused a problem.”

Anyone with experience in IT will intuitively understand this truth. Luckily, we also have some data to back this up. Donna Scott, VP & Research Director, Gartner, notes that, “80 percent of unplanned downtime is caused by people and process issues, including poor change management practices, while the remainder is caused by technology failures and disasters.” I think our unwillingness to address this truth directly is because we’d rather blame some “system” or “hardware” for root cause rather than the people who should be held accountable for uptime. Throwing money at software and hardware will not solve people problems. Buying the super redundant n+4 failover hot-cold-warm standby solution won’t fix the problem that “Jimmy type-twice-think-once” has root (Administrator) access to the production environment.

Read the full post »

Netcraft Names INetU Top-10 Most Reliable Hosting Company

We are excited to have been named a Top-10 Most Reliable Hosting Company by Netcraft for March 2009!

Based in Bath, England, Netcraft is a popular internet monitoring service that measures the response times of fifty leading hosting providers’ websites. These response times indicate a host’s network capacity and level of congestion; a company with a high ranking has higher capacity and lower congestion on its servers. Measurements are taken every 15 minutes from locations around the world. The companies are ranked by fewest failed requests, a result more reliable than ranking by shortest periods of outage.

INetU often ranks well in Netcraft’s Top 10 Most Reliable Hosting Company Sites, and we can only attribute our success to a dedicated team of skilled network administrators, backing our network performance with a 100% uptime SLA.

For more information about Netcraft’s process, please visit their site.

©1996-2011 INetU Inc, All Rights Reserved.