How to organize software architecture of servers?

Question

Virtualization

Hello.
How to organize server software architecture for rapid deployment.
there are 2 servers one main, the second reserve. The following solution was assembled in my head

SRV_0:
VM_0: DHCP + NTP
VM_1: VM_0 clone

BM_2: ownCloud
VM_3: VM_2 clone

BM_4: Postgresql DB (replication to srv_0 BM_5 and srv_1 VM_4 and srv_1 BM_5 )
BM_5: BM_4 clone

BM_6: Docvision
BM_6: BM_6 clone

BM_8: Docvision
BM_9: BM_8 clone VM_10

: MSQL DB (replicated to srv_1 VM_10)
BM_11: VM_9 clone

SRV_1:
VM_0: DHCP + NTP
VM_1: VM_0 clone

BM_2: ownCloud
VM_3: VM_2 clone

BM_4: Postgresql DB
BM_5: BM_4 clone

BM_6: Docvision
BM_7: BM_6 clone

BM_8: Docvision
BM_9: BM_8 clone

VM_10: DB MSQL
BM_11: VM_9

clone If there are problems with the server, I transfer to a backup. Does all this nonsense have a right to exist?
Where to read how VM architecture is organized?

Answer 1

The description is similar to a cluster of servers that run on a cluster of virtual machines. Why not? The scheme seems to be working, a lot of money is needed, but it seems to be as you described, everything is in automatic mode and everything will continue to work if any of the servers falls