Drogas La Rebaja — Forty minutes: continuity on the replica
Client: Drogas La Rebaja — Pharmacy retail
The challenge
A cumulative update left the primary database engine down in the middle of business operations.
The solution
Operations failed over to the replica server and service was back in forty minutes. The affected environment was rebuilt that same night, outside business hours.
What makes it possible to resume operations so quickly?
When the primary database engine stops in the middle of business operations, the most valuable thing is having an alternative ready to go into service. In this case, that alternative was the replica server, to which operations were failed over so that service could return in forty minutes.
Restoring service is only part of the job. The affected environment was rebuilt that same night, outside business hours, so the pharmacy could keep serving its customers while the full recovery was carried out.
This experience shows the importance of an architecture that does not depend on a single point. With SQL Server and Microsoft Azure as its foundation, business continuity is backed by a replica that can take over operations when the primary server stops.
Technologies used
- Microsoft SQL Server
- Microsoft Azure
Results
- 40 min Service restored — By failing over to the replica
Frequently asked questions
What happened to the primary database engine?
How was service restored so quickly?
What happened to the affected environment after the failover?
What technologies were used in this solution?
Keep reading
Want similar results?
Let's talk. We design solutions tailored to your industry.
Book a consultation