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.

Why Taking that Vacation Can Lead to a Better Workplace Do you love your vacations? Are they relaxing, fun and entertaining? There are many reasons why a vacation can enrich your life and fulfill you with joy and happiness. But many of these reasons actually can also be directly translated into reasons for why taking that vacation can lead to a better workplace for you, your boss and other employees. Vacations are as essential to a hard working employee as a parachute to a person jumping from an airplane with the goal to land safely. Many employers would love to minimize the time you are gone from your workplace because they think the more time you spend there, the more work you will accomplish. This argument is right up to a certain amount of hours and days a months or a year, but whenever your body starts to get tired and exhausted, the amount of work that you produce decreases. The quality of your work starts to decline as well. Time off work, time together with your family, time to relax, time to regenerate and time to just plain have fun are very important in an employees life. Taking a vacation has many benefits to the employee, but also to the company you work for. The more relaxed and happy your worker starts a workday or the workweek; the better will most likely be his or her performances at work. Research has shown that relaxation and regeneration are essential to human bodies. Did you know that in some companies in Europe and Asia, the emphasis on relaxation goes so far that meditation, morning sport and a short power nap belong to their required parts of a work day? The United States is actually one of the only industrialized countries that does not mandate a minimum of vacation days that the worker has to take off. In fact, in many countries in Europe, a minimum of 20 and more days is the norm. Since the late 1970s, the average middle income family works in total hours three and more months a year more then they did back then and according to a research done by Boston College, approximately 25% of Americans do not take a vacation at all. After all these facts are slowly emerging from mounts of collected date, some of the bigger American companies have actually begun to realize that off-time and vacation are essential to prevent mishaps and screwed up designs and products. If you are not taking your vacation or your employers does not allow for any vacation, a series of health hazards such as stress and high stress, sleeplessness, burnout, heart attacks and even more serious health conditions can occur. Another big factor in working too much, working overtime or never having vacation can be problems and loss of family and friends. Problems with families and friends will directly impact performance at work and even though the employee might not talk about it at work or might b e holding back his or her feelings, the mood and general behavior of the employee will have an impact ion his work and other employees. Every employee should value the vacation time given to him or her and employers should grant the time asked for to their employees. Vacation is essential to the performance at work and the quality in products the company can deliver. Following the examples that are set by many European countries, the US should give their employees the time they need and also make sure that their employees do take the time off to be a better employee overall. Vacation is fun, relaxing and regenerating.

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.