This is the VMware vSphere Design Deep-Dive. I have aggregated all of the design considerations that I could find that need to be assessed in a VMware vSphere architecture design. Brevity and bullet-points are used to keep the information concise and readable. If you are going down the VMware vSAN route, consider these design considerations […]
via vSphere Design Considerations — vcdx133.com
In addition to the support of Nutanix clusters that use Nutanix native AHV hypervisors, HYCU introduces the support for Nutanix environments that use VMware ESXi hypervisors. By using the native Nutanix storage layer snapshot technology, VMware snapshot stuns are avoided.
via Demo: ESXi Backup with Nutanix Snapshot with HYCU — IT BLOOD PRESSURE
Finally has been announced (or better, confirmed) that VMware plans to deprecate the Flash-based vSphere Web Client with the next numbered release (not update release) of VMware vSphere. What does it mean, that the HTML5-based vSphere Client will become the only GUI client… finally! After the death of the vSphere Client for Windows, written with C#…
via Client options for VMware vSphere — vInfrastructure Blog
You are setting up a new template or VM to be used with SQL Server and to get the best performance you are adding multiple disks to the VM. When you first boot the VM the disks are all offline. First thing you do is change the default SAN policy in diskpart to set disks…
via Windows Script for Marking All Disks Online — Long White Virtual Clouds
For a long time, it has been widely considered that thick provisioning is required to achieve maximum storage performance and for many years this was a good rule of thumb. Before we get into details, what are Thick and Thin provisioning? … Continue reading →
via It’s 2017, let’s review Thick vs Thin Provisioning — CloudXC
REF: http://blogs.vmware.com/apps/2016/06/rush-post-microsoft-convenience-update-and-vmware-vmxnet3-incompatibilities.html
Microsoft recently released a Convenience Update for Windows 7 and Windows 2008 R2 which will casuse majot inconvenience if using VMXNet 3.
The announcement at https://support.microsoft.com/en-us/kb/3125574 clearly says:
Symptoms
A new Ethernet vNIC may be created with default settings in place of the previously existing vNIC, causing network issues. Any custom settings on the previous vNIC are still persisted in the registry but unused.
Resolution
To resolve this issue, uninstall the convenience rollup.
Status
Microsoft is investigating this issue to determine proper course of action with VMWare. To resolve this issue uninstall the convenience rollup. Further information will be posted here as the investigation continues.
Be warned.. and always always follow change management and test systems before updating production systems.
