A referral.
A critical outage.
The client contacted the Fortis team on another client’s recommendation while their server and hosting were effectively down. The environment was critical to business operations, so getting it running again was the immediate priority.
The initial brief concerned the server’s FcgidMaxProcesses limit. Behind that request was a wider infrastructure problem: multiple applications had been crowded into one underprovisioned virtual machine.
Restore service with a dedicated engineer and an emergency change window. Then assess what needed to change for the longer term.
A dedicated engineer.
A coordinated recovery.
- One point of contact
Provide a dedicated engineer
The client reached the Fortis team through a recommendation from another client during a critical outage. We assigned a dedicated engineer to work directly with them, understand the business impact and take ownership of the technical investigation.
- Diagnose before changing
Identify the issues and assess the action needed
Our engineer worked with the client to identify the issues affecting the server and assess the changes needed to restore service. The original FastCGI process-limit concern was considered within the wider hosting problem, rather than treated as an isolated setting.
- Agree the recovery work
Arrange an emergency change window
We provided an emergency change window for the corrective work. The client was told what the engineer intended to do and why, keeping the recovery coordinated and the next steps clear during a business-critical incident.
- Restore service
Get the server back up and running
The engineer carried out the corrective work and got the server back up and running. The Fortis team stayed in communication throughout, working through the hosting issues until service was restored.
Restore today.
Improve tomorrow.
Once the server was back up and running, we audited the infrastructure. That review informed a proposed service package and an infrastructure change to address the limitations of the existing setup.
The client’s applications had been sharing one underprovisioned VM. We proposed moving them onto their own dedicated virtualised server environment, with separate instances for the applications instead of keeping everything together.
The subsequent migration separated those workloads and provided a better foundation for running them. The change improved performance and the overall security posture of the environment.
Back online.
Better foundations.
Service restored
A dedicated engineer identified the issues, assessed the corrective action and got the server running again within an emergency change window.
A plan beyond the immediate fix
An infrastructure audit informed a proposed service package and a redesign of the hosting environment.
Applications separated
Migration to a dedicated virtualised environment moved the applications out of one shared, underprovisioned VM into separate instances.
Improved performance and security posture
The infrastructure change improved both how the applications ran and the overall security posture of the environment.
The difference
for the client.
“saved the day for us when our server and hosting essentially ceased to work.”
Recovery is the start.
Resilience comes next.
During an outage, the first job is to restore service and keep the client informed. Once the immediate pressure has passed, there is an opportunity to address the underlying infrastructure.
In this case, that meant moving beyond a configuration fix to a dedicated virtualised environment with separated application instances. The client gained a working service and a stronger platform for the business.