StarWind Resource Library

StarWind iSCSI SAN & NAS: Configuring HA Shared Storage for Scale-Out File Servers in Windows Server 2012

Published: January 19, 2013

INTRODUCTION

 

CREATING AN HA DEVICE

1. Open a StarWind configuration file.

Note: The default path is C:\Program Files\StarWind Software\StarWind\StarWind.cfg

2. Find the string “<!–<iScsiDiscoveryListInterfaces value=”1″/> –>” and uncomment it (should look as follows: <iScsiDiscoveryListInterfaces value=”1″/>).

3. Restart StarWind Service and repeat the same procedure on another StarWind HA node.

4. Launch StarWind Management Console: Start -> All Programs -> StarWind Software -> StarWind.

Note: The StarWind Console icon appears in the system tray when the Console is running. To open StarWind Management Console, double-click the icon or right-click it, and then select Start Management Console from the shortcut menu.

5. Select the server you want to provide with the iSCSI target device from the Console tree. Double-click the host to connect.

Note: If you are prompted to enter login and password, specify “root” and “starwind”, respectively. These are the default login and password, but you can always change them later.

6. After connecting to StarWind Service, you can create devices and targets on the server. Open Add Device Wizard by one of the following ways:

  • Select Add Device from the Target menu.
  • Select Add Device from the Devices shortcut menu (right-click to open it).

7. Add Device Wizard appears. Please, follow the wizard’s steps to create a new HA device.

8. Select the High Availability Device option.

9. Click Next to continue.

10. Click Add to add a new host.

11. Specify partner server parameters. Enter the server IP-address. If needed, specify username and password for StarWind Service in the corresponding text fields. Click OK.

12. Click Next to continue.

13. Specify the appropriate information in the Target Alias and Target Name text fields.

Note: The name must be unique. Under this name the device is declared to iSCSI initiators that are connected to StarWind Service over an IP network.

14. Click to specify a name and location of an HA virtual disk on the server. If you want to create a new virtual disk, select the Create new checkbox.

15. Click Next to continue.

16. Specify target and virtual disk parameters of the second node.

17. Click Next to continue.

18. Configure data synchronization and Heartbeat channel parameters.

Note: At least one Heartbeat channel must be separated from a synchronization channel due to the availability considerations.

19. Click Next to continue.

20. Specify cache parameters of the HA device.

21. Click Next to continue.

22. Select an initialization method of the HA device.

23. Check whether device parameters are correct. Click Back to make any changes. Click Next to continue.

24. Click Finish to close the wizard.

Follow the similar procedure to create the second HA device that will be used as a storage disk.

 

 

CONFIGURING CLUSTER NODES

This document assumes that you have already configured Active Directory and two servers on the domain. It also assumes that you have enabled the Failover Clustering, Multipath I/O features, and the File Server role on both servers. These configurations can be performed using Server Manager (the Add Roles and Features option).

1. Launch Server Manager, select the Manage item, and click the Add Roles and Features option. Install the File Server role, Multipath I/O, and Failover Clustering features following the wizard’s steps.

Note: Restart the server after installation is completed.

2. Select Role-based or feature-based installation as an installation type and click Next to continue.

3. Select a server from the server pool. Use a filter to find an appropriate server.

4. Click Next to continue.

5. Select the File and iSCSI Services checkbox in the Roles and Features section. Click Next to continue.

6. Click Add Features and Next to continue.

7. Select Failover Clustering and Multipath I/O checkboxes in the Features section.

8. Click Next to continue.

9. Select the corresponding checkbox if you want the server to be restarted automatically, and click Install. Otherwise, click Install and restart server manually after the installation is completed.

 

CONNECTING TARGETS

To connect the previously created disks on all servers that will be added to the cluster:

1. Launch Microsoft iSCSI Initiator: Start > Administrative Tools > iSCSI Initiator. The iSCSI Initiator Properties window appears.

2. Navigate to the Discovery tab.

3. Click the Discover Portal button. Enter an IP address of each StarWind Server in the appropriate field of the Discover Target Portal dialog. Click OK.

4. Complete the same steps for the second node.

5. Click the Targets tab. The previously created targets are listed in the Discovered Targets section.

Note: If the created targets are not listed, check the firewall settings of the StarWind Server as well as the list of networks served by the StarWind Server (go to StarWind Management Console -> Configuration -> Network).

6. Select each of the targets and click Connect to add them.

7. Select Add this connection to the list of Favorite Targets and Enable multi-path checkboxes in the Connect to Target dialog.

8. Repeat the actions described in the previous step for each target.

9. Open the MPIO Manager: Start -> Administrative Tools -> MPIO.

10. Go to the Discover Multi-Paths tab. Select the Add support for iSCSI devices checkbox and click Add.

11. When prompted to restart the server, click Yes to proceed. After the server is restarted, initialize the disk and create partitions, as if it was a physical hard drive.

 

INITIALIZING DISKS

Note: The StarWind disks must be initialized and formatted to be used as cluster disks.

Note: Changes made to the first node (e.g. initialization or partition) are applied to the second node as soon as it is brought online.

To initialize disks and create partitions:

1. Launch the Computer Management console.

2. Go to Storage -> Disk Management.

3. Right-click each disk and select Online Disk to bring it online.

4. Right-click each disk and select Initialize Disk. Follow the wizard’s instructions to initialize disks.

Note: Select MBR (Master Boot Record) as a partition style.

5. Click OK to continue.

The Computer Management console should look as shown on the screenshot below.

To create partitions and format new disks:

1. Right-click each disk in the Computer Management window and select New Simple Volume.

2. Follow the wizard’s instructions to create partitions.

The Computer Management window should look as shown on the screenshot below.

Perform the same actions on the other servers. Creation of partitions is no longer necessary.

 

CREATING A CLUSTER

To validate a cluster:

1. Open Server Manager. Select the Failover Cluster Manager item from the Tools menu.

2. Verify whether the servers are suitable for building a cluster: click Validate a Configuration in the Actions section.

To create a cluster:

1. Click the Create a Cluster item in the Actions section of Failover Cluster Manger. As Create Cluster Wizard appears, click Next to continue.

2. Specify servers to be included to the cluster.

3. Click Next to continue.

4. Specify a cluster name.

Note: If the cluster servers get IP addresses over DHCP, the cluster also gets its IP address over DHCP. If the IP addresses are set statically, you need to set a cluster IP address manually as well.

5. Click Next to continue.

6. Make sure that all of the settings are correct. Click Previous to make any changes. Click Next to continue.

7. The process of cluster creation starts. After it is completed, the system displays a report with detailed information.

8. Click Finish to close the wizard.

The Failover Cluster Manager window should look as follows.

 

 

CONFIGURING AND MANAGING SCALE-OUT FILE SERVERS

Adding Disks to Cluster Shared Volumes

1. Right-click the disk assigned to Available Storage (see the Assigned To column), and click Add to Cluster Shared Volumes.

2. The disk will be displayed as a CSV at the Failover Cluster Manager window as shown in the screenshot below.

 

 

Configuring a Scale-Out File Server Role

To configure a Scale-Out File Server role:

1. Launch Failover Cluster Manager.

2. Right-click the Role item and select Configure Role. High Availability Wizard appears.

3. As High Availability Wizard appears, click Next to continue.

4. Select the File Server role and click Next.

5. Select File Server for scale-out application data and click Next.

6. On the Client Access Point page, in the Name text field type a NETBIOS name that will be used to access a Scale-Out File Server.

7. Click Next to continue.

8. Check the selected settings. Click Next to continue or Previous to make any changes.

9. Review the information on the Summary page and click Finish.

10. The Failover Cluster Manager window should look as shown in the screenshot below.

 

 

Creating a Continuously Available File Share on a Cluster Shared Volume

To create a continuously available file share on the cluster shared volume:

1. Launch the Failover Cluster Manager.

2. Select the Roles item.

3. Right-click a previously created file server role and select Add File Share.

4. Select SMB Share —Applications from the list of profiles.

5. Click Next.

6. Select a CSV to host the share.

7. Click Next.

8. Enter a share name and verify the path to the share.

9. Click Next.

10. Ensure the Enable Continuous Availability checkbox is selected.

11. Click Next.

12. Click Customize permissions and grant the following permissions:

  • If you are using Scale-Out File Server for Hyper-V, all Hyper-V computer accounts, the SYSTEM account, and all Hyper-V administrators must be granted full control on the share and file system.
  • If you are using Scale-Out File Server on Microsoft SQL Server, the SQL Server service account must be granted full control on the share the file system.

 

13. Click Next to continue.

14. Review the settings and click Create. To make any changes, click Previous.

15. Review the results on the last page and click Close.

The Failover Cluster Manager should look as shown on the screenshot below.