Quantcast
Channel: VMware Communities: Message List
Viewing all articles
Browse latest Browse all 49146

Re: vMotion scenario

$
0
0

Hi,

Thanks for replying.

 

Ok the term "Master" and "Slave" are master as running production VM and slave as backup vm for vMotion. So when running vm dies or lost connection, it gets automatically migrated to that "slave" vm which is not in production and using very little bit of resource. So it is just active-standby situation to clarify.

 

The total resource pool we have is 512GB of ram currently and master and slave are allocated 256GB each. Master VM (production vm) is using almost every ram resource allocated and slave VM is using 50GB / 256 GB, so slave has capacity of 200GB of ram. So we are planning to add 1 more DB server and share that remaining 200GB of ram from slave VM.

 

But the problem is that when that newly added DB server (probably will be allocated 128GB ram), vm, is down, will it be able to migrated into the slave VM.

Since I have not experienced such environment, I am searching the similar situation but couldn't find it.

 

Will this plan be able to pull off?

 

Thanks,


Viewing all articles
Browse latest Browse all 49146

Trending Articles