VMware: Clustering VirtualCenter 2.5 with MSCS


Eric Sloof heeft een document op zijn blog geplaatst over hoe je VC 2.5 kunt clusteren met MSCS. Dit document is geschreven door Chris Skinner een Technical trainer van VMware.

 

This paper documents the steps to successfully implement a high availability solution for VirtualCenter 2.5 using Microsoft’s cluster services. There are some basic requirements to start the process. Microsoft requires Active Directory for cluster services. Additionally, Windows 2003 Enterprise server or higher will be necessary. This document was compiled from several sources. It demonstrates creating a VC cluster on the same ESX host (cluster-in-a-box) with a SAN-based quorum disk. The hyperlinks at the end of the document has more detailed information for other types of configurations, such as, cluster-across-boxes and physical-to-virtual.

 

Chris and Eric, thanks for sharing

Bron: ntpro.nl

VMware: Deploying VI with Cisco


Anyway, so what better time is there to announce the publication of an in-depth deployment paper jointly authored by Cisco and VMware. We posted this paper about a week ago on the vmware.com/go/networking site. It’s around 90 pages, so no short read; but it delves into many of the considerations, architectures, etc in deploying VI with Cisco switches.

Download de pdf hier: http://www.vmware.com/files/pdf/vmi_cisco_network_environment.pdf

 

Bron: http://blogs.vmware.com/networking/2008/06/deploying-vi-wi.html

VMware: Recreating Missing VMDK Descriptor Files!


Paul Shannon heeft een post geschreven over hoe je VMDK descriptor files kunt aanmaken.

A few times over the years VMDK files have been ‘lost’ when a customer has had to shutown their storage in a less than graceful fashion.

In every case so far, touch wood, it is only the desciptor files that have been deleted so the raw data is still present in the *-flat.vmdk file.

It is actually quite simple to rescue the situation you simply restore from backup. Ahaha what if you do not have a backup, then there is another way.

Lees de rest van de post hier: http://www.vm-aware.com

NetApp: Open Systems SnapVault for VI3


 

Paul Shannon poste het onderstaande op zijn blog: http://www.vm-aware.com/.

OSSV installs directly into the VMware ESX service console and acts as a very light-weight interface to backup Virtual Machines on NetApp storage and non-NetApp storage. It works best with NetApp Protection Manager, but works well as a stand-alone product.  There’s also an excellent Best Practice guide for OSSV available here.

 

Bron: http://www.vm-aware.com/

VMware: First benchmarks with 10 GigE


Generally this is exactly what we expected: to be able to provide good performance to many virtual servers which do network and/or disk-I/O only periodically without overprovisioning the whole infrastructure.

At the moment there is exactly one dual-port 10 GigE card in every VMware server and there are two physical connections to two different switches – a much cleaner setup than the 12 (!) GigE interfaces per server we had before

Lees de rest van de benchmark hier: http://21stcenturystorage.cebis.net

VMware: Top Things you should know about VI


Een tip: zie de volgende site: http://vmware-land.com/Top_10_Lists.html

Top 10 things you must read when trying to sell Vmware as a solution to management
Top 10 things you must read if you are new to VMware
Top 10 things you must read to get more technical with VI3
Top 10 things you must read about Vmware Storage (SAN/NAS/iSCSI/NFS)
Top 10 things you must read about Vmware Security
Top 10 things you must read about Vmware Troubleshooting
Top 10 things you must read about Vmware Networking
Top 10 things you must read about VirtualCenter
Top 10 things you must read about Vmware Performance
Top 10 things you must read about Memory
Top 10 things you must read about the ESX Service Console
Top 10 things you must read about Disaster Recover/Business Continuity and Vmware
Top 10 reasons to go to VMworld 2007

VMware: start a VM in ESX 3.5 on WS 6.5


Eric Sloof heeft het onderstaan de al gepost op zijn blog:

From the ESX or VC client, highlight the VM and select > Edit virtual machine settings
Select Resources tab
Un-check Unlimited in the right pane and lower Mhz count to 700
Select Advanced CPU in the left pane
Under Scheduling Affinity in the right pane > Select Run on processor(s):
Check "0"
Click OK to close VM edit window
Boot VM