Welcome to www.minisinbox.com
|
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 - Why Backups Are Essential One thing most web site owners have little time for is... anything! Anything other than focusing on their site content and the business or service it supports and the information it provides, that is. That means that administration often suffers, as it frequently must. There's only so much time in the day. But the one thing that you should never let slide are backups. They are like insurance. You rarely need it (you hope), but when you do you need it very badly. Performing regular backups - and testing them - doesn't have to be a nightmare. A little bit of forethought and effort and they can be automated to a high degree. And, they should be tested from time to time. Even when a backup appears to have gone without a hitch, the only way to know whether it's of any value is to attempt to restore the information. If it can't be restored, the backup is worthless. Even when the web hosting company provides the service, there is still some planning involved for the site owner. Hosting companies often rely on one or both of two methods. They backup everything (called a full backup), then backup anything which has changed since the last full backup (called an incremental backup). Of special interest are any configuration files that have been tailored. If you've modified the default installation of a software package, you want to be able to recapture or reproduce those changes without starting from scratch. Network configuration files, modifications to basic HTML files, CSS style sheets and others fall into the same category. If you have XML files, databases, spreadsheets or other files that carry product or subscriber information - about items purchased, for example, or people who signed up for a newsletter - those should get special attention, too. That's the lifeblood of your business or service. Lose them and you must start over. That can break your site permanently. It should go without saying that all HTML and related web site files that comprise visible pages should be backed up regularly. It isn't necessary to record every trivial change, but you can tailor backup software to exclude files or folders. Usually they're so small it isn't worth the trouble. But in some cases those small changes can add up in scenarios where there are many thousands of them. Here again, the backups are worthless if they can't be used. Even if the hosting company charges for doing so, it's worthwhile to test once or twice a year at least to ensure the data can be restored. That's especially true of database backups, which often involve special software and routines. Database files have a special structure and the information is related in certain ways that require backups be done differently. Developing a backup strategy can be straightforward. Start simply and review your plan from time to time, modifying it as your site changes and grows. But don't neglect the subject entirely. The day will come when a hard drive fails, or you get hacked or attacked by a virus, or you accidentally delete something important. When that day comes, the few minutes or hours you spent developing and executing a backup plan will have saved you days or weeks of effort. Patent and copyright law Understanding Patent and Copyright Law Patent and copyright law gives the inventor the exclusive rights to the invention. No one else can produce the invention for a set period of time under patent and copyright law. Patent and copyright law is set up to protect inventors. The law on patents can be found in the United States Constitution, Article 1, Section 8 and in Title 35 of the United States Code. The agency that is in charge of patent laws is a Federal Agency known as the Patent and Trademark Office. Anyone who applies for a patent will have their application reviewed by an examiner. The examiner will decide if a patent should be granted to the inventor. Individuals who have their patent application turned down can appeal it to the Patents Office Board of Appeals. Just because someone has a patent does not mean that they have the right to use, make or sell the invention. For instance, if a drug company comes up with a new drug, they can get a patent on it. However, it would not be available to be sold to the general public until the drug becomes approved by other regulatory bodies. Likewise, someone may invent an improvement to an existing product, yet they will not be allowed to produce or sell the item until they obtain a license to do so from the owner of the original patent holder. For someone to receive a patent, as stated, they must fill out an application on their invention. The application will entail the details of the invention and how it is made. In addition, the person applying for a patent must make claims that point to what the applicant deems or regards as his or her invention. A patent may have many claims with it. The claims protect the patent owner and notify the public exactly what the individual has patented or owns. If someone infringes upon patent and copyright law, it is usually enforced in a civil court setting. The owner of the patent will generally bring a civil lawsuit against the person who has infringed upon their patent and ask for monetary compensation. In addition, the patent owner can seek an injunction which would prohibit the violator from continuing to engage in any acts that would infringe upon their patent in the future. Many patent owners will make licensing agreements (or contracts) with others. These agreements allow another person or company to use someone’s patented invention in return for royalties. In addition, some patent holders who are competitors may agree to license their patents to each other to expand both of their profits. Most everything we use in our day to day life was invented by someone. That person had to seek out a patent for their invention. Patent and copyright law protects inventors from having their ideas and inventions stolen out from under them. This makes the playing field more level for individuals. Without these laws, the marketplace would be out of control and the small guy would probably be eaten alive by big business |