Hi guys,
my customer asks me for providing a solution to allow him to apply planned maintenance to the Sql Server and Application server with minor impact on production (reducing downtime).
It means that when 1 or all machine/s is/are under maintenance/update another copy of the same server/s must be connected to provide service (the <slave> machines must be identical to the master).
Currently, I am thinking to propose a solution based on VM but I need your help to better define it.
Scenario:
just for comprehend my problem: assume that currently the system is represented by 3 physical machines (2 application servers and 1 is the SQL Server 2008 R2); the database is stored in a external storage.
I am thinking over some solutions (depending mainly on the cost).
Requirements:
1) When a master VM is under maintenance, the slave VM (in the second machine) take ownership unless the <master> VM is updated. Then, the <slave> must be update as for the <master> VM.
2) Version of VmWare may be important: is not clear if my clients is available to purchase new vmWare software
1) Solution 1:
1 physical machine (production machine) hosting the 3 VMs (2 app servers + SQL Server): this represent the production system
1 physical machine (slave: service) hosting 1 or more VMs when 1 or more VM from the Production Host is /are under maintenance. It means that when 1 VM machine is under maintenance is not provide service.
My question is:
How can I reach this goal:
a) by using vMotion (but is not clear: the VM share the same files? or each VM is stored locally)
or
b) by Using Backup & Recovery
2) Solution 2
3 Phisical machines (2 bapp servers + 1 SQL server)
1 Phisical MAchine hosting vMWare Esxi: the 3 phisical machines are converted in Virtual machines and loaded in Esxi and run when the <master> machine is down for maintenance.
Any help/suggestion will be very appreciated.
Many thanks