We have a cpanel server with a list of accounts running as www.site1.com, www.site2.com etc. If a failure occurs to this primary server then it will take some time to recover and /or restore backups and make our sites work.
As a part of ensuring availability we are planning to install one more cpanel server(as a backup server) , host the same code and database as that of the accounts in primary server. The code will be duplicated and possibly updated with rsync to keep in sync with the primary server. The databses will be replicated from the primary server to the backup server. The objective of this strategy is straigh forward - when a failure occurs, we just need to switch our dns to point to this backup server so that our client users will not suffer any outage
I would like to here about this strategy - any improvisations/critisims welcome
I would also like to here about easily copying the application code , rsync with the backup , create mysql replication etc from WHM/Cpanel
I know that I can copy accounts from the primary server to the backup server from WHM itself - including databse.
As a part of ensuring availability we are planning to install one more cpanel server(as a backup server) , host the same code and database as that of the accounts in primary server. The code will be duplicated and possibly updated with rsync to keep in sync with the primary server. The databses will be replicated from the primary server to the backup server. The objective of this strategy is straigh forward - when a failure occurs, we just need to switch our dns to point to this backup server so that our client users will not suffer any outage
I would like to here about this strategy - any improvisations/critisims welcome
I would also like to here about easily copying the application code , rsync with the backup , create mysql replication etc from WHM/Cpanel
I know that I can copy accounts from the primary server to the backup server from WHM itself - including databse.