Comments on: (Presentation) Design tips for VMware vSphere 4 http://www.gabesvirtualworld.com/presentation-design-tips-for-vmware-vsphere-4/ Your P.I. on virtualization Tue, 24 Aug 2010 15:28:38 -0700 http://wordpress.org/?v=2.9.2 hourly 1 By: VMUG Aftermath » Yellow Bricks http://www.gabesvirtualworld.com/presentation-design-tips-for-vmware-vsphere-4/comment-page-1/#comment-502 VMUG Aftermath » Yellow Bricks Mon, 14 Dec 2009 07:32:53 +0000 http://www.gabesvirtualworld.com/?p=669#comment-502 [...] presentation consisted of many best practices and recommendations. The presentation can be found here and is most definitely a must [...] [...] presentation consisted of many best practices and recommendations. The presentation can be found here and is most definitely a must [...]

]]> By: Duncan http://www.gabesvirtualworld.com/presentation-design-tips-for-vmware-vsphere-4/comment-page-1/#comment-729 Duncan Sun, 01 Nov 2009 14:06:26 +0000 http://www.gabesvirtualworld.com/?p=669#comment-729 It does not matter Tom as long as it is documented indeed. I would personally prefer the approach that makes the most sense which is the first and second host in a cluster. It does not matter Tom as long as it is documented indeed. I would personally prefer the approach that makes the most sense which is the first and second host in a cluster.

]]> By: Duncan http://www.gabesvirtualworld.com/presentation-design-tips-for-vmware-vsphere-4/comment-page-1/#comment-731 Duncan Sun, 01 Nov 2009 14:04:43 +0000 http://www.gabesvirtualworld.com/?p=669#comment-731 maybe you can also post the context as I hardly see any decisions based business requirements? maybe you can also post the context as I hardly see any decisions based business requirements?

]]> By: Top 5 Planet V12n blog posts week 44 – VMvisor http://www.gabesvirtualworld.com/presentation-design-tips-for-vmware-vsphere-4/comment-page-1/#comment-460 Top 5 Planet V12n blog posts week 44 – VMvisor Sun, 01 Nov 2009 11:59:25 +0000 http://www.gabesvirtualworld.com/?p=669#comment-460 [...] van Zanten – Design tips for VMware vSphere 4Recently at the Belgium VMUG I gave a presentation in which I covered some design tips for VMware [...] [...] van Zanten – Design tips for VMware vSphere 4Recently at the Belgium VMUG I gave a presentation in which I covered some design tips for VMware [...]

]]> By: Duncan http://www.gabesvirtualworld.com/presentation-design-tips-for-vmware-vsphere-4/comment-page-1/#comment-464 Duncan Sun, 01 Nov 2009 07:06:26 +0000 http://www.gabesvirtualworld.com/?p=669#comment-464 It does not matter Tom as long as it is documented indeed. I would personally prefer the approach that makes the most sense which is the first and second host in a cluster. It does not matter Tom as long as it is documented indeed. I would personally prefer the approach that makes the most sense which is the first and second host in a cluster.

]]> By: Duncan http://www.gabesvirtualworld.com/presentation-design-tips-for-vmware-vsphere-4/comment-page-1/#comment-463 Duncan Sun, 01 Nov 2009 07:04:43 +0000 http://www.gabesvirtualworld.com/?p=669#comment-463 maybe you can also post the context as I hardly see any decisions based business requirements? maybe you can also post the context as I hardly see any decisions based business requirements?

]]> By: Tom http://www.gabesvirtualworld.com/presentation-design-tips-for-vmware-vsphere-4/comment-page-1/#comment-728 Tom Thu, 29 Oct 2009 18:13:22 +0000 http://www.gabesvirtualworld.com/?p=669#comment-728 Perfect sense. Except that I would not say 1st and 2nd host, I would explain more like what you said here.<br>Your point is that one must always know which host(s) the VC VM is on, but which hosts in the cluster, it doesn't really matter.<br>In smaller environments this is easy, I'm sure in larger environments this can be difficult.<br>Thank you, Tom Perfect sense. Except that I would not say 1st and 2nd host, I would explain more like what you said here.
Your point is that one must always know which host(s) the VC VM is on, but which hosts in the cluster, it doesn't really matter.
In smaller environments this is easy, I'm sure in larger environments this can be difficult.
Thank you, Tom

]]> By: Tom http://www.gabesvirtualworld.com/presentation-design-tips-for-vmware-vsphere-4/comment-page-1/#comment-462 Tom Thu, 29 Oct 2009 11:13:22 +0000 http://www.gabesvirtualworld.com/?p=669#comment-462 Perfect sense. Except that I would not say 1st and 2nd host, I would explain more like what you said here.<br>Your point is that one must always know which host(s) the VC VM is on, but which hosts in the cluster, it doesn't really matter.<br>In smaller environments this is easy, I'm sure in larger environments this can be difficult.<br>Thank you, Tom Perfect sense. Except that I would not say 1st and 2nd host, I would explain more like what you said here.
Your point is that one must always know which host(s) the VC VM is on, but which hosts in the cluster, it doesn't really matter.
In smaller environments this is easy, I'm sure in larger environments this can be difficult.
Thank you, Tom

]]> By: Gabrie van Zanten http://www.gabesvirtualworld.com/presentation-design-tips-for-vmware-vsphere-4/comment-page-1/#comment-727 Gabrie van Zanten Thu, 29 Oct 2009 03:30:47 +0000 http://www.gabesvirtualworld.com/?p=669#comment-727 Hi Tom,<br><br>(Also replied to you by e-mail)<br><br>Your question on why run vCenter on 1st and 2nd host only.... Well, if you have vCenter moved around constantly by DRS you don't always know on which host it is running. Now, if a real disaster happens, it might happen that you lose your vCenter and want to use direct connections to your ESX host to restart the vCenter VM. But when vCenter is down, you have no way of figuring out on which host the vCenter VM was last seen. You could connect to each host in your cluster and search for it there, but image doing this for 8 or 16 hosts with a manager breathing down your neck.<br><br>So the easiest way is to excluded the vCenter VM from DRS. It will now never be VMotioned without you knowing. If you now also agree upon with your fellow admins that vCenter should always run on the first host in the cluster. You always directly know where vCenter is. Should host1 require maintenance, you move vCenter to the second and move it back to the first afterwards.<br><br>Regards<br>Gabe Hi Tom,

(Also replied to you by e-mail)

Your question on why run vCenter on 1st and 2nd host only…. Well, if you have vCenter moved around constantly by DRS you don't always know on which host it is running. Now, if a real disaster happens, it might happen that you lose your vCenter and want to use direct connections to your ESX host to restart the vCenter VM. But when vCenter is down, you have no way of figuring out on which host the vCenter VM was last seen. You could connect to each host in your cluster and search for it there, but image doing this for 8 or 16 hosts with a manager breathing down your neck.

So the easiest way is to excluded the vCenter VM from DRS. It will now never be VMotioned without you knowing. If you now also agree upon with your fellow admins that vCenter should always run on the first host in the cluster. You always directly know where vCenter is. Should host1 require maintenance, you move vCenter to the second and move it back to the first afterwards.

Regards
Gabe

]]> By: Jared Evans http://www.gabesvirtualworld.com/presentation-design-tips-for-vmware-vsphere-4/comment-page-1/#comment-730 Jared Evans Thu, 29 Oct 2009 01:24:05 +0000 http://www.gabesvirtualworld.com/?p=669#comment-730 Thanks for the PDF! Thanks for the PDF!

]]>