![]() ![]() To get vSAN up and running the following tasks have to be performed: At least that’s how we configure it via the vSphere Web Client.VMkernel ports have to be created for each host for vSAN communicationĪfter steps 1-4 have have been completed, the vSAN Configuration Wizard can be used to enable vSAN. These tasks are typically accomplished using the Web Client as part of vCenter, but if the vSAN datastore isn’t available, how can vCenter be deployed to it? Using a Temporary Datastoreīy creating a temporary datastore, the VCSA installer could deploy the VCSA there, and once everything was configured, the VCSA could be SvMotioned to the vSAN datastore, the temporary datastore could be removed, and those disks could be claimed for vSAN.William Lam has a blog post on the steps to use this method: There are a lot of moving parts that aren’t necessarily difficult, but definitely time consuming. ( ) Manually Creating a vSAN configurationįor those that are more comfortable with the ESXi command line, can manually create a vSAN cluster. This is not very difficult, but does require some default storage policy manipulation. ![]() ![]() Not quite as many moving parts, does require cli access to ESXi and specific steps. William Lam has another good post on how to use this method: ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |