« May 2005 | Main | July 2005 »

June 18, 2005

The Business Cost of Downtime (by Bob Williamson)

MetaGroup report published last year argues that businesses need to look closely at the cost of application downtime and should also look beyond HA solutions as simply being insurance policies against unplanned outages.  Amen.

We've been educating our prospects and customers for some time that the use of failover clustering and data replication products is more about management than it is about protection.  Sure, you get a safeguard against all of the things that go bump in the night, but you also gain the ability to reduce/eliminate downtime from maintenance windows, to implement more cost effective backup procedures, to do quicker data restores, to gain more insight into the health of your existing infrastructure. 

If you have an HA solution deployed in your IT shop and you're not using it as a tool to help you proactively manage application availability, you should take a moment to reflect on if you can do more with it.  If you can't, it's probably not the optimal solution.

June 16, 2005

Scrumming Away (by Nella Bishop)

SteelEye’s Engineering Team continues to employ Scrum on a daily basis for each and every development task that we undertake.  If you are unfamiliar with the Agile process known as Scrum, two good first stops to check out are www.agilealliance.com and www.controlchaos.com.   If you are interested in increasing your team’s flexibility and productivity, then you should consider implementing the Scrum process for your team.

A new and somewhat controversial paper on Scrum’s future discusses parallel pipelining of sprints for more complex projects. Check it out and give me your opinions

June 13, 2005

Linux vs. Windows - Is the Gap Narrowing? (from TechTarget)

Excerpted from the May 24, 2005 "Analyst Views Weekly Report" by Jim Zimmermann, Executive Editor, Analyst Information Products, TechTarget

According to leading analysts, Linux is a legitimate player for corporate servers, but it has yet to make any perceptible impact in the desktop market. In the past, the main reasons for migrating from Windows to Linux servers were to lower the total cost of ownership (TCO) and to improve security. However, recent analyst commentary is questioning this reasoning.

Linux vs. Microsoft Market Statistics
Sageza Group recently reported that market share and revenue for Linux installations continues to rise, stating that Linux has shown "revenue growth and unit growth both above 50 percent, with revenue topping $1 billion for the fifth consecutive quarter - at nearly $1.6 billion for the last quarter alone." Sageza goes on to point out, "While Linux revenue is growing much faster than that of Windows-based servers, the Microsoft product still holds a commanding 4 to 1 revenue edge in 2004 figures."
 

Yankee Group reports that "Linux now accounts for 20 percent of the worldwide installed base of server operating systems and its share of the North American market is approximately 15 percent." However, Info-Tech Research Group reports that "Most mid-sized enterprises are simply not interested in Linux. A tiny 10 percent of mid-sized enterprises plan to evaluate Linux within the next three years and only a portion of these will actually adopt it." Info-Tech claims that the lack of interest in Linux in mid-sized companies is due to the fact that "smaller organizations already have a trained Windows-based support staff, and adding Linux to the mix can add headcount, complexity and create havoc."

What about TCO?
Yankee Group recently released the results of a survey that compared the TCO of Linux and Windows. Its findings should surprise those Microsoft-haters who believe that Windows is a lost cause and that Linux is the future. According to the study, "An overwhelming 88 percent of corporations report that Microsoft's Windows Server 2003 operating system provides performance and reliability that are equal to or better than Linux in comparable usage scenarios." This represented a 12 percent increase over Yankee's 2004 survey results.
 

The survey found that from 2004 to 2005, Linux maintained - but did not expand - its healthy 15 percent market share compared to the 73 percent market share for various versions of Windows servers. This is not to say that Windows servers are the solution for all server needs in a company. Yankee Group believes that Windows and Linux each have their own specific "strengths, weaknesses, opportunities and threats that can affect a corporation's TCO and ROI, positively or negatively." Yankee cautions that "To achieve optimum results and avoid undue deployment problems and expenses, corporations must perform a thorough cost, performance and risk analysis to determine the right technology option."

What about Security?
Microsoft's focus on correcting security concerns seems to be yielding results. The Yankee Group survey found that:

  • "Users rated the security of Linux and Windows servers nearly equal."
  • "Windows servers recover 30 percent faster from security attacks than Linux servers."
  • "Patch management woes lessen for Windows, but are on the rise for Linux."
  • "Microsoft clearly and convincingly corrected its most severe technical customer concerns. It must now maintain that vigilance."
  • Several firms also have pointed out that as Linux servers become more numerous, hackers have begun developing viruses and other threats to Linux. Although the number of Linux hacks is still small, the numbers are rising (Sources: Yankee Group, The Sageza Group).

    Conclusions
    Both Linux and Windows are here to stay. The decision to deploy a Linux or a Windows server should be based on a careful evaluation of both technical and business needs. For smaller companies with in-house Windows skills, moving to Linux or implementing Linux alongside Windows could cause more headaches and staff issues than value. For larger companies with sufficient staff and training budgets, implementing Linux-based servers may prove cost-effective in the long-term.

    June 12, 2005

    Port of LifeKeeper to POWER goes smoother than expected (by Bob Williamson)

    Read about the port of LifeKeeper for Linux to IBM's OpenPower line in a new case study just published here.

    June 10, 2005

    Windows 2003 SP1 modifies File Server behavior to prevent “reflection” attacks (by Dave Krantz)

    Microsoft has modified the use of SMB server Alias names to improve server protection from “reflection” attacks.  Effective with Windows 2003 SP1, the use of server Alias names on the same server where they are defined has been disabled by default.  For more information about this change, refer to Microsoft Knowledge Base article Q281308 and Microsoft article 896861.

    Access to SMB shared files on a file server is usually initiated from other client computers on the network, and access to file shares over the network using a server Alias name is still supported.  However, use of a server Alias name on the local server where it is defined has been disabled by SP1 and attempts to use it locally will generate the following error messages:

    System error 52 has occurred.
    A duplicate name exists on the network.

    If local access to shares on the same server (using an SMB Alias name) is needed, and if the server is not vulnerable to a reflection attack, the original behavior can be restored.  A new DWORD registry value “DisableLoopbackCheck” is required (=1) at the following registry key location:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa
    DWORD Value Name = DisableLoopbackCheck
                 Value Setting = 1

    June 03, 2005

    Windows v5.0 Porting Guide available on www.steeleye.com (by Nella Bishop)

    The Windows v5 product just released has a new Linux/UNIX emulation layer based on Cygwin code.  There is a slight chance that existing scripts which make emulated calls may need to be modified.

    If you have custom recovery kits written prior to v5.0 or have modified any core LifeKeeper scripts for specific custom requirements, you will definitely want to check out the  handy (but brief)  Porting Guide available with LifeKeeper for Windows v5.0.  It is located at http://licensing.steeleye.com/support/docm.php?file=3, with the rest of the LifeKeeper for Windows v5.0 Documentation.  Review the guide and then perform an audit of your custom kits. 

    Call or email our support team if you have any questions or need help in doing your review.

     

    June 02, 2005

    New Windows Product is GA! (by Bob Williamson)

    The Windows team completed final testing on the new version5 product yesterday and today we announced GA.  Yeah! and congratulations to the team who worked very hard to accomplish this major release.  You can read all about the features in the press release at:  http://www.steeleye.com/news/press_releases/060205.html

    Our final test phase always includes placing the Release Candidate bits onto our corporate IT servers to perform what we call "Feature Audit".  No matter how good your test lab emulation procedures are, you just cannot replicate all of the environmental factors of a live production environment.  So, we go into production prior to GA as a final sanity check.  If it's good enough for our customers, it's gotta be good enough for us as well.   Our corporate Exchange server has been running v5 for a couple of weeks and all is well.