I want to buy server, but need it with a proper disaster recovery plan for it? Print

If you are looking for a disaster recovery plan where even if the hardware of one server is failed with minimal downtime, you can have a secondary server take place, then here is the plan:

What hardware or software setup is required for it?
1x Load balancer
2x Cloud servers (on high availability infrastructure) with identical case configuration
1x Remote backup addon on primary server (For restore of data in case of primary server failure).

1. When ordered 2 cloud servers we setup them and keep them ready with the same software and runtime environment, so your application is actually hosted on the server and another server is only the secondary server, that is up and running for emergency take over for the application.

2. Load balancer initially we setup it with primary server configured, however in case of failure of primary hardware, the load balancer back-end IP can be updated to secondary server to make that online immediately without downtime for DNS propagation or IP changes.

3. Remote backup addon will take backup of primary server on an hourly basis of your database and daily basis of your files / folders to have the best and latest restorable points available.

What if the primary server fails?
Step 1) We can add the secondary server to load balancer IP, so that the application hosted on your domain name or sub domain name which points to the load balancer can now point to the secondary server.
Step 2) Our system admin team can restore your files/folders + database to a new server using our backup tools with the last available restore points to make your website live without any additional dns changes etc.

Ideally, in such a plan (except any exceptional case), your website can get live again in a matter of few minutes / hrs time, even in case of a hardware failure.

What are the advantages of this plan?
1. There is no need to wait for a new server to be setup (in case of primary server's hardware failure), as secondary server is always with us side by side.
2. There is no need to install any software etc on a new server, as the secondary server already has all the same runtime setup as the primary server.
3. There is no wait time, as the restore task can be started as soon as downtime on the primary server is found downtime in monitoring.
4. There is no need to wait for dns propagation, as your website or subdomain works with load balancer IP A record, thus the back-end of load balancer IP is updated to secondary one, so no need to have any dns changes or wait time for dns propagation required.

Any technical person can evaluate these 4 points mentioned above, as in case of a disaster recovery, these are the primary elements which take time to make the application live from the new server, so the new server. Therefore, this plan is to make sure to have an optimal and fastest way to deal with hardware failure situations.

Note - It is planned as per ideal situation and case studies encountered in experience by us, but when dealing with real-time technical issues, sometimes new challenges or exceptional cases can be there. However, that also can't discard the importance of the planning mentioned above in any sense.