We are currently running a thin provisioned SAN back-end with a thick provisioned VM environment. I'm trying to understand how this works / the logic behind it. Is the SAN essentially saying "I'm going to give VM a logical block, but I will only account for what is used" and then the VM env is saying "oh I have this whole block of storage, I'm going to take it all"?
That is the scenario that I laid out in my mind, but I'm looking for confirmation as to what is actually happening here.
Since thick provision lazy zeroed only allocate the space but don't zero it out (like thick eager zeroed does), from SAN it will behave in the same way of a thin provision VM. But from VMware, you will
Quip doubles as a “living” wiki and a project management tool that evolves with your organization. As you finish projects in Quip, the work remains, easily accessible to all team members, new and old.
- Increase transparency
- Onboard new hires faster
- Access from mobile/offline
This is an issue that we can get adding / removing permissions in the vCSA 6.0. We can also have issues searching for users / groups in the AD (using your identify sources). This is how one of the ways to handle this issues and fix it.
This tutorial will walk an individual through the steps necessary to install and configure the Windows Server Backup Utility.
Directly connect an external storage device such as a USB drive, or CD\DVD burner:
If the device is a USB drive, ensure i…
This video shows you how to use a vSphere client to connect to your ESX host as the root user.
Demonstrates the basic connection of bypassing certification set up.
Demonstrates how to access the traditional view to begin managing your virtual mac…