Welcome to crazydating.net
|
Web Hosting - Changing Web Hosts, Pitfalls and Planning
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.
Web Hosting - Sharing A Server – Things To Think About You can often get a substantial discount off web hosting fees by sharing a server with other sites. Or, you may have multiple sites of your own on the same system. But, just as sharing a house can have benefits and drawbacks, so too with a server. The first consideration is availability. Shared servers get re-booted more often than stand alone systems. That can happen for multiple reasons. Another site's software may produce a problem or make a change that requires a re-boot. While that's less common on Unix-based systems than on Windows, it still happens. Be prepared for more scheduled and unplanned outages when you share a server. Load is the next, and more obvious, issue. A single pickup truck can only haul so much weight. If the truck is already half-loaded with someone else's rocks, it will not haul yours as easily. Most websites are fairly static. A reader hits a page, then spends some time skimming it before loading another. During that time, the server has capacity to satisfy other requests without affecting you. All the shared resources - CPU, memory, disks, network and other components - can easily handle multiple users (up to a point). But all servers have inherent capacity limitations. The component that processes software instructions (the CPU) can only do so much. Most large servers will have more than one (some as many as 16), but there are still limits to what they can do. The more requests they receive, the busier they are. At a certain point, your software request (such as accessing a website page) has to wait a bit. Memory on a server functions in a similar way. It's a shared resource on the server and there is only so much of it. As it gets used up, the system lets one process use some, then another, in turn. But sharing that resource causes delays. The more requests there are, the longer the delays. You may experience that as waiting for a page to appear in the browser or a file to download. Bottlenecks can appear in other places outside, but connected to, the server itself. Network components get shared among multiple users along with everything else. And, as with those others, the more requests there are (and the longer they tie them up) the longer the delays you notice. The only way to get an objective look at whether a server and the connected network have enough capacity is to measure and test. All systems are capable of reporting how much of what is being used. Most can compile that information into some form of statistical report. Reviewing that data allows for a rational assessment of how much capacity is being used and how much is still available. It also allows a knowledgeable person to make projections of how much more sharing is possible with what level of impact. Request that information and, if necessary, get help in interpreting it. Then you can make a cost-benefit decision based on fact. Software copyright act The Software Copyright Act was a Great Step in the Right Direction The software copyright act, which is actually called the Digital Millennium Copyright Act has given software developers a little more power when it comes to protecting their works. If you've bought software in the last few years I'm sure you've noticed some of the changes that have been made in the software buying process. If not, then you really should wake up and take note. Some of the more noteworthy achievements of this act are the following: 1) It is now a crime to go around anti-piracy measures in software. 2) It is no longer legal to make, sale, or give away software or devices that were invented for the purpose of cracking codes enabling the illegal copying of software. 3) Limits the liability that ISPs (as far as copyright infringement violations) when information is transmitted online. The problem isn't the people want to be bad or do something wrong. Most of us by nature want to do the right thing. The problem lies in educating people to the fact that it really is stealing when you bootleg, pirate, illegally download, or otherwise acquire copies of software that you didn't pay for. It's one of those 'white lie' types of crimes for most people and they don't really see how it will hurt anyone for them to copy a game that their brother, cousin, uncle, or friend has. Someone paid for it after all. The problem is that at $50 plus being the average price for computer games and simple software if 10 million people are doing it, the numbers are staggering and they add up quickly. The software copyright act sought to protect businesses from losing money this way. The software copyright act was the worldwide response to a growing problem. This problem was so widespread with illegal downloading of music that lawsuits and massive commercial ad campaigns were initiated in order to curtail illegal downloading activities when it comes to music. It seems to be working to some degree. Fewer people are illegally downloading music; the downside is that these people aren't buying as much music either. The reason is because they are no longer being exposed to the wide variety of music and artists that they were getting freely when downloading music each night at no cost. This equals lower record sales and is becoming a problem of lower movie sales and software sales as well. People aren't trying new games like they could before the software copyright act by going to LAN parties and everyone sharing a copy to play, now everyone has to own a copy before they can play. While this may be great for the companies that make a few (a minimal few at best) extra sales on the games for the sake of a great party but for the most part, it is costing them the extra money that could be made by 10 people finding they liked the game enough to go out and buy it so they could play it whenever (and the next group of 10 they will introduce the game to) Gamers are a funny group and software copyright act or no, they are going to stick with the software and games that serve them best. The software copyright act was created in order to protect the rights of those writing and developing computer software. We want those who fill our lives with fun games, useful tools, and great ways to connect to friends and family to continue providing these great services and to get paid for the ones they've already provided. The software copyright act is one giant step in the right direction as far as I'm concerned. |