<rss version="2.0">
<channel>
<title> Servers articles</title>
<description>Free information about Servers</description>
<link>http://www.web-articles.info/e/s/s/Servers/</link>
<language>en-us</language>
<copyright>Web-articles.info 2007</copyright>
<managingEditor>adv@e-articles.info</managingEditor>
<webMaster>adv@e-articles.info</webMaster>
     <item>
        <title> System ptime availability</title>
        <description> (...) &amp;rdquo; But the tune usually
  changes when the project leader finds out how much 100 percent availability
  would cost. Then the discussion becomes a matter of money, and more of a
  negotiation process.
  As you can see in Table 2. (...) by Ben Smeider</description>
        <guid>http://www.web-articles.info/e/a/title/System-ptime-availability/</guid>
		<link>http://www.web-articles.info/e/a/title/System-ptime-availability/</link>
        <pubDate> Tue, 27 Nov 2007 00:00:00 GMT</pubDate>
     </item>  
     <item>
        <title> Definitions for downtime vary from gentle to tough</title>
        <description> (...) 
  We prefer a very strict definition for downtime: If a user cannot get her job
  done on time, the system is down. A computer system is provided to its users
  for one purpose: to allow them to complete their work in an efficient and
  timely way. When circumstances prevent a user from doing this work, regardless
  of the reason, the system is down. (...) by Ben Smeider</description>
        <guid>http://www.web-articles.info/e/a/title/Definitions-for-downtime-vary-from-gentle-to-tough/</guid>
		<link>http://www.web-articles.info/e/a/title/Definitions-for-downtime-vary-from-gentle-to-tough/</link>
        <pubDate> Tue, 27 Nov 2007 00:00:00 GMT</pubDate>
     </item>  
     <item>
        <title> File and Print Server Failures</title>
        <description> (...) 
  Networks are also affected by configuration problems. Incorrect routing
  information, duplicate hostnames or IP addresses, and machines that misinterpret
  broadcast addresses can lead to misdirected packets. You&amp;rsquo;ll also have to
  deal with redundancy in network connections, as you may have several
  routers connecting networks at multiple points. (...) by Ben Smeider</description>
        <guid>http://www.web-articles.info/e/a/title/File-and-Print-Server-Failures/</guid>
		<link>http://www.web-articles.info/e/a/title/File-and-Print-Server-Failures/</link>
        <pubDate> Tue, 27 Nov 2007 00:00:00 GMT</pubDate>
     </item>  
     <item>
        <title> Web and Application Server Failures</title>
        <description> (...)  However, there are many
  other places within the web server environment where things might go awry.
  There are many new places for bugs to crop up, including in the Common
  Gateway Interface (CGI), Perl, Java, JavaScript, or Active Server Page (ASP)
  code that manages the web page. If some set of circumstances causes a CGI
  program to get stuck in a loop, the web page it manages will never display,
  most likely causing the user to try another site. (...) by Ben Smeider</description>
        <guid>http://www.web-articles.info/e/a/title/Web-and-Application-Server-Failures/</guid>
		<link>http://www.web-articles.info/e/a/title/Web-and-Application-Server-Failures/</link>
        <pubDate> Tue, 27 Nov 2007 00:00:00 GMT</pubDate>
     </item>  
     <item>
        <title> Your system fails because the operating system panics</title>
        <description> (...)  What&amp;rsquo;s the probability of another failure due to an operating
  system panic? In all likelihood, it&amp;rsquo;s exactly the same as it was before the reboot.
  There are many cases, however, in which repairing a system changes the MTBF characteristics of the system, increasing the probability of another failure
  in the near-term future.
  When you replace a punctured tire on your car with the &amp;ldquo;doughnut&amp;rdquo; spare
  tire, the MTBF for tire problems isn&amp;rsquo;t the same as when you were running on
  four original tires; the doughnut has speed and distance restrictions on it that
  make it less reliable than a new tire. (...) by Ben Smeider</description>
        <guid>http://www.web-articles.info/e/a/title/Your-system-fails-because-the-operating-system-panics/</guid>
		<link>http://www.web-articles.info/e/a/title/Your-system-fails-because-the-operating-system-panics/</link>
        <pubDate> Tue, 27 Nov 2007 00:00:00 GMT</pubDate>
     </item>  
     <item>
        <title> Direct and Indirect Costs of Downtime</title>
        <description> (...) 

Direct Costs of Downtime

  The most obvious cost of downtime is probably not the most expensive one:
  lost user productivity. The actual cost of that downtime is dependent upon
  what work your users perform on the affected systems.
  If your users are developers, then perhaps the cost seems to be nothing more
  than the time and carrying cost for the idled developers. (...) by Ben Smeider</description>
        <guid>http://www.web-articles.info/e/a/title/Direct-and-Indirect-Costs-of-Downtime/</guid>
		<link>http://www.web-articles.info/e/a/title/Direct-and-Indirect-Costs-of-Downtime/</link>
        <pubDate> Tue, 27 Nov 2007 00:00:00 GMT</pubDate>
     </item>  
     <item>
        <title> COST OF DOWNTIME IS NOT A CONSTANT</title>
        <description> (...)  If the site
  suffers a brief outage (a 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 but the most disloyal users will simply hit their browser&amp;rsquo;s reload
  button and try again. A 30-minute outage will cause some customers to take
  their business to a competitor&amp;rsquo;s site; others will be patient and keep trying. (...) by Ben Smeider</description>
        <guid>http://www.web-articles.info/e/a/title/COST-OF-DOWNTIME-IS-NOT-A-CONSTANT/</guid>
		<link>http://www.web-articles.info/e/a/title/COST-OF-DOWNTIME-IS-NOT-A-CONSTANT/</link>
        <pubDate> Tue, 27 Nov 2007 00:00:00 GMT</pubDate>
     </item>  
     <item>
        <title> The Politics of Availability</title>
        <description> (...)  Fundamentally, this means
  that you achieve your goals by helping (or if you aren&amp;rsquo;t particularly scrupulous,
  appearing to help) others around you achieve their goals, so that they
then help you achieve yours.
Start Inside
  Probably the best way 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, you must understand what their goals are. (...) by Ben Smeider</description>
        <guid>http://www.web-articles.info/e/a/title/The-Politics-of-Availability/</guid>
		<link>http://www.web-articles.info/e/a/title/The-Politics-of-Availability/</link>
        <pubDate> Tue, 27 Nov 2007 00:00:00 GMT</pubDate>
     </item>  
     <item>
        <title> Rational case that explains in nontechnical terms</title>
        <description> (...) 

  Find Allies

  Ask around your organization. Look for friends and colleagues who share
  your concerns. Maybe you&amp;rsquo;ll find someone who has tried to convince management
  of something in the past. (...) by Ben Smeider</description>
        <guid>http://www.web-articles.info/e/a/title/Rational-case-that-explains-in-nontechnical-terms/</guid>
		<link>http://www.web-articles.info/e/a/title/Rational-case-that-explains-in-nontechnical-terms/</link>
        <pubDate> Tue, 27 Nov 2007 00:00:00 GMT</pubDate>
     </item>  
     <item>
        <title> 20 Key High Availability Design Principles 1</title>
        <description> (...) 
   The decision to implement availability is a
  business decision. It comes down to dollars and cents. If you look at the business
  decision to implement availability purely as &amp;ldquo;how much will it cost me,&amp;rdquo;
  then you are missing half of the equation, and no solution will appear adequate. (...) by Ben Smeider</description>
        <guid>http://www.web-articles.info/e/a/title/20-Key-High-Availability-Design-Principles-1/</guid>
		<link>http://www.web-articles.info/e/a/title/20-Key-High-Availability-Design-Principles-1/</link>
        <pubDate> Tue, 27 Nov 2007 00:00:00 GMT</pubDate>
     </item>  
     <item>
        <title> Consolidate Your Servers</title>
        <description> (...)  Instead of having many small singlepurpose
  machines or lots of machines running a single instance of a database,
  companies are rolling them together and putting all the relevant applications
  onto one or more larger servers with a capacity greater than all of the replaced
  servers. This setup can significantly reduce the complexity of your computing
  environment. It leads to fewer machines that require backups; fewer machines
  that require reboots; and overall, fewer things that can fail. (...) by Ben Smeider</description>
        <guid>http://www.web-articles.info/e/a/title/Consolidate-Your-Servers/</guid>
		<link>http://www.web-articles.info/e/a/title/Consolidate-Your-Servers/</link>
        <pubDate> Tue, 27 Nov 2007 00:00:00 GMT</pubDate>
     </item>  
     <item>
        <title> Documentation provides audit trails to work that has been completed</title>
        <description> (...)  It can provide the system administrator
  and his management with accomplishment records. (These can be very handy
  at personnel review time.) Good documentation can also help with problem
solving. (...) by Ben Smeider</description>
        <guid>http://www.web-articles.info/e/a/title/Documentation-provides-audit-trails-to-work-that-has-been-completed/</guid>
		<link>http://www.web-articles.info/e/a/title/Documentation-provides-audit-trails-to-work-that-has-been-completed/</link>
        <pubDate> Tue, 27 Nov 2007 00:00:00 GMT</pubDate>
     </item>  
     <item>
        <title> Keep your production and development environments separate</title>
        <description> (...)  Ideally,
  testing should take place in a production-like environment, with as similar an
  environment to the operational one as possible, and with as much of the same
  hardware, networks, and applications as possible. Even better, the same users
  should perform the tests. The tests need to be performed with the same production
  network configuration and loads, and with the same user inputs and
  application sets. (...) by Ben Smeider</description>
        <guid>http://www.web-articles.info/e/a/title/Keep-your-production-and-development-environments-separate/</guid>
		<link>http://www.web-articles.info/e/a/title/Keep-your-production-and-development-environments-separate/</link>
        <pubDate> Tue, 27 Nov 2007 00:00:00 GMT</pubDate>
     </item>  
     <item>
        <title> Two relational database management systems</title>
        <description> (...)  (We are not endorsing Oracle; the same rules
  would apply to any mature software product. As far as we know, Joe has not
  yet released a database.) Joe&amp;rsquo;s product has a couple of features that make it a
  little easier to use, and it comes in a lot cheaper than Oracle does. (...) by Ben Smeider</description>
        <guid>http://www.web-articles.info/e/a/title/Two-relational-database-management-systems/</guid>
		<link>http://www.web-articles.info/e/a/title/Two-relational-database-management-systems/</link>
        <pubDate> Tue, 27 Nov 2007 00:00:00 GMT</pubDate>
     </item>  
     <item>
        <title> User documentation is often a good starting point</title>
        <description> (...) 
  Arrange for on-site consultation from vendor resources or independent contractors,
  and be sure a transfer-of-information or technical exchange is part of
  the planned work. If vendors offer training classes on a product, make sure the
  right people attend them so that you learn the pitfalls and issues before you
  start implementation.
  Read articles (we know an excellent one on high availability) and magazines,
  both on paper and online. (...) by Ben Smeider</description>
        <guid>http://www.web-articles.info/e/a/title/User-documentation-is-often-a-good-starting-point/</guid>
		<link>http://www.web-articles.info/e/a/title/User-documentation-is-often-a-good-starting-point/</link>
        <pubDate> Tue, 27 Nov 2007 00:00:00 GMT</pubDate>
     </item>  
     <item>
        <title> Incremental Backups of Databases</title>
        <description> (...)  Once they are backed up, pointers
  and indices must be maintained so that the blocks can be put back into the
  database upon restore.
  Some solutions require a complete scan of the database for changed blocks.
  At least one solution (VERITAS NetBackup with the VERITAS File System,
  only available on Unix) keeps track of the blocks that have changed and does
  not need to do a full database scan in order to perform an incremental backup. (...) by Ben Smeider</description>
        <guid>http://www.web-articles.info/e/a/title/Incremental-Backups-of-Databases/</guid>
		<link>http://www.web-articles.info/e/a/title/Incremental-Backups-of-Databases/</link>
        <pubDate> Tue, 27 Nov 2007 00:00:00 GMT</pubDate>
     </item>  
     <item>
        <title> Hierarchical Storage Management</title>
        <description> (...) 
  Go back further if your systems have been around that long.
Consider this: Those files that haven&amp;rsquo;t been touched in 6 months or more
  still take up valuable time, space, and bandwidth during your backups and
  once again during restores. Apart from simply deleting them, what can you do
  to recapture the resources that these files consume?
  Welcome to the world of Hierarchical Storage Management (HSM). (...) by Ben Smeider</description>
        <guid>http://www.web-articles.info/e/a/title/Hierarchical-Storage-Management/</guid>
		<link>http://www.web-articles.info/e/a/title/Hierarchical-Storage-Management/</link>
        <pubDate> Tue, 27 Nov 2007 00:00:00 GMT</pubDate>
     </item>  
  
</channel>
</rss>
