+ Admin Guide Overview - Revision history

Qadmin: Link the new Clustered SCSI-3 Persistent Reservations page

2026-09-28T16:32:15Z

Link the new Clustered SCSI-3 Persistent Reservations page

← Older revision		Revision as of 16:32, 28 September 2026
Line 66:		Line 66:
	\|-		\|-
	\| [[Storage Volumes]] \|\| Block devices (LUNs) accessed over iSCSI, Fibre Channel or Infiniband/SRP.		\| [[Storage Volumes]] \|\| Block devices (LUNs) accessed over iSCSI, Fibre Channel or Infiniband/SRP.
			\|-
			\| style="padding-left: 2.5em;" \| [[Clustered SCSI-3 Persistent Reservations]] \|\| Sharing client reservations across an HA group so Hyper-V, WSFC and SQL Server clusters survive a failover.
	\|-		\|-
	\| [[Fibre Channel Target Port Management]] \|\| Exposing volumes as LUNs to Fibre Channel initiator hosts alongside iSCSI.		\| [[Fibre Channel Target Port Management]] \|\| Exposing volumes as LUNs to Fibre Channel initiator hosts alongside iSCSI.

Qadmin: Add Multi-protocol File Locking under Storage Provisioning

2026-09-24T03:11:58Z

Add Multi-protocol File Locking under Storage Provisioning

← Older revision		Revision as of 03:11, 24 September 2026
Line 72:		Line 72:
	\|-		\|-
	\| [[NFS Configuration]] \|\| The two NFS server implementations, and which one applies to a given storage architecture.		\| [[NFS Configuration]] \|\| The two NFS server implementations, and which one applies to a given storage architecture.
			\|-
			\| [[Multi-protocol File Locking]] \|\| Locking on shares used by NFS and SMB clients at once, the setting that makes it coherent, and its limits.
	\|-		\|-
	\| [[Cloud Containers / NAS Gateway]] \|\| Mapping an object-storage bucket to a Network Share so it can be accessed as files.		\| [[Cloud Containers / NAS Gateway]] \|\| Mapping an object-storage bucket to a Network Share so it can be accessed as files.

Qadmin: Move Encryption Bypass from Scale-out Cluster Configuration to Security, Alerting & Upgrades - it is a data-at-rest encryption topic that governs scale-up Storage Pool devices as well as scale-out OSDs, and the old placement and description scoped it to Ceph (QSTOR-12352)

2026-09-04T05:59:18Z

Move Encryption Bypass from Scale-out Cluster Configuration to Security, Alerting & Upgrades - it is a data-at-rest encryption topic that governs scale-up Storage Pool devices as well as scale-out OSDs, and the old placement and description scoped it to Ceph (QSTOR-12352)

← Older revision		Revision as of 05:59, 4 September 2026
Line 92:		Line 92:
	\|-		\|-
	\| [[FIPS Mode]] \|\| Running the appliance with the FIPS 140-2 validated cryptographic module, and verifying it is active.		\| [[FIPS Mode]] \|\| Running the appliance with the FIPS 140-2 validated cryptographic module, and verifying it is active.
			\|-
			\| [[Encryption Bypass]] \|\| Why QuantaStor does not encrypt devices that arrays such as Seagate Corvault, Seagate Exos E/EP and Dell PowerVault already encrypt in hardware, and how to add new vendor and model combinations as they are released. Applies to scale-up Storage Pools and scale-out OSDs alike.
	\|}		\|}

Line 138:		Line 140:
	\|-		\|-
	\| [[Scale-out Object Setup (ceph)]] \|\| Scale-out object storage over the S3-compatible REST protocols.		\| [[Scale-out Object Setup (ceph)]] \|\| Scale-out object storage over the S3-compatible REST protocols.
	\|-
	~~\| [[Encryption Bypass]] \|\| Excluding specific devices from Ceph's at-rest encryption.~~
	\|}		\|}

Qadmin: Point at the renamed Encryption Bypass page directly rather than through the redirect - the feature is not Ceph-specific

2026-09-04T05:58:12Z

Point at the renamed Encryption Bypass page directly rather than through the redirect - the feature is not Ceph-specific

← Older revision		Revision as of 05:58, 4 September 2026
Line 139:		Line 139:
	\| [[Scale-out Object Setup (ceph)]] \|\| Scale-out object storage over the S3-compatible REST protocols.		\| [[Scale-out Object Setup (ceph)]] \|\| Scale-out object storage over the S3-compatible REST protocols.
	\|-		\|-
	\| [[~~Ceph~~ Encryption Bypass]] \|\| Excluding specific devices from Ceph's at-rest encryption.		\| [[Encryption Bypass]] \|\| Excluding specific devices from Ceph's at-rest encryption.
	\|}		\|}

Qadmin: Remove the Getting Started row and revert the section lead - Getting Started is its own guide with its own side-menu section, so it is not duplicated here (QSTOR-12352)

2026-09-04T04:29:54Z

Remove the Getting Started row and revert the section lead - Getting Started is its own guide with its own side-menu section, so it is not duplicated here (QSTOR-12352)

← Older revision		Revision as of 04:29, 4 September 2026
Line 6:		Line 6:
	== Using the Web Interface ==		== Using the Web Interface ==

	The web management interface itself: its screen regions, its nine main tabs, the navigation conventions this guide uses to describe it~~, and the built-in setup launcher a new appliance starts from~~.		The web management interface itself: its screen regions, its nine main tabs, and the navigation conventions this guide uses to describe it.

	{\| class="wikitable"		{\| class="wikitable"
Line 12:		Line 12:
	\|-		\|-
	\| [[Using the Web Interface]] \|\| Logging in, every region of the screen, the nine main tabs, toolbar groups and the overflow chevron, right-click menus, and how to read a '''Navigation''' breadcrumb.		\| [[Using the Web Interface]] \|\| Logging in, every region of the screen, the nine main tabs, toolbar groups and the overflow chevron, right-click menus, and how to read a '''Navigation''' breadcrumb.
	\|-
	\| [[+ Getting Started Overview\|Getting Started]] \|\| The built-in Getting Started / Configuration Guide: first-time login, the twelve setup workflows in their four groups, what each achieves and in what order, and the page that documents every step.
	\|}		\|}

Qadmin: Add a Getting Started entry - the guide had no link to the Getting Started Overview at all, which is now rewritten around the twelve workflows of the built-in configuration guide (QSTOR-12352)

2026-09-04T03:49:30Z

Add a Getting Started entry - the guide had no link to the Getting Started Overview at all, which is now rewritten around the twelve workflows of the built-in configuration guide (QSTOR-12352)

← Older revision		Revision as of 03:49, 4 September 2026
Line 6:		Line 6:
	== Using the Web Interface ==		== Using the Web Interface ==

	The web management interface itself: its screen regions, its nine main tabs, ~~and~~ the navigation conventions this guide uses to describe it.		The web management interface itself: its screen regions, its nine main tabs, the navigation conventions this guide uses to describe it, and the built-in setup launcher a new appliance starts from.

	{\| class="wikitable"		{\| class="wikitable"
Line 12:		Line 12:
	\|-		\|-
	\| [[Using the Web Interface]] \|\| Logging in, every region of the screen, the nine main tabs, toolbar groups and the overflow chevron, right-click menus, and how to read a '''Navigation''' breadcrumb.		\| [[Using the Web Interface]] \|\| Logging in, every region of the screen, the nine main tabs, toolbar groups and the overflow chevron, right-click menus, and how to read a '''Navigation''' breadcrumb.
			\|-
			\| [[+ Getting Started Overview\|Getting Started]] \|\| The built-in Getting Started / Configuration Guide: first-time login, the twelve setup workflows in their four groups, what each achieves and in what order, and the page that documents every step.
	\|}		\|}

Qadmin: Correct the Configure Member Standby description - standby evacuates the node and stops it receiving resources; the previous wording said the cluster could fail over TO it, which is backwards

2026-09-04T00:34:59Z

Correct the Configure Member Standby description - standby evacuates the node and stops it receiving resources; the previous wording said the cluster could fail over TO it, which is backwards

← Older revision		Revision as of 00:34, 4 September 2026
Line 107:		Line 107:
	\| [[Cluster VIFs]] \|\| Adding a cluster virtual interface and choosing its use case -- grid primary, scale-up storage pool, scale-out storage pool -- and what each type follows.		\| [[Cluster VIFs]] \|\| Adding a cluster virtual interface and choosing its use case -- grid primary, scale-up storage pool, scale-out storage pool -- and what each type follows.
	\|-		\|-
	\| [[Configure Member Standby]] \|\| ~~Taking one~~ node ~~out~~ of ~~service per-node,~~ while the ~~rest of the cluster keeps operating and can fail over to it~~.		\| [[Configure Member Standby]] \|\| Setting a node into standby moves all VIF resources and pools off it, so maintenance can be done without risk of a pool or resource moving onto it while the work is in progress.
	\|}		\|}

Qadmin: Rename the Site Clusters section to High-availability VIF Management, matching the WUI main tab, and populate it: link the existing High-availability VIF Management page (which was not referenced from the overview at all) and add entries for the two pages now being written - Site Cluster Setup and Cluster VIFs (QSTOR-12352)

2026-09-04T00:00:57Z

Rename the Site Clusters section to High-availability VIF Management, matching the WUI main tab, and populate it: link the existing High-availability VIF Management page (which was not referenced from the overview at all) and add entries for the two pages now being written - Site Cluster Setup and Cluster VIFs (QSTOR-12352)

← Older revision		Revision as of 00:00, 4 September 2026
Line 94:		Line 94:
	\|}		\|}

	== ~~Site Clusters & Cluster~~ VIF Management ==		== High-availability VIF Management ==

	~~Configuring~~ cluster heartbeat ~~mechanism~~ for ~~cluster VIF management in~~ scale-out (Ceph) and scale-up (ZFS) storage clusters within a grid.		The cluster heartbeat layer and the floating service addresses it manages, for both scale-out (Ceph) and scale-up (ZFS) storage clusters within a grid. Named for the main tab these are managed from.

	{\| class="wikitable"		{\| class="wikitable"
	! Topic !! Description		! Topic !! Description
			\|-
			\| [[High-availability VIF Management]] \|\| How cluster VIFs work: the grid, site cluster, heartbeat ring, HA group and VIF hierarchy, what triggers a failover and how long one takes, what blocks one, moving a VIF deliberately, and location constraints.
			\|-
			\| [[Site Cluster Setup]] \|\| Creating a site cluster and its heartbeat rings, adding and removing members, and the corosync and pacemaker configuration it puts in place.
			\|-
			\| [[Cluster VIFs]] \|\| Adding a cluster virtual interface and choosing its use case -- grid primary, scale-up storage pool, scale-out storage pool -- and what each type follows.
	\|-		\|-
	\| [[Configure Member Standby]] \|\| Taking one node out of service per-node, while the rest of the cluster keeps operating and can fail over to it.		\| [[Configure Member Standby]] \|\| Taking one node out of service per-node, while the rest of the cluster keeps operating and can fail over to it.

Qadmin: /* Cluster Configuration */

2026-09-03T23:43:14Z

Cluster Configuration

← Older revision		Revision as of 23:43, 3 September 2026
Line 120:		Line 120:
	\|}		\|}

	== Cluster Configuration ==		== Scale-out Cluster Configuration ==

	~~Highly available scale-up pools, and the scale~~-out Ceph ~~configurations~~.		Scale-out Ceph cluster setup and configuration.

	{\| class="wikitable"		{\| class="wikitable"
	! Topic !! Description		! Topic !! Description
	\|-
	~~\| [[HA Cluster Setup (JBODs)]] \|\| Clustered pools on shared SAS JBODs, so a node or path outage does not take storage offline.~~
	\|-
	~~\| [[HA Cluster Setup (external SAN)]] \|\| The same clustered pool configuration where the media comes from an external SAN.~~
	\|-		\|-
	\| [[Scale-out Block Setup (ceph)]] \|\| Scale-out SAN built on Ceph.		\| [[Scale-out Block Setup (ceph)]] \|\| Scale-out SAN built on Ceph.
Line 138:		Line 134:
	\|-		\|-
	\| [[Ceph Encryption Bypass]] \|\| Excluding specific devices from Ceph's at-rest encryption.		\| [[Ceph Encryption Bypass]] \|\| Excluding specific devices from Ceph's at-rest encryption.
			\|}

			== Scale-up Cluster Configuration ==

			Highly available scale-up pool cluster configuration.

			{\| class="wikitable"
			! Topic !! Description
			\|-
			\| [[HA Cluster Setup (JBODs)]] \|\| Clustered pools on shared SAS JBODs, so a node or path outage does not take storage offline.
			\|-
			\| [[HA Cluster Setup (external SAN)]] \|\| The same clustered pool configuration where the media comes from an external SAN.
	\|}		\|}

Qadmin: /* Security, Alerting & Upgrades */

2026-09-03T23:41:01Z

Security, Alerting & Upgrades

← Older revision		Revision as of 23:41, 3 September 2026
Line 93:		Line 93:
	\| [[FIPS Mode]] \|\| Running the appliance with the FIPS 140-2 validated cryptographic module, and verifying it is active.		\| [[FIPS Mode]] \|\| Running the appliance with the FIPS 140-2 validated cryptographic module, and verifying it is active.
	\|}		\|}


	== Site Clusters & Cluster VIF Management ==		== Site Clusters & Cluster VIF Management ==