QuantaStor Upgrade Guide - Revision history

Joshua.blake: /* Pre-Upgrade Checklist for Scale-Up */

2025-09-05T07:39:48Z

Pre-Upgrade Checklist for Scale-Up

← Older revision		Revision as of 07:39, 5 September 2025
Line 59:		Line 59:
	== Recommended Distribution Upgrade Method for Scale-Up Systems ==		== Recommended Distribution Upgrade Method for Scale-Up Systems ==

	=== Pre-Upgrade Checklist ~~for Scale-Up~~ ===		=== Pre-Upgrade Checklist ===
	# It is recommended that you schedule a downtime work window, as '''a reboot will be required''' after a distro upgrade.		# It is recommended that you schedule a downtime work window, as '''a reboot will be required''' after a distro upgrade.
	# For more complex upgrades we recommend scheduling time with OSNEXUS support for assistance		# For more complex upgrades we recommend scheduling time with OSNEXUS support for assistance

Joshua.blake: /* Recommended Upgrade Method for Scale-Up Systems */

2025-09-05T07:39:03Z

Recommended Upgrade Method for Scale-Up Systems

← Older revision		Revision as of 07:39, 5 September 2025
Line 57:		Line 57:
	The qstormanager package contains the QuantaStor Manager web management interface and it depends on the qstortomcat package. It depends on qstortomcat as it contains a specially configured version of Apache Tomcat which is installed to /opt/osnexus/quantastor/tomcat. The QuantaStor Manager package brings the Java servlet backend component that runs under Apache Tomcat as well as all the front-end QuantaStor Manager JavaScript that runs in the browser.		The qstormanager package contains the QuantaStor Manager web management interface and it depends on the qstortomcat package. It depends on qstortomcat as it contains a specially configured version of Apache Tomcat which is installed to /opt/osnexus/quantastor/tomcat. The QuantaStor Manager package brings the Java servlet backend component that runs under Apache Tomcat as well as all the front-end QuantaStor Manager JavaScript that runs in the browser.

	== Recommended Upgrade Method for Scale-Up Systems ==		== Recommended Distribution Upgrade Method for Scale-Up Systems ==

	=== Pre-Upgrade Checklist for Scale-Up ===		=== Pre-Upgrade Checklist for Scale-Up ===

Joshua.blake at 07:38, 5 September 2025

2025-09-05T07:38:38Z

← Older revision		Revision as of 07:38, 5 September 2025
Line 56:		Line 56:
	=== qstormanager ===		=== qstormanager ===
	The qstormanager package contains the QuantaStor Manager web management interface and it depends on the qstortomcat package. It depends on qstortomcat as it contains a specially configured version of Apache Tomcat which is installed to /opt/osnexus/quantastor/tomcat. The QuantaStor Manager package brings the Java servlet backend component that runs under Apache Tomcat as well as all the front-end QuantaStor Manager JavaScript that runs in the browser.		The qstormanager package contains the QuantaStor Manager web management interface and it depends on the qstortomcat package. It depends on qstortomcat as it contains a specially configured version of Apache Tomcat which is installed to /opt/osnexus/quantastor/tomcat. The QuantaStor Manager package brings the Java servlet backend component that runs under Apache Tomcat as well as all the front-end QuantaStor Manager JavaScript that runs in the browser.
	~~== Pre-Upgrade Checklist for Scale-Up ==~~

			== Recommended Upgrade Method for Scale-Up Systems ==

			=== Pre-Upgrade Checklist for Scale-Up ===
	# It is recommended that you schedule a downtime work window, as '''a reboot will be required''' after a distro upgrade.		# It is recommended that you schedule a downtime work window, as '''a reboot will be required''' after a distro upgrade.
	# For more complex upgrades we recommend scheduling time with OSNEXUS support for assistance		# For more complex upgrades we recommend scheduling time with OSNEXUS support for assistance
Line 66:		Line 68:
	# For systems running 18.04 Bionic, it is required to upgrade through 20.04 Focal and then to 22.04 Jammy. To avoid any risks during the upgrade, it may be easier to make a backup of the osn.db and other relevant configuration files, and reinstall. OSNEXUS Support will best guide you on this.		# For systems running 18.04 Bionic, it is required to upgrade through 20.04 Focal and then to 22.04 Jammy. To avoid any risks during the upgrade, it may be easier to make a backup of the osn.db and other relevant configuration files, and reinstall. OSNEXUS Support will best guide you on this.

	== Upgrade QuantaStor Version ==		=== Upgrade QuantaStor Version ===
	OSNEXUS recommends that QuantaStor is upgraded to the most recent version with a full upgrade before performing a distribution upgrade. You can do this from the WUI (Web User Interface) using the ‘[[Upgrade Manager]]’ and specifying to include the kernel. A full upgrade, depending on the version you are originating from, may require a reboot. The WUI should inform you if this is the case, but it is generally a good idea to reboot the system anyway, just to ensure it can boot normally. This is good preparation for the distribution upgrade.		OSNEXUS recommends that QuantaStor is upgraded to the most recent version with a full upgrade before performing a distribution upgrade. You can do this from the WUI (Web User Interface) using the ‘[[Upgrade Manager]]’ and specifying to include the kernel. A full upgrade, depending on the version you are originating from, may require a reboot. The WUI should inform you if this is the case, but it is generally a good idea to reboot the system anyway, just to ensure it can boot normally. This is good preparation for the distribution upgrade.

	== Upgrade Ubuntu OS Distribution ==		=== Upgrade Ubuntu OS Distribution ===
	Note: This procedure upgrades the Ubuntu operating system to the next major version and updates QuantaStor to the latest release supported by that version.		Note: This procedure upgrades the Ubuntu operating system to the next major version and updates QuantaStor to the latest release supported by that version.

Joshua.blake at 07:35, 5 September 2025

2025-09-05T07:35:46Z

@@ Line 56: / Line 56: @@
 === qstormanager ===
 The qstormanager package contains the QuantaStor Manager web management interface and it depends on the qstortomcat package.  It depends on qstortomcat as it contains a specially configured version of Apache Tomcat which is installed to /opt/osnexus/quantastor/tomcat.   The QuantaStor Manager package brings the Java servlet backend component that runs under Apache Tomcat as well as all the front-end QuantaStor Manager JavaScript that runs in the browser.
 == Pre-Upgrade Checklist for Scale-Up ==

JP.Lucero at 07:33, 5 September 2025

2025-09-05T07:33:51Z

← Older revision		Revision as of 07:33, 5 September 2025
Line 78:		Line 78:
	apt-get install qstorservice qstormanager qstortomcat qstortarget		apt-get install qstorservice qstormanager qstortomcat qstortarget
	</pre>		</pre>

			== Pre-Upgrade Checklist for Scale-Up ==

			# It is recommended that you schedule a downtime work window, as '''a reboot will be required''' after a distro upgrade.
			# For more complex upgrades we recommend scheduling time with OSNEXUS support for assistance
			# Execute the distribution upgrade within a ‘screen’ session to prevent issues in case of network disconnection.
			# It is advisable to stop clients from using the system, including stopping or pausing virtual machines that are consuming storage volumes presented from QuantaStor.
			# Submit logs from all nodes to Support using the ‘[https://wiki.osnexus.com/index.php?title=Send_Support_Log_Files Send Support Logs]’ option in the WUI.
			# Place the cluster into ‘[https://wiki.osnexus.com/index.php?title=Enter_Site_Cluster_Maintenance_Mode Maintenance Mode]’ to prevent automatic failover during the upgrade.
			# For systems running 18.04 Bionic, it is required to upgrade through 20.04 Focal and then to 22.04 Jammy. To avoid any risks during the upgrade, it may be easier to make a backup of the osn.db and other relevant configuration files, and reinstall. OSNEXUS Support will best guide you on this.

			== Upgrade QuantaStor Version ==
			OSNEXUS recommends that QuantaStor is upgraded to the most recent version with a full upgrade before performing a distribution upgrade. You can do this from the WUI (Web User Interface) using the ‘[[Upgrade Manager]]’ and specifying to include the kernel. A full upgrade, depending on the version you are originating from, may require a reboot. The WUI should inform you if this is the case, but it is generally a good idea to reboot the system anyway, just to ensure it can boot normally. This is good preparation for the distribution upgrade.

			== Upgrade Ubuntu OS Distribution ==
			Note: This procedure upgrades the Ubuntu operating system to the next major version and updates QuantaStor to the latest release supported by that version.

			To upgrade the distribution for QuantaStor Scale-Up systems, follow these steps:

			'''Upgrade from 18.04 Bionic to 20.04 Focal'''

			# Ensure that QuantaStor node is upgraded (including Kernel) to the most recent version using the ‘[[Upgrade Manager]]’
			# Reboot to ensure that the system boots without an issue
			# The site cluster HA (High Availability) between Bionic and Focal is not compatible. Site cluster VIFs must be deleted and migrated to local VIFs, along with deleting the site cluster configuration from all nodes.
			# Ensure you are in a screen session as per the '''Pre-Upgrade Checklist for Scale-Up.'''
			# Log in as root and execute the command '''''qs-distupgrade'''''.
			# If you are not using ‘screen’, then you may be prompted "Do you want to continue without session continuation protection provided by the screen. (y/n) default: no ?", you can '''choose 'y' or 'n'. Please note that your input is taken straight away without pressing the Enter key'''.
			# When asked "Do you want to proceed with the distribution upgrade for the base platform. (y/n) ?", '''type 'y'. Please note that your input is taken straight away without pressing the Enter key.'''
			# When prompted "Do you wish to gather logs (y/n) Default:no ?", '''type 'y'. * Please note that your input is taken straight away without pressing the Enter key.'''
			# Wait for the upgrade process to complete.
			# Reboot the server. Check if the system comes online and is healthy (as confirmed with '''''qs-showlog -f''''' or in /var/log/qs/qs_service.log when the services start), then proceed to upgrade the other system.
			# Repeat steps 1-10 on all nodes within the cluster.
			# Once all systems are upgraded, do not recreate the cluster yet. Continue upgrading to 22.04 Jammy.

			'''Upgrade from 20.04 Focal to 22.04 Jammy'''

			# If you are upgrading from 18.04 Bionic to 20.04 Focal, do not recreate the cluster yet and skip steps 3 and 4. The cluster should only be recreated once all nodes have been upgraded to the latest OS and QuantaStor version. Otherwise, follow the procedure as documented.
			# Ensure you are in a screen session as per the '''Pre-Upgrade Checklist for Scale-Up.'''
			# For HA (High Availability) setup, via the WUI perform a failover of the pool(s) to one system before performing a full upgrade (including reboot).
			# Place the cluster into ‘[https://wiki.osnexus.com/index.php?title=Enter_Site_Cluster_Maintenance_Mode Maintenance Mode]’.
			# Ensure that QuantaStor node is upgraded (including Kernel) to the most recent version using the ‘[https://wiki.osnexus.com/index.php?title=Upgrade_Manager Upgrade Manager]’
			# Log in as root and execute the command '''''qs-distupgrade'''''.
			# If you are not using ‘screen’, then you may be prompted "Do you want to continue without session continuation protection provided by the screen. (y/n) default: no ?", you can '''choose 'y' or 'n'. Please note that your input is taken straight away without pressing the Enter key.'''
			# When asked "Do you want to proceed with the distribution upgrade for the base platform. (y/n) ?", '''type 'y'. Please note that your input is taken straight away without pressing the Enter key.'''
			# When prompted "Do you wish to gather logs (y/n) Default:no ?", '''type 'y'. * Please note that your input is taken straight away without pressing the Enter key.'''
			# Wait for the upgrade process to complete.
			# Reboot the server. Check if the system comes online and is healthy (as confirmed with '''''qs-showlog -f''''' or in /var/log/qs/qs_service.log when the services start), then proceed to upgrade the other system.
			# Repeat steps 2-11 on all nodes within the cluster.


			''* Gathering and submitting logs to OSNexus support will better assist in resolving any encountered issues.''

Qadmin: /* Web Based Upgrade Procedure */

2021-07-09T00:17:00Z

Web Based Upgrade Procedure

← Older revision		Revision as of 00:17, 9 July 2021
Line 4:		Line 4:

	Upgrading QuantaStor to the latest version is made easy using the		Upgrading QuantaStor to the latest version is made easy using the
	[https://wiki.osnexus.com/index.php?title=Storage_System_Upgrade_Manager Storage System Upgrade Manager] that's integrated into the web management interface. Alternatively you can run this command to upgrade your system at the console or via an SSH session:		[https://wiki.osnexus.com/index.php?title=Storage_System_Upgrade_Manager Storage System Upgrade Manager Dialog] that's integrated into the web management interface. Alternatively you can run this command to upgrade your system at the console or via an SSH session:

	== Console Based Upgrade Procedure ==		== Console Based Upgrade Procedure ==

Qadmin: /* Web Based Upgrade Procedure */

2021-07-09T00:16:21Z

Web Based Upgrade Procedure

← Older revision		Revision as of 00:16, 9 July 2021
Line 4:		Line 4:

	Upgrading QuantaStor to the latest version is made easy using the		Upgrading QuantaStor to the latest version is made easy using the
	[https://wiki.osnexus.com/index.php?title=Storage_System_Upgrade_Manager] that's integrated into the web management interface. Alternatively you can run this command to upgrade your system at the console or via an SSH session:		[https://wiki.osnexus.com/index.php?title=Storage_System_Upgrade_Manager Storage System Upgrade Manager] that's integrated into the web management interface. Alternatively you can run this command to upgrade your system at the console or via an SSH session:

	== Console Based Upgrade Procedure ==		== Console Based Upgrade Procedure ==

Qadmin: /* Web Based Upgrade Procedure */

2021-07-09T00:15:39Z

Web Based Upgrade Procedure

← Older revision		Revision as of 00:15, 9 July 2021
Line 4:		Line 4:

	Upgrading QuantaStor to the latest version is made easy using the		Upgrading QuantaStor to the latest version is made easy using the
	[~~http~~://wiki.osnexus.com~~/mediawiki~~/index.php~~/Storage_System_Upgrade_Manager_Dialog Upgrade Manager~~] that's integrated into the web management interface. Alternatively you can run this command to upgrade your system at the console or via an SSH session:		[https://wiki.osnexus.com/index.php?title=Storage_System_Upgrade_Manager] that's integrated into the web management interface. Alternatively you can run this command to upgrade your system at the console or via an SSH session:

	== Console Based Upgrade Procedure ==		== Console Based Upgrade Procedure ==

Qadmin: /* qstorservice */

2019-03-26T18:52:25Z

qstorservice

← Older revision		Revision as of 18:52, 26 March 2019
Line 43:		Line 43:
	The QuantaStor core services package is called qstorservice. It contains the service, database, and all the surrounding components that are required for the storage system to run. You can start and stop the QuantaStor service manually with these following commands respectively:		The QuantaStor core services package is called qstorservice. It contains the service, database, and all the surrounding components that are required for the storage system to run. You can start and stop the QuantaStor service manually with these following commands respectively:
	"sudo service quantastor stop" and		"sudo service quantastor stop" and
	"sudo service quantastor start",\.		"sudo service quantastor start".
	As part of the installation process the QuantaStor service is restarted and while it is starting up you will not have access to login to the storage system via the Web Management interface for about 60 seconds. Starting and stopping the QuantaStor service will in no way interrupt access to you iSCSI disks / storage volumes.		As part of the installation process the QuantaStor service is restarted and while it is starting up you will not have access to login to the storage system via the Web Management interface for about 60 seconds. Starting and stopping the QuantaStor service will in no way interrupt access to you iSCSI disks / storage volumes.

Qadmin: /* qstorservice */

2019-03-26T18:51:59Z

qstorservice

← Older revision		Revision as of 18:51, 26 March 2019
Line 42:		Line 42:
	=== qstorservice ===		=== qstorservice ===
	The QuantaStor core services package is called qstorservice. It contains the service, database, and all the surrounding components that are required for the storage system to run. You can start and stop the QuantaStor service manually with these following commands respectively:		The QuantaStor core services package is called qstorservice. It contains the service, database, and all the surrounding components that are required for the storage system to run. You can start and stop the QuantaStor service manually with these following commands respectively:
	sudo service quantastor stop		"sudo service quantastor stop" and
	sudo service quantastor start		"sudo service quantastor start",\.
	As part of the installation process the QuantaStor service is restarted and while it is starting up you will not have access to login to the storage system via the Web Management interface for about 60 seconds. Starting and stopping the QuantaStor service will in no way interrupt access to you iSCSI disks / storage volumes.		As part of the installation process the QuantaStor service is restarted and while it is starting up you will not have access to login to the storage system via the Web Management interface for about 60 seconds. Starting and stopping the QuantaStor service will in no way interrupt access to you iSCSI disks / storage volumes.

	=== qstortarget ===		=== qstortarget ===
	The QuantaStor iSCSI target is a customized version of the open source SCST driver and includes support for iSCSI, FC, and Infiniband. If you upgrade the target mode driver your system will continue to function normally but your new drivers will not become active until after you reboot. You can manually restart the driver like so:		The QuantaStor iSCSI target is a customized version of the open source SCST driver and includes support for iSCSI, FC, and Infiniband. If you upgrade the target mode driver your system will continue to function normally but your new drivers will not become active until after you reboot. You can manually restart the driver like so: