{"id":21377,"date":"2017-07-17T09:00:29","date_gmt":"2017-07-17T07:00:29","guid":{"rendered":"http:\/\/nolabnoparty.com\/?p=21377\/"},"modified":"2017-07-14T08:38:10","modified_gmt":"2017-07-14T06:38:10","slug":"starwind-virtual-san-setup-datastore-pt-3","status":"publish","type":"post","link":"https:\/\/nolabnoparty.com\/en\/starwind-virtual-san-setup-datastore-pt-3\/","title":{"rendered":"StarWind Virtual SAN setup datastore - pt.3"},"content":{"rendered":"

\"starwindvsandatastore01\"<\/p>\n

The StarWind Virtual SAN configuration is finalized connecting the created devices<\/strong> to the ESXi hosts of the StarWind cluster.<\/p>\n

To ensure storage resilience, the application relies\u00a0on redundant network links<\/strong> between StarWind hosts allowing to maintain a fully fault tolerant storage cluster with just hosts. This solution avoids the need of using a third entity<\/strong> to maintain resilience in case of hardware failure.<\/p>\n

 <\/p>\n

Blog series<\/h2>\n

StarWind Virtual SAN installation - pt.1<\/a>
\nStarWind Virtual SAN configuration - pt.2<\/a>
\nStarWind Virtual SAN setup datastore - pt.3<\/p>\n

 <\/p>\n

Discover targets<\/h2>\n

To connect previously created\u00a0devices to the ESXi hosts, you have to select the first host and go to\u00a0Configure > Storage Adapters<\/strong>.\u00a0Select the adapters under iSCSI Software Adapter<\/strong> then go to Network Port Binding<\/strong> tab. Here you can find the StarWind_iSCSI_VMs<\/em> bind created in part 1<\/a>.<\/p>\n

\"starwindvsandatastore02\"<\/p>\n

Go to Targets<\/strong> and make sure Dynamic Discovery<\/strong> is selected. Click Add<\/strong> to add StarWind Servers nodes.<\/p>\n

\"starwindvsandatastore03\"<\/p>\n

Enter the IP address of the first<\/strong> StarWind Server node and click OK<\/strong>.<\/p>\n

\"starwindvsandatastore04\"<\/p>\n

Now enter the IP address of the second<\/strong> StarWind Server node then click OK<\/strong>.<\/p>\n

\"starwindvsandatastore05\"<\/p>\n

Now click Rescan<\/strong> button to discover newly added storage devices.<\/p>\n

\"starwindvsandatastore06\"<\/p>\n

The StarWind device has been discovered successfully.<\/p>\n

\"starwindvsandatastore07\"<\/p>\n

Repeat same procedure for the second ESXi host.<\/p>\n

\"starwindvsandatastore08\"<\/p>\n

 <\/p>\n

Create the datastore<\/h2>\n

Select the first host and go to Configure > Datastore<\/strong>. Click on Create a new datastore<\/strong> icon to setup the datastore.<\/p>\n

\"starwindvsandatastore09\"<\/p>\n

Select VMFS<\/strong> as datastore type and click Next<\/strong>.<\/p>\n

\"starwindvsandatastore10\"<\/p>\n

Enter a Datastore name<\/strong> and select the StarWind iSCSI device to use. Click Next<\/strong>.<\/p>\n

\"starwindvsandatastore11\"<\/p>\n

Specify the VMFS version<\/strong> (i.e. VMFS 6) and click Next<\/strong> to continue.<\/p>\n

\"starwindvsandatastore12\"<\/p>\n

Specify the Partition Configuration<\/strong> and click Next<\/strong>.<\/p>\n

\"starwindvsandatastore13\"<\/p>\n

Review the settings and click Finish<\/strong> to create the datastore.<\/p>\n

\"starwindvsandatastore14\"<\/p>\n

The StarWind datastore has been created successfully.<\/p>\n

\"starwindvsandatastore15\"<\/p>\n

Check that created storage is connected also to the second host of the StarWind cluster.<\/p>\n

 <\/p>\n

Datastore path<\/h2>\n

Since StarWind Virtual SAN does not support any form of NIC teaming<\/strong> for resiliency or throughput aggregation, the recommended MPIO mode is Round-Robin<\/strong>.<\/p>\n

Right click the created StarWind datastore and select Settings<\/strong>.<\/p>\n

\"starwindvsandatastore16\"<\/p>\n

Go to Connectivity and Multipathing<\/strong> tab and select the first host. Click on Set Multipathing<\/strong> button.<\/p>\n

\"starwindvsandatastore17\"<\/p>\n

In Path selection policy<\/strong> field, specify Round Robin (VMware)<\/strong> and click OK<\/strong>.<\/p>\n

\"starwindvsandatastore18\"<\/p>\n

The policy is now set to Round Robin.<\/p>\n

\"starwindvsandatastore19\"<\/p>\n

Repeat same procedure for the second host.<\/p>\n

\"starwindvsandatastore20\"<\/p>\n

The virtual machines can now be stored on the new datastore\u00a0provided by StarWind.<\/p>\n

Local storage of both ESXi hosts have been converted in a fault tolerant shared storage mirrored between the nodes<\/strong>. StarWind applications ensures data safety and maintains continuous application availability.<\/p>\n

\"starwindvsandatastore21\"<\/p>\n

StarWind vSAN is available as 30-day trial<\/a>\u00a0for testing purposes.<\/p>\n

StarWind offers also a\u00a0Free Edition<\/a>, a self-supported or community-supported version that can be managed through the Windows PowerShell or SCVMM<\/strong> since the access to StarWind Management Console is limited to 30 days<\/strong> after installation.<\/p>\n

\"signature\"<\/p>\n","protected":false},"excerpt":{"rendered":"

The StarWind Virtual SAN configuration is finalized connecting the created devices to the ESXi hosts of the StarWind cluster. To ensure storage resilience, the application relies\u00a0on redundant network links between StarWind hosts allowing to maintain a fully fault tolerant storage cluster with just hosts. This solution avoids the need of using a third entity to maintain resilience in case of hardware failure.<\/p>\n","protected":false},"author":3,"featured_media":21505,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"rop_custom_images_group":[],"rop_custom_messages_group":[],"rop_publish_now":"initial","rop_publish_now_accounts":{"linkedin_93tdZWzMZc_93tdZWzMZc":"","facebook_2879994398731222_17841400390232720":"","twitter_113568041_113568041":"","mastodon_115463926174894442_115463926174894442":""},"rop_publish_now_history":[],"rop_publish_now_status":"pending","footnotes":""},"categories":[903,1787],"tags":[1774,963,1775],"class_list":["post-21377","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-vmware-en","category-starwind-en","tag-starwind","tag-storage-en","tag-virtual-san","has_thumb"],"_links":{"self":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/posts\/21377","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/comments?post=21377"}],"version-history":[{"count":0,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/posts\/21377\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/media\/21505"}],"wp:attachment":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/media?parent=21377"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/categories?post=21377"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/tags?post=21377"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}