The Gadget Blog - New Gadgets & Tech Talk » Web Hosting

Changing Web Hosts, Pitfalls and Planning

Jennifer — Fri, 31 Aug 2007 23:48:29 +0000

At some point, nearly everyone finds it necessary to change web hosts. It may be just a migration to another server, or it may be changing web hosting companies entirely. Either way, the process is fraught with potential dangers. But there are ways to minimize the odds of problems and maximize your changes of a smooth migration.

Plan, plan, plan.

Make a very detailed list of everything that is on your current system. Review what is static and what changes frequently. Note any tailoring done to software and files. Be prepared to remake them if the systems aren’t transferred properly or can’t be restored. Keep careful track of all old and new names, IP addresses and other information needed to make the migration.

Backup and Test

Backup everything on your system yourself, whenever possible. Web hosting companies typically offer that as a service, but the staff and/or software are often less than par. Often backups appear to go well, but they’re rarely tested by restoring to a spare server. When the time comes that they’re needed, they sometimes don’t work.

Do a dry run, if you can. Restore the system to its new location and make any needed changes. If you have the host name and or IP address buried in files, make sure it gets changed.

This is often true of databases. SQL Server on Windows, for example, picks up the host name during installation. Moving a single database, or even multiple ones, to a new server is straightforward using in-built utilities or commercial backup/restore software. But moving certain system-related information may require changing the host name stored inside the master database. Similar considerations apply to web servers and other components.

Accept Some Downtime

Be prepared for some downtime. Very few systems can be picked up, moved to another place, then brought online with zero downtime. Doing so is possible, in fact it’s common. But in such scenarios high-powered professionals use state-of-the-art tools to make the transition seamless. Most staff at web hosting companies don’t have the skills or the resources to pull it off.

Prepare for Name Changes

One aspect of moving to a new host can bedevil the most skilled professionals: changing domain names and or domain name/IP address combinations.

When you type a URL into your browser, or click on one, that name is used because it’s easier for people to remember. www.yahoo.com is a lot easier to remember than 209.131.36.158. Yet the name and or name/IP address combination can (and does) change. Still, specialized servers called DNS (Domain Name System) servers have to keep track of them. And there are a lot of them.

There may be only two (rarely) or there may be a dozen or more DNS servers between your visitors’ browsers/computers and your web host. Every system along the chain has to keep track of who is who. When a name/IP address changes, that pair has to be communicated to everyone along the chain, and that takes time.

In the meantime, it’s possible for one visitor to find you at the new place, while another will be pointing to the old one. Some amount of downtime will usually occur while everything gets back in sync.

The Little Gotchas

But even apart from name and IP address changes, there are a hundred little things that can, and often do, go wrong. That’s not a disaster. It’s just the normal hurdles that arise when changing something as complicated as a web site and the associated systems that underlie it.

Gather Tools and Support

Having an FTP program that you’re familiar with will help facilitate the change. That will allow you to quickly move files from one place to the next to do your part to get the system ready to go or make repairs.

Making the effort to get to know, and become friendly with, support staff at the new site can be a huge benefit. They may be more willing to address your problem before the dozen others they have to deal with at any given moment.

Ok. On your mark. Get ready. Go.

When Changing Web Hosts

Jennifer — Thu, 30 Aug 2007 23:49:38 +0000

Nearly everyone will want to change to a new web host at some point. It may involve just changing out old hardware for new. It usually means finding an entirely new web hosting company. When faced with that decision there are a number of issues to be considered.

Swapping hardware and/or software is a fairly straightforward decision. There are two possible scenarios. Either you maintain your own hardware and software at a facility managed by others, or you are considering upgrading to newer (usually more expensive) systems maintained by others.

In either case, it’s simply a matter of estimating the cost and the short-term impact versus the long-term benefits. If the system(s) you currently use are short on capacity, sooner or later you’ll be sufficiently motivated to make the change. Either the hardware will become unreliable or loaded to the point you’ll be forced to migrate, or your needs will expand enough to justify the effort and expense of moving.

Similar considerations apply to the scenario in which you rely on the web hosting company for everything, and want to find someone else to rely on. Regrettably, that’s a very common situation. Many web hosting companies provide systems and staff that sooner or later fall below an acceptable level.

Most people make the decision to change based on emotion. That’s not entirely bad. Emotions incent you to take action. But you need to keep a cool head, too, in order to calculate your long-range self-interest. Bearing some minor inconveniences from time to time is usually worth the trade off. When it begins to affect your site to the point you’re losing visitors, it’s time to make a change.

To get a more objective handle on when that point is reached, reach for some numbers. Maintain, or get from the hosting company, a factual report about availability and current usage. If the server is down so much, or so heavily loaded, that it drives your visitors away, it’s time to take action.

There are other less easily quantifiable but equally important factors, as well.

You will at some point need to communicate with one or more persons who help maintain your site. Even if you do all your own server, database and web site maintenance, someone behind the scenes is helping to keep things running smoothly. That’s called ‘infrastructure’. If the road you drive on has potholes, it’s not enough that you can fix your own car.

In terms of network bandwidth and availability, server capacity, disk space, security and a whole array of other aspects, the web hosting company has to have competent people who care (and are allowed) to do the job well. When the company’s people fall down – because of incompetence, lack of resources or absence of a culture of excellence – or for any other reason – your web site suffers. This issue more than any other is what drives people to seek another web hosting company.

Even if you choose well at the outset, things can change. Management changes, staff changes and companies are taken over by other companies. Sometimes, it isn’t simply a matter of swapping out an unreliable piece of hardware or software. When it’s time to swap out people, you look for the same aspect: doing the job required.

Databases, What Are They and Do You Need One?

Jennifer — Wed, 29 Aug 2007 23:50:04 +0000

‘Database’ is one of the most commonly used terms that one encounters in web site design. Yet, what they really are and whether they’re essential is often not clear to novices.

A database is a collection of organized data, stored in files that have a specific structure. It’s that organization and structure that allows for easy and rapid storage and retrieval.

The need for a database generally only arises when you have a certain amount of information and that information needs to have some structure. If you have a half-dozen names and addresses to store, a database is usually overkill. If you have a blob of data with no relationships between any of the items in that blob, maintaining a database is usually more trouble than it’s worth.

Maintain a database? Yes, like other complex systems a database, to be effective, needs to be designed properly at the outset then kept ‘tuned’ for good performance. The alternative is to gradually allow the database to become more and more disorganized. That leads to difficulty in use, poor speed of retrieval and more frequent failures.

With MySQL, Access or MS SQL Server, the three most common choices of database product for web sites today, setting up a database is relatively simple. Even those with limited technical skill can get one up and running just by following some simple instructions. But some thought should be given to how you want the information organized, and to maintaining the system during its lifetime.

Suppose you have a set of names, addresses, email addresses, products purchased, date purchased and amount. If you have only a few dozen records it matters very little how these pieces are arranged and related. A database usually isn’t even warranted in this scenario. Once you have several thousand or more records, it matters a lot. Speed, the ease of expanding the set of attributes (like adding, say, product category), and other issues come into play.

Even those with little technical expertise, but a willingness to exert logical thought and invest some time, can build a very robust database. Think about how you would organize a set of data (called ‘tables’). Should Name, Address, and Product be in the same table? Or should the personal information be stored in one table and any product information (product, price, …) in another?

Some experimentation may be needed to get it right, but the choices have an impact on how easy the tables are to maintain. It also affects the speed with which programs can fetch old data and store the new.

Having a database also introduces new maintenance issues for the server administrator, since backups usually need to be done differently. Recovering a failed database is usually more complicated than simply re-copying files from yesterday. Ask your hosting company what tools and skills they have for dealing with any database system you consider.

It’s true that introducing a database creates more complexity and the need for additional thought and administrative effort. At a certain level, professional expertise will be needed. But clearly the advantages outweigh the costs in many cases. Companies large and small eventually use databases to store and organize data. At some point, you may be fortunate enough to be one of them.

DNS, How The Internet Keeps Track of Names

Jennifer — Tue, 28 Aug 2007 23:50:29 +0000

The way computers communicate is, in a way, very similar to something very familiar: the postal system that delivers letters and packages. Here’s how…

The Internet is just what the name suggests, a large inter-connected set of networks. But those networks are pointless without the one part that forms what is called their ‘end-nodes’, otherwise known as computers. Those computers often need to share information because the people who use them want to share information.

But, in a system where there are millions of separate computers, how can you enable them all to communicate? One very important feature of that solution is performed by something called DNS, the Domain Name System.

Every part of a network that is going to send or receive information is assigned an IP address. That’s a numeric identifier that uniquely specifies a particular ‘node’, such as a computer, a router that directs traffic or other component. They look like this: 209.131.36.158

But those numbers are more difficult for people to remember and work with. They also aren’t very attractive from a marketing perspective. So, a naming system was layered on top of some of them, mostly the computers involved, though routers have names, too.

But once you have a system that associates a unique IP address to a given name, you need some way of keeping track of all of them. That’s carried out by several different pieces of the system: Name Registrars, DNS Servers and other components.

The Name Registrars, overseen by IANA (Internet Assigned Numbers Authority) and other international bodies, provide and keep track of domain names. When you register with GoDaddy or any of a hundred other intermediate companies, ultimately that information makes its way into a number of specialized databases stored inside DNS Servers.

A DNS Server is the hardware and/or software that tracks and forwards the IP Address/Domain Name pair from one place to the next. In many cases, there are a number of them between your browser and the remote computer you want to share information with.

Suppose you request information from, say, Yahoo’s site by clicking on a link on their site. DNS resolves (translates) the name of WHO IS making the request and OF WHOM, to addresses, then passes the request through the network to the requested IP address. The requested data is then passed back through the mesh of network components to your computer and displayed in your browser.

Whether the communication is between a desktop computer and a server somewhere, or between one server and another, the process is essentially the same. DNS servers translate names into IP addresses and the requests for data are forwarded on.

In some cases those DNS servers are part of a specialized network computer whose sole job is to do the translation and forwarding. In other cases the DNS software may reside on a server that also houses a database of general data, or stores email, or performs other functions.

But however complicated the chain or the parts, the basic process is simple. Translate the name to an address, just as the postal system does. Whether international or local, your name is associated with an address, and the deliveries are made to the address, then forwarded to a particular name.

Web Hosting: Do It Yourself Administration, Things to Consider

Jennifer — Sun, 26 Aug 2007 23:51:01 +0000

The choice of whether or not to try to administer your own web site brings with it a host, pun intended, of issues.

For most web site owners, the primary focus is naturally on creating, maintaining and enhancing the site. That often is just part of managing an entire business, for which the web site is just the means to an end.

That implies there will be little interest in or time left over for technical administration like database maintenance (tuning, space management, security, bug fixes), establishing and maintaining backups to ensure they’re successful and usable, email administration, disk space management, applying operating system fixes for bugs and security, and other tasks.

But cost is always a factor in any business. Paying for technical help can burden the budget of a new and struggling business.

Consulting fees can range from a few dollars an hour to over $100. On the lower end, the poor skill level and quality of work will make it not worth even that small amount. On the higher end, you can quickly rack up expenses that will bust your business.

Permanent employees are usually somewhere in the middle of that range when you add up salary, employment taxes and more. Often, server and/or web site administration can be paid for as part of the web hosting package. That cost is usually lower than independent contracting help, but those staff are usually tasked with maintaining dozens if not hundreds of servers and sites. They can, therefore, give very little individual attention to yours.

Often, novice web site owners are intimidated by some of the technical requirements for server or site administration. But, as with anything, a little familiarity can show that the knowledge required is more modest than one might expect. Administration in many cases involves fairly elementary, and frequently repetitive, tasks. These can be learned easily. Using a test site or a free hosting service is a good way to practice and learn without risk or cost, other than time invested.

Once that initial hurdle is jumped over, administration can be done quickly and some even find it interesting. It allows the site owner to exercise additional control over the total product, and there’s satisfaction in being able to say ‘I did that’ even if you prefer not to do it forever.

That real-life learning experience also allows the site owner to better judge any consultants or staff that are hired. It’s much easier to judge if someone is providing you with an accurate assessment of a problem if you’ve solved it yourself. Any time-estimate they provide to fix it can also be better calculated if you’ve had to do it yourself.

Every web site relies on a variety of factors, usually unseen, in order to continue to function properly. But the fact is that they misbehave from time to time. Deciding whether to tackle those problems yourself depends on your available time and skill set, and what it will require to get things back on track. In other words, it’s a standard cost-benefit analysis that everyone has to undertake every day in life.

Domain Name Changes and How They Affect You

Jennifer — Sat, 25 Aug 2007 23:51:42 +0000

New domain names are registered all the time, and ones previously registered expired. Sometimes that’s the result of simple neglect. The owner of the name chose not to renew his or her ownership, so the name became available for someone else to use. In rare cases, a highly original mind managed to think of a new one. In the other common scenarios, someone chose to just let it go or sell it.

When you choose to change your domain name, there are actually two separate steps involved: releasing the old name, and adopting the new one. But, just as the postal system can have difficulty forwarding your letters when you change your personal name, changing your domain name brings certain difficulties.

One of the most prominent is the fact that any name change requires a change to thousands of DNS Servers around the globe. DNS (Domain Name System) is the set of software/hardware components that allows domain names to map to IP addresses. IP addresses are what are actually used ‘under the covers’ when one computer communicates with another.

Note that there isn’t always a 1:1 correspondence between a name and an IP address. One IP address can serve multiple domain names and one domain name can have multiple IP addresses. For the sake of simplicity, we’ll stick to the common case here.

DNS servers around the world maintain internal databases that match the name to an IP address. Not all servers have all pairs of names/addresses. A series of complex routines allows a request to be forwarded when the particular DNS server doesn’t have a needed record. When you acquire a domain name that used to be associated with a given IP address, the odds of you acquiring the same IP address are extremely low.

In the unlikely case, for example, that you acquired the domain name yahoo.com, you would almost certainly not get the IP address that was matched with it (unless you bought the Yahoo! company). So, as a result of the change, the name/IP address pair is no longer what it was.

A similar circumstance exists when you retain your IP address, but want to change the domain name associated with it. In either case, the pairing has changed.

The catch is this: when the change takes place, those DNS databases are not all updated instantaneously around the world.

Even apart from the limited speed with which computers and networks operate, (and neglecting the human factor if/when the change is made manually to more than one server) the reason is something called caching.

In order to communicate efficiently, DNS servers are designed to assume that changes will be relatively rare. Just as with the postal system, you don’t move your address or change your name every minute. Since that’s true, in general, the name/IP address pair is cached. A cache is a set of stored information that is reused so that fresh information doesn’t have to be communicated with every request for a web page or data.

A chain of DNS servers pass requests to the last known address. There is usually more than one system between your computer and the server you want to communicate with. Most of the time, that’s your current name/address. When you change the name, that pair is no longer valid. In order to propagate the new name/address pair (so the terminology goes), that cache has to be refreshed.

Something similar happens when you establish an entirely new name. That name is first associated with an IP address and that pair has to be communicated to DNS servers around the world in order for you to be able to reach any one of them at random.

But DNS servers don’t do that until they are requested to do so by your action of asking for information from a remote server. Because of that, but chiefly because of caching, it can take quite a while for the new pair to become known around the Internet. Caches can expire and get refreshed in a few minutes or a few hours. It varies.

That time can be as short as an hour or less, if the path between your computer and the web server is very simple and only one DNS server needs to be updated. Or, it can take up to 48 hours or more. Though the ‘official’ range is often given by registrars as 24-48 hours, the average is closer to about six hours. But that’s an average. The actual time in any given case can (and does) vary widely.

In the meantime, a number of effects can occur. The most obvious is that, since the name/IP address pair can’t be resolved properly, you don’t reach the server you want. Your browser points to the old one (in the rare case it’s still accessible by that name and address), or it simply reports there’s no such name at that address.

So, when registering a new name or buying an old one, you should establish the site, but not advertise it for at least a couple of days. Better to wait to get visitors than to turn them off by being ‘not at home’ when they call.

Web Hosting & Email Issues

Jennifer — Fri, 24 Aug 2007 23:52:06 +0000

When you build a web site, you often provide a means for users to communicate with you. One of the most common ‘add-ons’ to a web site is the addition of some kind of email access. Email is used to sign users up for newsletters, provide communication for administrative issues and a hundred other uses. But, as everyone sadly knows, email problems can occur.

Virus infection is among the most common, though the situation is actually better today than in the past. Huge efforts, and some progress, has been made over the past 10 years to reduce the number and severity of virus attacks. Hackers haven’t surrendered, far from it. But they’re on the defensive like never before.

Many of those viruses were (and are) spread through email, usually in the form of email attachments. That’s the source of the now-common advice never to open an attachment from someone you don’t know. Professionals will often extend that advice to suggest you never open an attachment that’s unexpected, even if it’s from someone you know. Well-meaning, but computer-challenged friends often accidentally forward virus infected emails.

Spam has taken over the top spot for email annoyances. It’s estimated by various different professional sources that 92-97% of all email sent today is spam. While the definition varies, spam is generally regarded as any unwanted commercial email sent by someone whom the recipient doesn’t know or have a business relationship with.

Spam clutters email inboxes, requires people to sift through to find valid messages, and often contains offensive messages in some form. But, it’s a fact of life and isn’t going away anytime soon. Even though laws are in place, thousands of spammers continue to risk fines or jail for the chance of making money from that small percentage who will open the unwanted email.

Other forms of email problems are even more severe for many web site owners. When the mechanisms fail that they rely on to send and receive messages to and from their users, that’s a problem. Dealing with those problems can range from sending an email or instant message to an administrator, to tracking down the right person to get your site removed from a blacklist.

Email is the communications vehicle of choice for millions everyday. When the system burps, someone has to take time to do something about it. Often, that means relying on a person who is already overburdened with too many issues to resolve.

So, besides pointing out some sad facts or complaining, what’s the point? All of the above shows just one more area you should look at when selecting a web host or deciding whether to move to another. Just as with server or network administration, companies vary in their ability to deal with email-related issues. Some are responsive and super-competent. Others, are simply indifferent or worse. And many are in between.

Email administration, like server maintenance or network management, is a professional specialty. Skill in one does not necessarily mean quality work in another. Finding a web hosting company and/or system that has few email problems, and solves them quickly when they occur, is an important task. Spend some time researching who provides superior support in email. You’ll be happy you did.

Free vs Paid Web Hosting Options

Jennifer — Thu, 23 Aug 2007 23:52:34 +0000

Everyone likes to get something for free. But as the existence of spam shows, free isn’t always good. Sometimes, it’s downright harmful. Deciding whether it’s worth the cost to pay for hosting involves a number of complex considerations.

Hosting companies that offer free services obviously can’t stay in business from the money they make from you, since there isn’t any. So why do they offer free hosting and how do they make money? Why should you care, so long as you get yours? Because, in reality, there’s a price of some kind for everything, even something that’s free.

Free hosting may come from a company doing a promotion to attract business. They expect to demonstrate their value, then charge an existing customer base fees to make up for what they lost by the (short term) offer. It’s in essence a form of advertising.

But free hosting is offered by lots of companies that are not dedicated to managing servers for websites. Google, Yahoo and thousands of others provide a modest amount of disk space and a domain name on a server for free. Users are free to do anything they like with it, though if the load becomes excessive you can be shut down.

That introduces one of the more obvious drawbacks to free hosting: resource limitations.

Typically free hosting offers a relatively small amount of space. That’s often enough to host a few dozen pages. But an active site can quickly run out of room.

A more serious limitation is load.

Free hosting often places strict limitations on the allowed amount of bandwidth consumed. If you become a well-visited site, when users start banging away on the server, you can be asked to leave or simply be blocked for the rest of the month. Or, you may be permitted a certain quantity of total bandwidth use per month. Once it’s reached, no one else can reach your site until the beginning of a new month.

At the same time, you will certainly be sharing equipment with thousands of other sites. Their load can affect your performance, prompting you to move. Migrating an established site brings with it a number of thorny issues that might be better avoided in the first place.

Free hosting has another potential downside: lack of support. When you pay for hosting you typically get, at least in theory, a certain level of support. Backups in case of disaster recovery from a hack or server failure, assistance in analyzing connection problems… the variety is endless. With free hosting you usually get none of that.

A company or site that offers free hosting will usually recover a disk or server that fails completely and you’ll be back up when they do. But if only selected portions of the drive fail, or you lose a few files through a virus attack or accidental deletion, you have to rely on backups to recover. A free service will usually come with no such option.

That may not be a problem if you have a small site. You can make copies of everything at another location and simply recover the site yourself – if you have the discipline to keep it current and the skills to make and restore the copy.

Free hosting will typically come with a few email addresses, intended to be used for administration and other tasks. But if your needs grow beyond that, you’ll need to seek another option. The email service also comes with minimal oversight. The server may be protected against spam attacks and provide virus scanning. But few free services will provide even minimal help with any issues that arise.

But the most serious limitation may have nothing to do with any technical issues. Free hosting services often require that your site’s pages carry some form of advertising that pays the host, not you. That may be fine for you, or it may not. Individual circumstances vary.

On the other hand, if you’re just starting out, a free hosting option can be a great way to learn needed skills and a few of the potential pitfalls. You can set up a site, learn how to maintain and improve it, and not care too much if it gets hacked. Freely hosted sites can be a great platform for learning the ropes.

Free services don’t usually offer any of the features that an active, commercial site will need sooner or later. So if you plan to grow, it may be reasonable to get the free service for a while, knowing you’ll have to migrate when you become popular. But in the long run, you get what you pay for and you may need to pay for what you want.

Visit our favorite hosting place – HostGator – by clicking the link below!

FTP and Other File Transfer Tools

Jennifer — Tue, 21 Aug 2007 23:52:58 +0000

Anything related to the Internet or computers is bound to introduce technical issues pretty soon. One of the earliest that novice web site owners encounter is FTP, which is an acronym for File Transfer Protocol. Seeing it spelled out, it’s easy to see why those in the know quickly move to speaking in short hand.

The reason web site owners soon will (or need to) become familiar with FTP is obvious to anyone who has built a site on a remote server. You have to have some way of getting the files to the remote computer and FTP is one of the most common tools. It’s also one of the simplest and most efficient.

FTP is composed of two parts: the client software and the server software. It’s similar, in a way, to talking to someone on the phone who writes down everything you say. You (the client) make a request (’transfer this file to the server’) and the listener (the server) takes the request and acts on it.

That request to copy a file from a local computer to the remote one is carried out (often ‘under the covers’) by a PUT command, as in PUT this there. You create the web page (in the form of a file) and then PUT the file on the server. To move a file in the opposite direction, from the remote server to your local computer, your client software issues a GET command.

Many FTP clients have graphical interfaces, similar to Windows Explorer, that allow you to drag-and-drop or otherwise copy the file without ever seeing the actual commands that carry it out. But it’s helpful sometimes to know what goes on underneath. In tricky cases it can be an advantage to use a command line interface (in Windows, the ‘DOS box’, with a similar interface familiar to most Linux users).

Knowing the commands and being able to use them in the command line form can sometimes help you diagnose what is going on when the graphical tools misbehave.

But FTP is not the only way to get a file from here to there. In fact, your browser moves files around from a remote computer to your local one all the time. In most cases, when you type in or click on a URL, what happens under the covers is in essence a file transfer process. The web page is transferred from the web server to your local computer then displayed by the browser.

Alternatively, you can sometimes even email a web page/file from your local computer to the remote server, then use an email client on the server itself to get the file and put it in a folder. That requires that you have some form of access to the remote computer. But there are many ways of doing that, such as in-built utilities in the operating system or using commercial remote control programs.

Those alternatives can be helpful to know in cases where the FTP file transfer process is misbehaving. Having more than one way to accomplish the task helps you diagnose what might be going wrong. It also helps you get the job done when the usual tools aren’t cooperating.

The more you learn about these sometimes puzzling acronyms, the easier you can accomplish your own goals.

How To Select A Web Host

Jennifer — Sun, 19 Aug 2007 23:53:22 +0000

As with many purchases, our first impulse when selecting a web hosting company is to go with the cheapest. Hey, they’re all alike, why pay more? Au contraire.

There are a number of objective criteria that separates one web hosting company from another and money is only one of them. And not the most important one. Selecting a company based on price alone is equivalent to selecting an auto mechanic on price alone. Sure, he may maintain or fix your car cheaper. But will the car spend all the time in the shop and none on the road?

The first consideration is ‘horsepower’. Do they have the capacity to carry your load and deliver decent performance? Most hosting companies will advertise that they have huge bandwidth and hundreds of servers. They’re usually telling the truth.

But there’s a difference between existing capacity and usable capacity. If they also have thousands of sites with millions of visitors per day the available or free capacity will be much lower. A big pickup truck may be able to tow 5,000 lbs. But not if it’s already carrying 4,999.

Be sure to ask about available capacity, and have the prospective company back it up with reliable numbers. If you can’t interpret the information they provide, find someone to help you do so.

Next, and a very close second, is reliability. A lot of power is worthless if it’s cut often. Outages are a normal part of business. Even Google and Microsoft go down from time to time. The difference is, it happens rarely and they have failover plans. That means, if their site/system does go down it’s either up again in a flash, or you never see the outage because a backup system kicks in automatically and seamlessly.

Be sure to grill the company closely about their up time. They’ll often tout 99.6%, or some such figure. But, like the on-time figures of the airlines, those numbers can be shaded by adjusting the definition of ‘up time’. What matters to you is whether your visitors will be able to reach your site at any time of the day or night they might want to.

Find out what systems, both technical and human, they have in place to deal with failures of all sorts. Servers can go down, networks can fail, hard disks can become defective and lose data even when the other components continue to work fine. The result is YOUR site is unavailable, which is all that matters to you. The web hosting company should be able to deal with all of that and have you up again very quickly.

Last, but not least, is security. With the continuing prevalence of viruses and spam, you need to know that the web hosting company you select has an array of methods for dealing with them. That means a good technical plan and staff who are knowledgeable in dealing with those issues. The old saying: ‘an ounce of prevention is worth a pound of cure’ is more true here than anywhere else.

All these issues are central to finding a web hosting company that can deliver the services you need. After those criteria are satisfied by a number of candidates, then you can start narrowing them down by price.