I plan to implement "virtualization" in a near future with vmware products but i've some doubts after reading and discussing the subject but doubts still remain and I would like to ear a 2nd opinion from you.
Question: 1- Shall we consider having the VMDK file in a separate machine e.g a NAS and mount it in the vmware server? if so, a 1Gb ethernet cable connection is enough to support acces to 2 or 3 of these VMDK files in the NAS server?
2 - Is it recomendable or a good practice add 1 phisycal NIC per each VM we had to our server? or a physical NIC shared by all is enough?
3 - Is it peacefull to copy the VMDK file to make regular backups, for e.g. via rsync? There's no need to stop the VM first? to make the backup?
4 - Is it recomendable create a LVM volume e.g. ( 4x1TB HDD) in the mentioned NAS storage, and then split it into the space we need for each VM? for instance VM1 (1TB), VM2 (2,5TB) ?
I would appreciate very much if someone could help me with these doubts or suggest some improvements or steps i should adopt in order to create a good 1rst virtualization environment..
I'm on the same boat with you, but I've done my research from various sources and one of them is from the ESX Server Best Practice which give advice as below: Q1. Yes, deploy it on the SAN, I'd make it two in case there is a performance bottleneck between the SAN and the Server and to the network.
Q2. Four NIC ports for performance, security, and redundancy and two Fibre Channel ports for redundancy are the best practice for ESX versions earlier than version 3. For ESX version 3, six NIC ports are recommended for performance, security, and redundancy.
If adding more networks for use by the VMs, either use 802.1q VLAN tagging to run over the existing pair of NICs associated with the VMs or add a new pair of NICs for the VMs.
When using iSCSI with ESX version 3, add another NIC port to the service console