Telephone: 215-822-3244


Home » Case Studies . » Case Study 32: Server Consolidation Problems

Case Study 32: Server Consolidation Problems by Barry Koplowitz


  Cutting Through Opinions
Diagnosing Facts
Providing Resolution

 

Interpath Technology Saves Client Millions of Dollars per Day in Lost Financial Transactions

 

Server consolidation & Virtualization save a great deal of money in total cost of ownership & capital equipment.  However, it seldom goes smoothly.  Server Consolidation & Virtualization can also cost big money in lost productivity - vendor costs - damage to an IT Manager's reputation. 

Co-hosted environments - Virtualization, - Server Consolidation - collapses several different servers into one.   Interpath Technologies recommends a "stitch in time" approach with Single Transaction Analysis for Pre-Production & Parallel Production builds.  Load testing is not enough.  Single transaction analysis - before production deployment - is critical.  Countless applications pass load testing only to fail in production.  Single Transaction Testing will discover problems early & easily.

A large Financial Organization underwent a relatively small server consolidation from an outdated system to a cluster of fast Servers on FiberChannel.  After cut-over, new system began to lose transaction at a very alarming rate.  A very high profile project - an expensive problem - costing millions of dollars per day - in lost financial transaction.  Vendor worked this problem for several days with no improvement. 

Client engaged Interpath Technologies Corporation to perform an Enterprise Transaction Analysis. 

 

We designed a systematic approach - we examined all possible pathways - not just those designed by Vendor or those that were expected.  It isn’t an inspired process - just a thorough one.  We discovered - Oracle based traffic from lost transaction - which should have been exclusively in FiberChannel - on a 100Mbs Half Duplex copper segment!  Data had been falling into "bit bucket."  Once problem was understood, they reconfigured network interfaces - no further transaction were dropped.

 

For more information on this case study Click Here.

This article was published on Sunday 13 May, 2007.

Back to main topic: Case-Studies
Case Study 47: Layer 2 loss shown by Layer 4 errors
Case Study 62: Location, Location & Location
Clients--Applications--Services--Devices
Medical

Newsletter
Signup for our Newsletter:

Search

Search Text

Troubleshooting Info:
New Articles (0)
Application & NetAnalysis (13)
Case Studies . (5)
INTERPATHTECH MEDIA
NetAnalysis Myth Series (6)
Podcasts (2)
Team Building (12)
RSS News Feed
RSS

Information
Contact Us

Copyright © 1999-2009 Interpath Technologies Corporation