search the articles directory
Powered by Google™
old Servers articles
File and Print Server Failures - ...ddeningly, intermittent
network failures.
Networks are also affected by configuration problems. Incorrect routing
information, duplicate host...
Web and Application Server Failures - ...in the web server environment where things might go awry.
There are many new places for bugs to crop up, including in the Common
Gateway Interfa...
Your system fails because the operating system panics - ..., however, in which repairing a system changes the MTBF characteristics of the system, increasing the probability of another failure
in the near-te...
Direct and Indirect Costs of Downtime - ... downtime is probably not the most expensive one:
lost user productivity. The actual cost of that downtime is dependent upon
what work your user...
COST OF DOWNTIME IS NOT A CONSTANT - ... few seconds), the cost will be minimal, perhaps even
negligible. An outage of a minute or less probably will not affect business too
badly: All...
The Politics of Availability - ...y to convince others of the value of your ideas is to first
convince them that your ideas will help them achieve their own goals. To do
that, yo...
Rational case that explains in nontechnical terms - ...colleagues who share
your concerns. Maybe you’ll find someone who has tried to convince management
of something in the past. At the very l...
20 Key High Availability Design Principles 1 - ... costs.
The decision to implement availability is a
business decision. It comes down to dollars and cents. If you look at the business
decis...
Consolidate Your Servers - ...ger servers with a capacity greater than all of the replaced
servers. This setup can significantly reduce the complexity of your computing
envir...
Documentation provides audit trails to work that has been completed - ... (These can be very handy
at personnel review time.) Good documentation can also help with problem
solving.
1. The first audience is the...
Keep your production and development environments separate - ...ossible. Even better, the same users
should perform the tests. The tests need to be performed with the same production
network configuration and...
Two relational database management systems - ...mature software product. As far as we know, Joe has not
yet released a database.) Joe’s product has a couple of features that make it a
li...
User documentation is often a good starting point - ...o architect and implement your plans.
Arrange for on-site consultation from vendor resources or independent contractors,
and be sure a transfer-...
Incremental Backups of Databases - ...
database upon restore.
Some solutions require a complete scan of the database for changed blocks.
At least one solution (VERITAS NetBackup w...
Hierarchical Storage Management - .../p>
Consider this: Those files that haven’t been touched in 6 months or more
still take up valuable time, space, and bandwidth during you...
latest articles under "Servers"
Navigation: Categories » Computers and technology » Servers
Below is a list of all Servers articles. If you want to find a tutorial by keywords, all you have to do is a quick search in our directory. Just use the search option available at the top-right side of the page. The website search is powered by web-articles. Or, if you want to read specific Servers tutorial, just point to it. The newest articles and tutorials are shown first in the list. To access the last ones, browse the pages 2, 3, 4... at the bottom. Also, you may browse articles alphabetically ordered.
Page# 1 (last added articles shown first)
Enter page# 1 (last added articles shown first)
Below is a list of all Servers articles. If you want to find a tutorial by keywords, all you have to do is a quick search in our directory. Just use the search option available at the top-right side of the page. The website search is powered by web-articles. Or, if you want to read specific Servers tutorial, just point to it. The newest articles and tutorials are shown first in the list. To access the last ones, browse the pages 2, 3, 4... at the bottom. Also, you may browse articles alphabetically ordered.
Page# 1 (last added articles shown first)
System ptime availability (11/27/2007)
(...) and 4:30 A.M. on Sunday, that is going to be a lot more tolerable on many systems than if it occurs between 10:00 A. (...)
(...) and 4:30 A.M. on Sunday, that is going to be a lot more tolerable on many systems than if it occurs between 10:00 A. (...)
Definitions for downtime vary from gentle to tough (11/27/2007)
(...) And yet, as we saw in Figure 2.2 and Figure 2.3, they only make up less than half (possibly just a little more than a quarter, depending on whose numbers you like better) of all system outages. (...)
(...) And yet, as we saw in Figure 2.2 and Figure 2.3, they only make up less than half (possibly just a little more than a quarter, depending on whose numbers you like better) of all system outages. (...)
File and Print Server Failures (11/27/2007)
(...) Nary a hand goes up. Then he asks how many leave unprotected network access points like twisted-pair wall jacks in open offices, and you see the tentative hands raised. Access to the network is valuable and has to be protected while still allowing user activity to proceed without onerous overhead. (...)
(...) Nary a hand goes up. Then he asks how many leave unprotected network access points like twisted-pair wall jacks in open offices, and you see the tentative hands raised. Access to the network is valuable and has to be protected while still allowing user activity to proceed without onerous overhead. (...)
Web and Application Server Failures (11/27/2007)
(...) A failure in any of these components appears to be a web site failure. Sitting in front of the web server, load-balancing hardware and software may be used to distribute requests over multiple, identical web servers, and on the client side a proxy cache server sits between a client and server and caches commonly accessed pages so that requests don’t have to go outside of the client’s network. Again, these systems can fail, making it appear that the web server has gone away. (...)
(...) A failure in any of these components appears to be a web site failure. Sitting in front of the web server, load-balancing hardware and software may be used to distribute requests over multiple, identical web servers, and on the client side a proxy cache server sits between a client and server and caches commonly accessed pages so that requests don’t have to go outside of the client’s network. Again, these systems can fail, making it appear that the web server has gone away. (...)
Your system fails because the operating system panics (11/27/2007)
(...) Fixing one failure may not restore the system to its original state; if you’ve ever done a regular reboot or preventative maintenance reboot, you’ve aimed to make a system renewable the brute force way. In all of the examples and scenarios we describe, we are aiming to make systems renewable. Repairing a failed component, whether hardware or software, shouldn’t affect the expected time before the next failure. (...)
(...) Fixing one failure may not restore the system to its original state; if you’ve ever done a regular reboot or preventative maintenance reboot, you’ve aimed to make a system renewable the brute force way. In all of the examples and scenarios we describe, we are aiming to make systems renewable. Repairing a failed component, whether hardware or software, shouldn’t affect the expected time before the next failure. (...)
Direct and Indirect Costs of Downtime (11/27/2007)
(...) Not taken into account is the overtime required to make up for the lost time to ensure that delivery deadlines do not slip. If your developers are consultants, or other hourly employees, then at time-and-a-half, the overtime costs could exceed an additional $600,000. These figures do not take into account factors such as fatigue from working all that overtime or the impact on morale. (...)
(...) Not taken into account is the overtime required to make up for the lost time to ensure that delivery deadlines do not slip. If your developers are consultants, or other hourly employees, then at time-and-a-half, the overtime costs could exceed an additional $600,000. These figures do not take into account factors such as fatigue from working all that overtime or the impact on morale. (...)
COST OF DOWNTIME IS NOT A CONSTANT (11/27/2007)
(...) Depending on the nature of your business, an outage at 1:00 A.M. may cost less than an outage at 1:00 P. (...)
(...) Depending on the nature of your business, an outage at 1:00 A.M. may cost less than an outage at 1:00 P. (...)
The Politics of Availability (11/27/2007)
(...) Other ways to find information about a company include reading through press releases, looking for published interviews with executives, and surfing the Web for financial statements that companies are legally obligated to generate. In the United States, these include the 10-K and 10-Q forms, which are available on the Web. It is always good if you can demonstrate how your ideas can add value to popular internal projects. (...)
(...) Other ways to find information about a company include reading through press releases, looking for published interviews with executives, and surfing the Web for financial statements that companies are legally obligated to generate. In the United States, these include the 10-K and 10-Q forms, which are available on the Web. It is always good if you can demonstrate how your ideas can add value to popular internal projects. (...)
Rational case that explains in nontechnical terms (11/27/2007)
(...) Maybe you can also identify some end users who share your concerns and invite them to join the fight. If your organization is large enough to have multiple facilities, contact peers in other facilities and see if you can find allies there. If you can demonstrate to management that your concerns are shared in different parts of the organization, your case will be much stronger. (...)
(...) Maybe you can also identify some end users who share your concerns and invite them to join the fight. If your organization is large enough to have multiple facilities, contact peers in other facilities and see if you can find allies there. If you can demonstrate to management that your concerns are shared in different parts of the organization, your case will be much stronger. (...)
20 Key High Availability Design Principles 1 (11/27/2007)
(...) There is no question that implementing a protective measure will cost money; the key is to balance that against the ROI. That model is not perfect because it requires making predictions, but educated guesses will get you figures that are close to reality. Over time, you can revisit the figures and improve them for the future. (...)
(...) There is no question that implementing a protective measure will cost money; the key is to balance that against the ROI. That model is not perfect because it requires making predictions, but educated guesses will get you figures that are close to reality. Over time, you can revisit the figures and improve them for the future. (...)
Consolidate Your Servers (11/27/2007)
(...) ” A new trend is emerging, though, that may render this particular principle moot in a few years. Vendors are linking together hundreds or even thousands of very small systems called blades, and developing pseudo-backplanes and shared networks to connect them together, enabling these blade computers to act as a massive cluster. The biggest obstacle so far is administration; few mainstream tools allow easy administration of hundreds of systems, even ones that share applications and operating systems. (...)
(...) ” A new trend is emerging, though, that may render this particular principle moot in a few years. Vendors are linking together hundreds or even thousands of very small systems called blades, and developing pseudo-backplanes and shared networks to connect them together, enabling these blade computers to act as a massive cluster. The biggest obstacle so far is administration; few mainstream tools allow easy administration of hundreds of systems, even ones that share applications and operating systems. (...)
Documentation provides audit trails to work that has been completed (11/27/2007)
(...) When you look back at your own two- or three-year-old work (system or network design or programs, for example), it can be almost impossible to remember why you did something a particular way, and not another way, despite having excellent reasons at the time. Write comments in your code. Write manuals, even if they are just a couple of pages long. (...)
(...) When you look back at your own two- or three-year-old work (system or network design or programs, for example), it can be almost impossible to remember why you did something a particular way, and not another way, despite having excellent reasons at the time. Write comments in your code. Write manuals, even if they are just a couple of pages long. (...)
Keep your production and development environments separate (11/27/2007)
(...) When considering the results of tests, always remember what was being tested. A common mistake that is made in testing is the assumption that if the test didn’t go well, it was the people who messed up. People are people; if the test goes badly, then it is the test that has failed and that must be changed. (...)
(...) When considering the results of tests, always remember what was being tested. A common mistake that is made in testing is the assumption that if the test didn’t go well, it was the people who messed up. People are people; if the test goes badly, then it is the test that has failed and that must be changed. (...)
Two relational database management systems (11/27/2007)
(...) A small company like Joe’s is unlikely to have any of those things. Established support structures make it easier to get help from many different sources. You can find users with whom you can discuss various implementation options, performance optimization, problems you may have encountered, and all sorts of other interesting issues, real and imagined. (...)
(...) A small company like Joe’s is unlikely to have any of those things. Established support structures make it easier to get help from many different sources. You can find users with whom you can discuss various implementation options, performance optimization, problems you may have encountered, and all sorts of other interesting issues, real and imagined. (...)
User documentation is often a good starting point (11/27/2007)
(...) usenix.org) offer consistently excellent training and support services for Unix, Linux, and Windows administrators, on a variety of general and very specific topics. If you are a significant user of a particular vendor’s products, see whether they have user conferences; they represent an outstanding opportunity to meet other people who use similar products and who may have run into similar problems. (...)
(...) usenix.org) offer consistently excellent training and support services for Unix, Linux, and Windows administrators, on a variety of general and very specific topics. If you are a significant user of a particular vendor’s products, see whether they have user conferences; they represent an outstanding opportunity to meet other people who use similar products and who may have run into similar problems. (...)
Incremental Backups of Databases (11/27/2007)
(...) The bottom line on backup windows is that they are getting smaller and smaller, approaching zero. In many shops, they already are zero; backups cannot cause any service interruption at all. Fortunately, even tiny backup windows are no excuse to give backups short shrift. (...)
(...) The bottom line on backup windows is that they are getting smaller and smaller, approaching zero. In many shops, they already are zero; backups cannot cause any service interruption at all. Fortunately, even tiny backup windows are no excuse to give backups short shrift. (...)
Hierarchical Storage Management (11/27/2007)
(...) Stub files are usually about a couple of kilobytes in size. Once a file is migrated, a user need only access the old file in the usual manner, and the system will either locate and mount the appropriate tape or place an operator request for a particular tape to be mounted. Once accessed, the file is returned to the local disk, and the clock on it starts again. (...)
(...) Stub files are usually about a couple of kilobytes in size. Once a file is migrated, a user need only access the old file in the usual manner, and the system will either locate and mount the appropriate tape or place an operator request for a particular tape to be mounted. Once accessed, the file is returned to the local disk, and the clock on it starts again. (...)
Enter page# 1 (last added articles shown first)