HA Cluster Setup (external SAN) - Revision history

Qadmin: Rewrite to house style: verified software-adapter and auto-config paths for iSCSI/NVMe-oF back ends, the FC ALUA session check, per-port protocol access; replace the troubleshooting transclusion with a link to Scale-up HA Storage Pool Troubleshooting (QSTOR-12352)

2026-09-04T05:28:33Z

Rewrite to house style: verified software-adapter and auto-config paths for iSCSI/NVMe-oF back ends, the FC ALUA session check, per-port protocol access; replace the troubleshooting transclusion with a link to Scale-up HA Storage Pool Troubleshooting (QSTOR-12352)

Show changes

Qadmin: Replace four stale template transclusions with pointers to the verified sections on HA Cluster Setup (JBODs). Template:StoragePoolHAGroupFailover documented the failover sequence wrongly - it said the virtual interface is shut down and then the pool deported, whereas the pacemaker resource group moves BEFORE the export (verified live against CTaskStoragePoolHaFailoverGroupFailover). The site cluster, HA group, VIF and failover are common to both architectures; this page keeps the SAN-specific...

2026-09-04T04:00:35Z

Replace four stale template transclusions with pointers to the verified sections on HA Cluster Setup (JBODs). Template:StoragePoolHAGroupFailover documented the failover sequence wrongly - it said the virtual interface is shut down and then the pool deported, whereas the pacemaker resource group moves BEFORE the export (verified live against CTaskStoragePoolHaFailoverGroupFailover). The site cluster, HA group, VIF and failover are common to both architectures; this page keeps the SAN-specific...

← Older revision		Revision as of 04:00, 4 September 2026
Line 4:		Line 4:

	== Introduction ==		== Introduction ==

			''This page covers the SAN-specific back-end: presenting shared LUNs from an external array to both appliances. Everything above the shared storage -- the site cluster, the HA group, the virtual interface and failover -- is common to both architectures and is documented on '''[[HA Cluster Setup (JBODs)]]''', which was verified against a live HA cluster.''

	[[File:qs4_clustered_san.png\|thumb\|600px]]		[[File:qs4_clustered_san.png\|thumb\|600px]]
Line 116:		Line 118:


	~~{{Template:ClusteredHACommon}}~~		The site cluster and heartbeat ring underneath an HA group are configured the same way regardless of whether the shared storage is a JBOD or a SAN. See '''[[Site Cluster Setup]]'''.

	~~{{Template:ClusteredHAPoolCreation}}~~		Pool creation is the same as for any scale-up pool, with the HA-specific device rules covered under '''[[HA Cluster Setup (JBODs)#Before you build the HA group\|Before you build the HA group]]'''. See also '''[[Storage Pools]]'''.

	~~{{Template:StoragePoolHAGroupConfiguration}}~~		Creating the HA group and its virtual interface is identical for SAN-backed and JBOD-backed pools. See '''[[HA Cluster Setup (JBODs)#Creating the storage pool HA group\|Creating the storage pool HA group]]''' and '''[[HA Cluster Setup (JBODs)#The HA virtual interface\|The HA virtual interface]]'''.

	~~{{Template:StoragePoolHAGroupFailover}}~~		Failover behaviour does not depend on the type of shared storage. See '''[[HA Cluster Setup (JBODs)#Failover\|Failover]]''', which documents the verified order of operations, and '''[[HA Cluster Setup (JBODs)#I/O fencing and SCSI-3 persistent reservations\|I/O fencing and SCSI-3 persistent reservations]]'''.

	{{Template:TroubleshootingHAStoragePools}}		{{Template:TroubleshootingHAStoragePools}}

Qadmin: Remove version-era references: dropped Category:QuantaStor6 -- all customers run QuantaStor 6 or newer (wiki-docs rule 13, QSTOR-12352)

2026-09-03T03:15:13Z

Remove version-era references: dropped Category:QuantaStor6 -- all customers run QuantaStor 6 or newer (wiki-docs rule 13, QSTOR-12352)

← Older revision		Revision as of 03:15, 3 September 2026
Line 128:		Line 128:

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

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)]].