Abstract: A software sparing process and apparatus to reduce the likelihood of software failures is provided. Software sparing provides software entities, called spares, which take over and provide similar functionality as the failed system to the clients of the failed entity. They also permit the introduction of new software versions with no loss in service during the switch over period. These spare entities, which may be located on different nodes in a system, communicate using a standard interface protocol. Sparing is done at the software "chunk" level instead of at the hardware box level, which is the common practice, resulting in lower costs and improved reliability. A computer readable storage medium containing a program element to direct a processor of a computer to implement the software sparing process described earlier is also provided.