Storage Pool HA Failover Group Execute - Revision history

Qadmin: Redirect this dialog help page to the Administrator Guide section that documents it (QSTOR-12352). These pages were generated and contain unverified detail; the Help button URL is unchanged, so deployed appliances now land on verified content.

2026-09-04T05:19:57Z

Redirect this dialog help page to the Administrator Guide section that documents it (QSTOR-12352). These pages were generated and contain unverified detail; the Help button URL is unchanged, so deployed appliances now land on verified content.

← Older revision		Revision as of 05:19, 4 September 2026
Line 1:		Line 1:
	[[~~File:Exct~~ HA ~~Pool Fail Grp.jpg\|512px\|thumb\|Execute High-Availability~~ (HA) ~~Pool Failover.]]~~		#REDIRECT [[HA Cluster Setup (JBODs)#Creating the storage pool HA group]]

	~~In the context of QuantaStor,~~ the ~~"Execute High-Availability (HA) Pool Failover" feature serves a critical purpose in managing and ensuring the availability and reliability of~~ storage ~~resources. High-availability pools are designed to maintain data accessibility and minimize downtime, even in the event of hardware failures or other issues.~~

	~~== Failover to Same Node ==~~

	~~The 'From System' is where the~~ pool ~~currently resides and the 'To System' is where the pool will be moved to after the failover is completed.~~

	If you are working on starting a pool after doing some maintenance we recommend running a 'failover' where the 'To System' is the same as the 'From System'. When this is done all the pool startup sequence will be run through to restore access to all volumes and shares. Failover in this way is recommended for all HA ~~pools vs a simple Start Pool as the Start Pool is not comprehensive of Cluster VIF movement and other checks.~~

	~~== Failover Performance ==~~

	Failover performance is variable depending on the number of volumes and shares in a given pool. QuantaStor has a highly parallelized failover process to ensure the fastest possible failover speed but there is an incremental cost measured in the milliseconds as more volumes, shares, and snapshots are created. All HDD based storage pools should be configured with 3x SSDs (SAS or NVMe) for metadata offload as this will significantly reduce the HA failover time, so much so that we require metadata offload SSDs on all new hybrid (HDD+SSD) configurations.


	~~'''Navigation:''' Storage Management --> Storage Pools --> Storage Pool HA Resource Group --> Manual Failover ''(toolbar)''~~


	~~{{Template:ReturnToWebGuide}}~~
	~~[[Category:QuantaStor6]]~~
	~~[[Category:WebUI Dialog]]~~
	~~[[Category:Requires Review~~]]

Qadmin at 17:14, 15 August 2025

2025-08-15T17:14:56Z

← Older revision		Revision as of 17:14, 15 August 2025
Line 1:		Line 1:
	[[File:Exct HA Pool Fail Grp.jpg\|512px\|thumb\|Execute High-Availability (HA) Pool Failover.]]		[[File:Exct HA Pool Fail Grp.jpg\|512px\|thumb\|Execute High-Availability (HA) Pool Failover.]]

	In the context of QuantaStor, the "Execute High-Availability (HA) Pool Failover" feature serves a critical purpose in managing and ensuring the availability and reliability of storage resources. High-availability pools are designed to maintain data accessibility and minimize downtime, even in the event of hardware failures or other issues. ~~The specific purpose of executing a high-availability pool failover in QuantaStor includes:~~		In the context of QuantaStor, the "Execute High-Availability (HA) Pool Failover" feature serves a critical purpose in managing and ensuring the availability and reliability of storage resources. High-availability pools are designed to maintain data accessibility and minimize downtime, even in the event of hardware failures or other issues.

			== Failover to Same Node ==

			The 'From System' is where the pool currently resides and the 'To System' is where the pool will be moved to after the failover is completed.

			If you are working on starting a pool after doing some maintenance we recommend running a 'failover' where the 'To System' is the same as the 'From System'. When this is done all the pool startup sequence will be run through to restore access to all volumes and shares. Failover in this way is recommended for all HA pools vs a simple Start Pool as the Start Pool is not comprehensive of Cluster VIF movement and other checks.

			== Failover Performance ==

			Failover performance is variable depending on the number of volumes and shares in a given pool. QuantaStor has a highly parallelized failover process to ensure the fastest possible failover speed but there is an incremental cost measured in the milliseconds as more volumes, shares, and snapshots are created. All HDD based storage pools should be configured with 3x SSDs (SAS or NVMe) for metadata offload as this will significantly reduce the HA failover time, so much so that we require metadata offload SSDs on all new hybrid (HDD+SSD) configurations.

Qadmin at 17:06, 15 August 2025

2025-08-15T17:06:52Z

← Older revision		Revision as of 17:06, 15 August 2025
Line 3:		Line 3:
	In the context of QuantaStor, the "Execute High-Availability (HA) Pool Failover" feature serves a critical purpose in managing and ensuring the availability and reliability of storage resources. High-availability pools are designed to maintain data accessibility and minimize downtime, even in the event of hardware failures or other issues. The specific purpose of executing a high-availability pool failover in QuantaStor includes:		In the context of QuantaStor, the "Execute High-Availability (HA) Pool Failover" feature serves a critical purpose in managing and ensuring the availability and reliability of storage resources. High-availability pools are designed to maintain data accessibility and minimize downtime, even in the event of hardware failures or other issues. The specific purpose of executing a high-availability pool failover in QuantaStor includes:

	*Redundancy and Fault Tolerance: High-availability pools are configured to ensure redundancy and fault tolerance. If a node within the high-availability pool encounters a failure, such as hardware issues or network problems, initiating a failover ensures that the workload and data previously handled by the failed node are shifted to another healthy node within the pool.

	*Continuity of Service: Executing a failover is a means to maintain continuous access to storage resources for users or applications. By automatically or manually switching the workload to a standby or backup node, the failover process ensures that the services remain available despite a failure.

	*Automatic or Manual Transition: QuantaStor might support both automatic and manual failover modes. Automatic failover instantly switches operations to the redundant node without human intervention, whereas manual failover allows administrators to control when the switch occurs, potentially after investigating the cause of the issue.

	*Minimizing Downtime: The primary objective of the failover process is to minimize downtime. When a failover is executed promptly and efficiently, it reduces the impact of the failure on ongoing operations, preventing or reducing service disruptions.

	*Redirection of Workload: During a failover, the system redirects and balances the workload to the operational nodes in the high-availability pool. This ensures that data access and storage operations continue without interruption, albeit on alternative nodes.

	*Data Integrity and Recovery: Failover procedures in high-availability configurations are typically designed to maintain data integrity and facilitate recovery. These processes help in ensuring that no data is lost or corrupted during the failover event.

	*Monitoring and Alerting: High-availability failovers are often accompanied by monitoring and alert systems. They track the health of nodes and automatically trigger failovers when predetermined thresholds or failure events are detected.

	It's crucial to plan and configure high-availability setups in advance to ensure they function as intended when needed. Understanding how to execute a failover, the impact it might have on services, and how to restore the original state after addressing the issue is essential for administrators managing QuantaStor environments.

Qadmin at 22:11, 8 May 2024

2024-05-08T22:11:23Z

← Older revision		Revision as of 22:11, 8 May 2024
Line 1:		Line 1:
	[[File:Exct HA Pool ~~Failover~~.jpg\|512px\|thumb\|Execute High-Availability (HA) Pool Failover.]]		[[File:Exct HA Pool Fail Grp.jpg\|512px\|thumb\|Execute High-Availability (HA) Pool Failover.]]

	In the context of QuantaStor, the "Execute High-Availability (HA) Pool Failover" feature serves a critical purpose in managing and ensuring the availability and reliability of storage resources. High-availability pools are designed to maintain data accessibility and minimize downtime, even in the event of hardware failures or other issues. The specific purpose of executing a high-availability pool failover in QuantaStor includes:		In the context of QuantaStor, the "Execute High-Availability (HA) Pool Failover" feature serves a critical purpose in managing and ensuring the availability and reliability of storage resources. High-availability pools are designed to maintain data accessibility and minimize downtime, even in the event of hardware failures or other issues. The specific purpose of executing a high-availability pool failover in QuantaStor includes:

Qadmin at 21:37, 8 May 2024

2024-05-08T21:37:18Z

← Older revision		Revision as of 21:37, 8 May 2024
Line 1:		Line 1:
	[[File:Exct HA Failover.jpg\|512px\|thumb\|Execute High-Availability (HA) Pool Failover.]]		[[File:Exct HA Pool Failover.jpg\|512px\|thumb\|Execute High-Availability (HA) Pool Failover.]]

	In the context of QuantaStor, the "Execute High-Availability (HA) Pool Failover" feature serves a critical purpose in managing and ensuring the availability and reliability of storage resources. High-availability pools are designed to maintain data accessibility and minimize downtime, even in the event of hardware failures or other issues. The specific purpose of executing a high-availability pool failover in QuantaStor includes:		In the context of QuantaStor, the "Execute High-Availability (HA) Pool Failover" feature serves a critical purpose in managing and ensuring the availability and reliability of storage resources. High-availability pools are designed to maintain data accessibility and minimize downtime, even in the event of hardware failures or other issues. The specific purpose of executing a high-availability pool failover in QuantaStor includes:
Line 21:		Line 21:

	'''Navigation:''' Storage Management --> Storage Pools --> Storage Pool HA Resource Group --> Manual Failover ''(toolbar)''		'''Navigation:''' Storage Management --> Storage Pools --> Storage Pool HA Resource Group --> Manual Failover ''(toolbar)''
	~~<br>''or'' <br>~~
	~~'''Navigation:''' Cluster Resource Management --> Storage Pool HA Groups --> Storage Pool HA Resource Group --> Manual Failover ''(toolbar)''~~

Qadmin at 00:51, 7 November 2023

2023-11-07T00:51:25Z

← Older revision		Revision as of 00:51, 7 November 2023
Line 1:		Line 1:
			[[File:Exct HA Failover.jpg\|512px\|thumb\|Execute High-Availability (HA) Pool Failover.]]

	In the context of QuantaStor, the "Execute High-Availability (HA) Pool Failover" feature serves a critical purpose in managing and ensuring the availability and reliability of storage resources. High-availability pools are designed to maintain data accessibility and minimize downtime, even in the event of hardware failures or other issues. The specific purpose of executing a high-availability pool failover in QuantaStor includes:		In the context of QuantaStor, the "Execute High-Availability (HA) Pool Failover" feature serves a critical purpose in managing and ensuring the availability and reliability of storage resources. High-availability pools are designed to maintain data accessibility and minimize downtime, even in the event of hardware failures or other issues. The specific purpose of executing a high-availability pool failover in QuantaStor includes:

Line 21:		Line 23:
	<br>''or'' <br>		<br>''or'' <br>
	'''Navigation:''' Cluster Resource Management --> Storage Pool HA Groups --> Storage Pool HA Resource Group --> Manual Failover ''(toolbar)''		'''Navigation:''' Cluster Resource Management --> Storage Pool HA Groups --> Storage Pool HA Resource Group --> Manual Failover ''(toolbar)''

	~~[[File:Exct HA Failover.jpg\|512px]]~~

Qadmin at 00:49, 7 November 2023

2023-11-07T00:49:19Z

← Older revision		Revision as of 00:49, 7 November 2023
Line 1:		Line 1:
	Execute a manual storage ~~pool Ha~~ Failover. ~~<br>'''Warning~~:'~~'' Availability may be interrupted causing some applications~~ to ~~time out~~.		In the context of QuantaStor, the "Execute High-Availability (HA) Pool Failover" feature serves a critical purpose in managing and ensuring the availability and reliability of storage resources. High-availability pools are designed to maintain data accessibility and minimize downtime, even in the event of hardware failures or other issues. The specific purpose of executing a high-availability pool failover in QuantaStor includes:

			*Redundancy and Fault Tolerance: High-availability pools are configured to ensure redundancy and fault tolerance. If a node within the high-availability pool encounters a failure, such as hardware issues or network problems, initiating a failover ensures that the workload and data previously handled by the failed node are shifted to another healthy node within the pool.

			*Continuity of Service: Executing a failover is a means to maintain continuous access to storage resources for users or applications. By automatically or manually switching the workload to a standby or backup node, the failover process ensures that the services remain available despite a failure.

			*Automatic or Manual Transition: QuantaStor might support both automatic and manual failover modes. Automatic failover instantly switches operations to the redundant node without human intervention, whereas manual failover allows administrators to control when the switch occurs, potentially after investigating the cause of the issue.

			*Minimizing Downtime: The primary objective of the failover process is to minimize downtime. When a failover is executed promptly and efficiently, it reduces the impact of the failure on ongoing operations, preventing or reducing service disruptions.

			*Redirection of Workload: During a failover, the system redirects and balances the workload to the operational nodes in the high-availability pool. This ensures that data access and storage operations continue without interruption, albeit on alternative nodes.

			*Data Integrity and Recovery: Failover procedures in high-availability configurations are typically designed to maintain data integrity and facilitate recovery. These processes help in ensuring that no data is lost or corrupted during the failover event.

			*Monitoring and Alerting: High-availability failovers are often accompanied by monitoring and alert systems. They track the health of nodes and automatically trigger failovers when predetermined thresholds or failure events are detected.

			It's crucial to plan and configure high-availability setups in advance to ensure they function as intended when needed. Understanding how to execute a failover, the impact it might have on services, and how to restore the original state after addressing the issue is essential for administrators managing QuantaStor environments.


	'''Navigation:''' Storage Management --> Storage Pools --> Storage Pool HA Resource Group --> Manual Failover ''(toolbar)''		'''Navigation:''' Storage Management --> Storage Pools --> Storage Pool HA Resource Group --> Manual Failover ''(toolbar)''
Line 5:		Line 22:
	'''Navigation:''' Cluster Resource Management --> Storage Pool HA Groups --> Storage Pool HA Resource Group --> Manual Failover ''(toolbar)''		'''Navigation:''' Cluster Resource Management --> Storage Pool HA Groups --> Storage Pool HA Resource Group --> Manual Failover ''(toolbar)''

	[[File:Exct HA Failover.jpg\|~~412px~~]]		[[File:Exct HA Failover.jpg\|512px]]



	{{Template:ReturnToWebGuide}}		{{Template:ReturnToWebGuide}}
	[[Category:~~QuantaStor5~~]]		[[Category:QuantaStor6]]
	[[Category:WebUI Dialog]]		[[Category:WebUI Dialog]]
	[[Category:Requires Review]]		[[Category:Requires Review]]

Qadmin at 14:58, 5 May 2022

2022-05-05T14:58:15Z

← Older revision		Revision as of 14:58, 5 May 2022
Line 5:		Line 5:
	'''Navigation:''' Cluster Resource Management --> Storage Pool HA Groups --> Storage Pool HA Resource Group --> Manual Failover ''(toolbar)''		'''Navigation:''' Cluster Resource Management --> Storage Pool HA Groups --> Storage Pool HA Resource Group --> Manual Failover ''(toolbar)''

	[[File:Exct HA Failover.jpg\|~~512px~~]]		[[File:Exct HA Failover.jpg\|412px]]

Qadmin: Created page with "Execute a manual storage pool Ha Failover.
'''Warning:''' Availability may be interrupted causing some applications to time out. '''Navigation:''' Storage Management -->..."

2022-05-05T14:57:55Z

Created page with "Execute a manual storage pool Ha Failover. <br>'''Warning:''' Availability may be interrupted causing some applications to time out. '''Navigation:''' Storage Management -->..."

New page

Execute a manual storage pool Ha Failover. <br>'''Warning:''' Availability may be interrupted causing some applications to time out.

'''Navigation:''' Storage Management --> Storage Pools --> Storage Pool HA Resource Group --> Manual Failover ''(toolbar)''
<br>''or'' <br>
'''Navigation:''' Cluster Resource Management --> Storage Pool HA Groups --> Storage Pool HA Resource Group --> Manual Failover ''(toolbar)''

[[File:Exct HA Failover.jpg|512px]]

{{Template:ReturnToWebGuide}}
[[Category:QuantaStor5]]
[[Category:WebUI Dialog]]
[[Category:Requires Review]]