It is very common to find organizations that have dedicated physical infrastructure for each application/service, namely servers. On the other hand, due to the cost of physical servers, many organizations choose to concentrate all applications and services on a single physical server.
Despite the existence of products that supposedly reduce downtime associated with failure, they usually have several constraints, namely implementation complexity, limited support for different operating systems (OS) and associated licensing costs, which tend to be significant. This implies that in the occurrence of a physical server failure, there will be a breakdown in the availability of associated resources and the consequent impact on business.
In extreme cases, the replacement of the system's good functioning will be physically conditioned as to the availability of a new server, replacement of operating system and applications and restoration of the last available backup.
The time involved in this process of system replacement may take from days to weeks, compromising the organization in a perspective of cost and image to its customers and partners.
Another common problem has to do with infrastructure maintenance, which will have to be carefully planned, namely regarding the associated downtime, due to the lack of alternative application processing mobility, i.e. the inexistence of service during the intervention period.
Interventions should be carried out in a calculated and planned manner within a given time window, avoiding as far as possible the impact on the working period. Such interventions should also include careful contingency plans that allow for the normal replacement of the service in the event of slippage or problems during the intervention.