HA Cluster Setup (external SAN) - Revision history

Qadmin at 00:29, 7 November 2023

2023-11-07T00:29:40Z

← Older revision		Revision as of 00:29, 7 November 2023
Line 128:		Line 128:

	[[Category:QuantaStor Guide]]		[[Category:QuantaStor Guide]]
	[[Category:~~QuantaStor4~~]]		[[Category:QuantaStor6]]

Qadmin at 23:17, 16 April 2023

2023-04-16T23:17:13Z

← Older revision		Revision as of 23:17, 16 April 2023
Line 30:		Line 30:
	* Activate the Storage Pool		* Activate the Storage Pool
	* Test failover		* Test failover

			== Deployment of Highly Available (HA) Storage Pool on Seagate Exos ==

			[[Image:youtube_icon.png\|50px\|link=https://www.youtube.com/watch?v=WNCEjgboAQI]] [https://www.youtube.com/watch?v=WNCEjgboAQI QuantaStor 6: Deployment of Highly Available (HA) Storage Pool on Seagate Exos [ 19:02]]]

	== High Availability Tiered SAN/ZFS based SAN/NAS Storage Layout ==		== High Availability Tiered SAN/ZFS based SAN/NAS Storage Layout ==

Qadmin: /* iSCSI SAN Back-end Configuration */

2022-11-02T00:58:11Z

iSCSI SAN Back-end Configuration

← Older revision		Revision as of 00:58, 2 November 2022
Line 73:		Line 73:

	===== iSCSI SAN Back-end Configuration =====		===== iSCSI SAN Back-end Configuration =====
	[[File:Add Software Adapter Web.jpg\|512px\|thumb\|Add an iSCSI SAN Software Adapter.]]		[[File:Add Software Adapter Web 6.jpg\|512px\|thumb\|Add an iSCSI SAN Software Adapter.]]

	* It is highly recommended to separate the networks for the front-end (client communication) vs back-end (communicate between the control and data systems).		* It is highly recommended to separate the networks for the front-end (client communication) vs back-end (communicate between the control and data systems).

Qadmin: /* iSCSI SAN Back-end Configuration */

2021-07-19T21:17:12Z

iSCSI SAN Back-end Configuration

← Older revision		Revision as of 21:17, 19 July 2021
Line 73:		Line 73:

	===== iSCSI SAN Back-end Configuration =====		===== iSCSI SAN Back-end Configuration =====
	[[File:Add Software Adapter.jpg\|512px\|thumb\|Add an iSCSI SAN Software Adapter.]]		[[File:Add Software Adapter Web.jpg\|512px\|thumb\|Add an iSCSI SAN Software Adapter.]]

	* It is highly recommended to separate the networks for the front-end (client communication) vs back-end (communicate between the control and data systems).		* It is highly recommended to separate the networks for the front-end (client communication) vs back-end (communicate between the control and data systems).

Qadmin: /* iSCSI SAN Back-end Configuration */

2021-07-19T21:16:37Z

iSCSI SAN Back-end Configuration

← Older revision		Revision as of 21:16, 19 July 2021
Line 73:		Line 73:

	===== iSCSI SAN Back-end Configuration =====		===== iSCSI SAN Back-end Configuration =====
	[[File:Add ~~iSCSI SAN~~ Adapter ~~Web~~.jpg\|512px\|thumb\|Add an iSCSI SAN Software Adapter.]]		[[File:Add Software Adapter.jpg\|512px\|thumb\|Add an iSCSI SAN Software Adapter.]]

	* It is highly recommended to separate the networks for the front-end (client communication) vs back-end (communicate between the control and data systems).		* It is highly recommended to separate the networks for the front-end (client communication) vs back-end (communicate between the control and data systems).

Qadmin: /* Introduction */

2020-02-07T22:06:23Z

Introduction

← Older revision		Revision as of 22:06, 7 February 2020
Line 7:		Line 7:
	[[File:qs4_clustered_san.png\|thumb\|600px]]		[[File:qs4_clustered_san.png\|thumb\|600px]]

	QuantaStor's clustered storage pool configurations ensure high-availability (HA) in the event of a node outage or storage connectivity to the active node is lost. From a hardware perspective a QuantaStor deployment of one or more clustered storage pools requires at least two QuantaStor systems so that automatic fail-over can occur in the event that the active system goes offline. Another requirement of these configurations is that the disk storage devices for the highly-available pool cannot be in either of the system units. Rather the storage must come from an external source which can be as simple as using one or more SAS JBOD enclosures or for higher performance configurations could be a separate SAN delivering block storage (LUNs) to the QuantaStor front-end systems over FC (preferred) or iSCSI. This guide is focused on how to setup QuantaStor with a FC or iSCSI SAN back-end, for information on how to setup with a JBOD SAS enclosure back-end see ~~the~~ [[https://wiki.osnexus.com/index.php?title=HA_Cluster_Setup_(JBODs) HA Cluster Setup (JBODs)]].		QuantaStor's clustered storage pool configurations ensure high-availability (HA) in the event of a node outage or storage connectivity to the active node is lost. From a hardware perspective a QuantaStor deployment of one or more clustered storage pools requires at least two QuantaStor systems so that automatic fail-over can occur in the event that the active system goes offline. Another requirement of these configurations is that the disk storage devices for the highly-available pool cannot be in either of the system units. Rather the storage must come from an external source which can be as simple as using one or more SAS JBOD enclosures or for higher performance configurations could be a separate SAN delivering block storage (LUNs) to the QuantaStor front-end systems over FC (preferred) or iSCSI. This guide is focused on how to setup QuantaStor with a FC or iSCSI SAN back-end, for information on how to setup with a JBOD SAS enclosure back-end see [[https://wiki.osnexus.com/index.php?title=HA_Cluster_Setup_(JBODs) HA Cluster Setup (JBODs)]].

Qadmin: /* Introduction */

2020-02-07T22:06:00Z

Introduction

← Older revision		Revision as of 22:06, 7 February 2020
Line 7:		Line 7:
	[[File:qs4_clustered_san.png\|thumb\|600px]]		[[File:qs4_clustered_san.png\|thumb\|600px]]

	QuantaStor's clustered storage pool configurations ensure high-availability (HA) in the event of a node outage or storage connectivity to the active node is lost. From a hardware perspective a QuantaStor deployment of one or more clustered storage pools requires at least two QuantaStor systems so that automatic fail-over can occur in the event that the active system goes offline. Another requirement of these configurations is that the disk storage devices for the highly-available pool cannot be in either of the system units. Rather the storage must come from an external source which can be as simple as using one or more SAS JBOD enclosures or for higher performance configurations could be a separate SAN delivering block storage (LUNs) to the QuantaStor front-end systems over FC (preferred) or iSCSI. This guide is focused on how to setup QuantaStor with a FC or iSCSI SAN back-end, for information on how to setup with a JBOD SAS enclosure back-end see the [[~~Clustered_HA_SAN~~/~~NAS_with_JBOD_back-end\|guide for that here~~]].		QuantaStor's clustered storage pool configurations ensure high-availability (HA) in the event of a node outage or storage connectivity to the active node is lost. From a hardware perspective a QuantaStor deployment of one or more clustered storage pools requires at least two QuantaStor systems so that automatic fail-over can occur in the event that the active system goes offline. Another requirement of these configurations is that the disk storage devices for the highly-available pool cannot be in either of the system units. Rather the storage must come from an external source which can be as simple as using one or more SAS JBOD enclosures or for higher performance configurations could be a separate SAN delivering block storage (LUNs) to the QuantaStor front-end systems over FC (preferred) or iSCSI. This guide is focused on how to setup QuantaStor with a FC or iSCSI SAN back-end, for information on how to setup with a JBOD SAS enclosure back-end see the [[https://wiki.osnexus.com/index.php?title=HA_Cluster_Setup_(JBODs) HA Cluster Setup (JBODs)]].

Qadmin: /* FC SAN Back-end Configuration */

2020-02-07T21:33:38Z

FC SAN Back-end Configuration

← Older revision		Revision as of 21:33, 7 February 2020
Line 68:		Line 68:
	===== FC SAN Back-end Configuration =====		===== FC SAN Back-end Configuration =====
	* Create ''Host'' entries, one for each front-end system and add the WWPN of each of the FC ports on the front-end systems which will be used for intercommunication between the front-end and back-end nodes.		* Create ''Host'' entries, one for each front-end system and add the WWPN of each of the FC ports on the front-end systems which will be used for intercommunication between the front-end and back-end nodes.
	* Direct point-to-point physical cabling connections can be made in smaller configurations to avoid the cost of an FC switch. Here's a guide that can help with some [http://blog.osnexus.com/2012/03/20/understanding-fc-fabric-configuration-5-paragraphs/ ~~advice on~~ FC ~~zone setup~~] for larger configurations using a back-end fabric.		* Direct point-to-point physical cabling connections can be made in smaller configurations to avoid the cost of an FC switch. Here's a guide that can help with some [http://blog.osnexus.com/2012/03/20/understanding-fc-fabric-configuration-5-paragraphs/ Understanding FC (and FCoE) fabric configuration in 5 minutes or less] for larger configurations using a back-end fabric.
	* If you're using a FC switch you should use a fabric topology that will give you fault tolerance.		* If you're using a FC switch you should use a fabric topology that will give you fault tolerance.
	* Back-end systems must use Qlogic QLE 8Gb or 16Gb FC cards as QuantaStor can only present Storage Volumes as FC target LUNs via Qlogic cards.		* Back-end systems must use Qlogic QLE 8Gb or 16Gb FC cards as QuantaStor can only present Storage Volumes as FC target LUNs via Qlogic cards.

Qadmin: /* iSCSI SAN Back-end Configuration */

2020-01-07T00:19:58Z

iSCSI SAN Back-end Configuration

← Older revision		Revision as of 00:19, 7 January 2020
Line 73:		Line 73:

	===== iSCSI SAN Back-end Configuration =====		===== iSCSI SAN Back-end Configuration =====
			[[File:Add iSCSI SAN Adapter Web.jpg\|512px\|thumb\|Add an iSCSI SAN Software Adapter.]]

	* It is highly recommended to separate the networks for the front-end (client communication) vs back-end (communicate between the control and data systems).		* It is highly recommended to separate the networks for the front-end (client communication) vs back-end (communicate between the control and data systems).
	* If the back-end systems are in the same grid with the front-end systems, add Host entries with the IQN (or FC WWPN) for each of the front-end systems. These Host entries will be used to assign Storage Volumes from the back-end systems to the front-end systems so that the storage can be aggregated.		* If the back-end systems are in the same grid with the front-end systems, add Host entries with the IQN (or FC WWPN) for each of the front-end systems. These Host entries will be used to assign Storage Volumes from the back-end systems to the front-end systems so that the storage can be aggregated.
Line 78:		Line 80:
	* To establish iSCSI connectivity to the Storage Volumes on the back-end nodes, create a ''Software iSCSI Adapter'' by going to the Hardware Controllers & Enclosures section and adding a iSCSI Adapter. This will take care of logging into and accessing the back-end storage. Again, back-end storage systems must assign their Storage Volumes to all the ''Hosts'' for the front-end nodes with their associated iSCSI IQNs.		* To establish iSCSI connectivity to the Storage Volumes on the back-end nodes, create a ''Software iSCSI Adapter'' by going to the Hardware Controllers & Enclosures section and adding a iSCSI Adapter. This will take care of logging into and accessing the back-end storage. Again, back-end storage systems must assign their Storage Volumes to all the ''Hosts'' for the front-end nodes with their associated iSCSI IQNs.
	* Right-click to Modify Network Port of each port of the back-end systems. Disable client iSCSI access on the slow 1GbE ports or other (management) ports where iSCSI traffic should not flow. (If you have 10GbE be sure to disable iSCSI access on the slower 1GbE ports used for management access and/or remote-replication.)		* Right-click to Modify Network Port of each port of the back-end systems. Disable client iSCSI access on the slow 1GbE ports or other (management) ports where iSCSI traffic should not flow. (If you have 10GbE be sure to disable iSCSI access on the slower 1GbE ports used for management access and/or remote-replication.)

	~~[[File:Add iSCSI SAN Adapter Web.jpg\|512px\|thumb\|Add an iSCSI SAN Software Adapter.]]~~

	==== HA Network Setup ====		==== HA Network Setup ====

Qadmin: /* iSCSI SAN Back-end Configuration */

2020-01-07T00:19:22Z

iSCSI SAN Back-end Configuration

← Older revision		Revision as of 00:19, 7 January 2020
Line 79:		Line 79:
	* Right-click to Modify Network Port of each port of the back-end systems. Disable client iSCSI access on the slow 1GbE ports or other (management) ports where iSCSI traffic should not flow. (If you have 10GbE be sure to disable iSCSI access on the slower 1GbE ports used for management access and/or remote-replication.)		* Right-click to Modify Network Port of each port of the back-end systems. Disable client iSCSI access on the slow 1GbE ports or other (management) ports where iSCSI traffic should not flow. (If you have 10GbE be sure to disable iSCSI access on the slower 1GbE ports used for management access and/or remote-replication.)

	[[File:Add iSCSI SAN Adapter Web.jpg]]		[[File:Add iSCSI SAN Adapter Web.jpg\|512px\|thumb\|Add an iSCSI SAN Software Adapter.]]

	==== HA Network Setup ====		==== HA Network Setup ====