Critical virtualization mistakes that junior admins should avoid

1. Using desktop virtualization products like Vmware workstation…for production servers

2. Using unsupported virtualization product. If the product has a bug no support to call.

3. Installing other applications on the host and using it for other purposes besides virtualization.Example: running a file server on a windows/linux host. This may degrade host and VM performance.4. Overloading host resources: sizing should be done properly and the performance of the host resource (CPU, RAM, Disk, Network) should be monitored permanently

5. Forgotten snapshots: a snapshot will contineously grow until eating all the space reserved for the guests. Think about retaining it only when needed

6. Cloning the virtual machines: a cloned Windows VM will get the same SID as the original one. This SID should be modified using Sysprep or the old newsid. If you keep this SID, you will have trouble as this VM is seen as the same VM like the original one. (for example: in AD or WSUS you will see them as one computer…). Even after cloning linux, you should think about customizing it. For example you may get in trouble if you do not change the mac address…Instead of cloning use templates!

7. Oversizing or undersizing guests: use recommendations of the vendor of the applications to size guests. Peformance of guests should be contineously monitored.

8. Forgetting backups:this is an important point added by my friend Bassem. When a VM crashes, you should be able to recover it from a backup.

9. Brutal shutdown of the guest: with some hypervisors, there’s a power off button. This is equivalent to cutting electricity to a server. shutting down the guest in this way may damage the VM. To shutdown the guest properly use the shutdown menu from the OS or depending on the hypervisor do it in a clean way from the administration interface (“shutdown guest” with vSphere)

For more visit our complete blog site…!!