Welcome to elreno.org
|
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.
Web Hosting - Redundancy and Failover Among the more useful innovations in computing, actually invented decades ago, are the twin ideas of redundancy and failover. These fancy words name very common sense concepts. When one computer (or part) fails, switch to another. Doing that seamlessly and quickly versus slowly with disruption defines one difference between good hosting and bad. Network redundancy is the most widely used example. The Internet is just that, an inter-connected set of networks. Between and within networks are paths that make possible page requests, file transfers and data movement from one spot (called a 'node') to the next. If you have two or more paths between a user's computer and the server, one becoming unavailable is not much of a problem. Closing one street is not so bad, if you can drive down another just as easily. Of course, there's the catch: 'just as easily'. When one path fails, the total load (the amount of data requested and by how many within what time frame) doesn't change. Now the same number of 'cars' are using fewer 'roads'. That can lead to traffic jams. A very different, but related, phenomenon occurs when there suddenly become more 'cars', as happens in a massively widespread virus attack, for example. Then, a large number of useless and destructive programs are running around flooding the network. Making the situation worse, at a certain point, parts of the networks may shut down to prevent further spread, producing more 'cars' on now-fewer 'roads'. A related form of redundancy and failover can be carried out with servers, which are in essence the 'end-nodes' of a network path. Servers can fail because of a hard drive failure, motherboard overheating, memory malfunction, operating system bug, web server software overload or any of a hundred other causes. Whatever the cause, when two or more servers are configured so that another can take up the slack from one that's failed, that is redundancy. That is more difficult to achieve than network redundancy, but it is still very common. Not as common as it should be, since many times a failed server is just re-booted or replaced or repaired with another piece of hardware. But, more sophisticated web hosting companies will have such redundancy in place. And that's one lesson for anyone considering which web hosting company may offer superior service over another (similarly priced) company. Look at which company can offer competent assistance when things fail, as they always do sooner or later. One company may have a habit of simply re-booting. Others may have redundant disk arrays. Hardware containing multiple disk drives to which the server has access allows for one or more drives to fail without bringing the system down. The failed drive is replaced and no one but the administrator is even aware there was a problem. Still other companies may have still more sophisticated systems in place. Failover servers that take up the load of a crashed computer, without the end-user seeing anything are possible. In fact, in better installations, they're the norm. When they're in place, the user has at most only to refresh his or her browser and, bingo, everything is fine. The more a web site owner knows about redundancy and failover, the better he or she can understand why things go wrong, and what options are available when they do. That knowledge can lead to better choices for a better web site experience. 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 |