Solved

DRS question.

Posted on 2016-08-17
14
79 Views
Last Modified: 2016-08-24
We have recently added a new host to our VMware 5.5 cluster.  Currently, we have turned off DRS to make sure no VM being migrated to the new host.  

Besides turning off DRS at the cluster level, is there a way we can prevent any VM from being moved into the new host?  

We want the DRS option to be available only for the previous hosts to load balance each other until the new host is fully in production.  

Thanks.
0
Comment
Question by:nav2567
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 5
  • 4
  • 4
  • +1
14 Comments
 
LVL 10

Accepted Solution

by:
Richardson Porto earned 200 total points
ID: 41759330
You could create a affinity rule to avoid virtual machines to run on the new host. Take a look here for additional details: https://pubs.vmware.com/vsphere-51/index.jsp?topic=%2Fcom.vmware.vsphere.resmgmt.doc%2FGUID-D2E5FBE2-E4BF-48B1-BF02-BF37AE9D5F21.html
0
 
LVL 120

Assisted Solution

by:Andrew Hancock (VMware vExpert / EE MVE^2)
Andrew Hancock (VMware vExpert / EE MVE^2) earned 200 total points
ID: 41759385
Put the Host in maintenance mode will stop any VMs being migrated to it.
0
 

Author Comment

by:nav2567
ID: 41759684
Andrew, if I put the new host in maintenance mode, whatever VMs running in the new host will still be functioning, right?
0
NEW Veeam Agent for Microsoft Windows

Backup and recover physical and cloud-based servers and workstations, as well as endpoint devices that belong to remote users. Avoid downtime and data loss quickly and easily for Windows-based physical or public cloud-based workloads!

 
LVL 120
ID: 41759690
No, they will be moved.

What are you trying to do?

If the host is not fully in production, it should not have been added to the cluster! It should be tested first, and then moved finally into the Cluster for Production.

You will also need to disable HA, because in the event a Host Crashes, VMs will be restarted on the new host.

Also remember DRS is not a load balancer, it moves a VM, if the current host cannot satisfy it's resources it requires e.g. CPU and Memory.

and if you leave DRS ON, and set to MANUAL, no VMs are going to move anywhere, unless you manually do something.
0
 

Author Comment

by:nav2567
ID: 41759693
Sorry that I did not make the question clear.  

We add a new host to a cluster, move a group of VMs into this new host.  We do not want any more VM being moved as a result of DRS.

Besides turning off DRS at the cluster level which impacts the previous hosts in the cluster, is there a better way to do it?

Thanks.
0
 
LVL 120
ID: 41759706
What we do, if you are trying to build confidence in your new host, is we set DRS ON and MANUAL....

So, this will stop any VMs automatically moving around your cluster, and then run the DRS review, manually move VMs using vMotion (a human does this) to satisfy DRS conditions and CPU and Memory pressure - if any exists...

 and we then only move low priority VMs to test this new host, until we are happy all is working well, to set DRS back to AUTOMATIC, Aggressive.

How long you test and build confidence in this new host is based on your Test Plan.
0
 
LVL 10

Expert Comment

by:Richardson Porto
ID: 41759715
Another option, instead of disable DRS, is let it Fully Automated and change the migration threshold to a level different than the level 3 (default). For example, changing the migrating threshold to level 1 (conservative) will only apply recommendations that must be taken to satisfy cluster constraints like affinity rules and host maintenance.
0
 

Author Comment

by:nav2567
ID: 41760942
Thanks, guys.  

I am not familiar.  Would you provide instruction on how to set DRS to different level?  

Thanks.
0
 
LVL 10

Expert Comment

by:Richardson Porto
ID: 41760945
0
 
LVL 120
ID: 41761200
set to manual.
0
 

Author Comment

by:nav2567
ID: 41762312
For of all, thanks for your useful suggestions.

Currently, there are 5 VMs in the new host and DRS is set to off.  

To see the threshold settings, I will have to enable DRS again.  Other VMs will be moved to the new host as it has more resources.  

Is there a way that I can enable DRS but exclude the new host to be involved?

If I enable DRS, set automation level to MANUAL, migration threshold to MEDIUM, I think no migration will occur, right?  What is the different between doing this and disable DRS?
0
 
LVL 10

Expert Comment

by:Richardson Porto
ID: 41762384
If I enable DRS, set automation level to MANUAL, migration threshold to MEDIUM, I think no migration will occur, right?
Yes, only recommendations will be generated but no automatic migration will occur.

What is the different between doing this and disable DRS?
The difference is that on DRS enable in manual mode, the DRS will evaluate the resource utilization of your cluster and made migration recommendation. With DRS disable, no evaluation or recommendation will be generated.

Again, I believe that the best scenario for you is create Affinity Rules, that will allow DRS run in Fully Automated mode and avoid unwanted virtual machines be migrated to the new host.
0
 
LVL 120
ID: 41762391
Disable DRS and it does not function.
0
 
LVL 1

Assisted Solution

by:patron
patron earned 100 total points
ID: 41764123
if u want host to be balanced except this new host so get this host out  from cluster till it is ready to move in production
or keep in maintenance mode till u get it ready for balanced cluster
0

Featured Post

Manage your data center from practically anywhere

The KN8164V features HD resolution of 1920 x 1200, FIPS 140-2 with level 1 security standards and virtual media transmissions at twice the speed. Built for reliability, the KN series provides local console and remote over IP access, ensuring 24/7 availability to all servers.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

In this article, I will show you HOW TO: Create your first Windows Virtual Machine on a VMware vSphere Hypervisor 6.5 (ESXi 6.5) Host Server, the Windows OS we will install is Windows Server 2016.
When rebooting a vCenters 6.0 and try to connect using vSphere Client we get this issue "Invalid URL: The hostname could not parsed." When we get this error we need to do some changes in the vCenter advanced settings to fix the issue.
Teach the user how to convert virtaul disk file formats and how to rename virtual machine files on datastores. Open vSphere Web Client: Review VM disk settings: Migrate VM to new datastore with a thick provisioned (lazy zeroed) disk format: Rename a…
Teach the user how to use configure the vCenter Server storage filters Open vSphere Web Client:  Navigate to vCenter Server Advanced Settings: Add the four vCenter Server storage filters: Review the advanced settings: Modify the values of the four v…

738 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question