Storage Groups - Revision history

Digimer: /* Adding DR Host VGs to a SG */

2025-04-08T17:00:45Z

Adding DR Host VGs to a SG

← Older revision		Revision as of 17:00, 8 April 2025
Line 339:		Line 339:
	=== Adding DR Host VGs to a SG ===		=== Adding DR Host VGs to a SG ===

	One of the other common needs to manually manage storage groups is for setting up DR hosts.		One of the other common needs to manually manage storage groups is for setting up [[DR hosts]].

			For this, the DR host needs to be linked to this node, then one of the DR host's VGs need to be added to this node's storage group.

			The reason for this is; When a server is to be protected on a DR host, storage on the DR host needs to be allocated. Having the DR's VG in the same SG and the server uses allows the program to know where to allocate the server's storage.

			Examples are found here;

			* [[Disaster Recovery Tasks]]

Digimer: /* Using anvil-manage-storage-groups */

2025-04-08T16:51:54Z

Using anvil-manage-storage-groups

@@ Line 244: / Line 244: @@
   - [an-a01n02_vg0], size: [248.41 GiB], free: [152.68 GiB], internal UUID: [LG8Wib-poB1-ygyo-fVUj-yTks-Mpq4-4qs057]
 </syntaxhighlight>
 Here we see two [[VG]]s, but no storage groups. So lets manually create <span class="code">Storage Group 1</span>.
@@ Line 300: / Line 302: @@
 </syntaxhighlight>
-This happened because the sizes of both VGs are very close (within 1 [GiB]).
+This happened because the sizes of both VGs are very close (within 1 [[GiB]]).
 <span class="code"></span>

Digimer at 05:00, 8 April 2025

2025-04-08T05:00:13Z

← Older revision		Revision as of 05:00, 8 April 2025
Line 187:		Line 187:

	The Anvil! ensures that write ordering is maintained across disks to make sure this never happens.		The Anvil! ensures that write ordering is maintained across disks to make sure this never happens.

			= Working With Storage Groups =

			In most systems, the "<span class="code">Storage Group 1</span>" will be auto-assembled during node setup. If you have additional [[VG]]s, or for some reason the auto-assembly doesn't work, you can manage SGs manaually.

			== Using Striker ==


			== Using anvil-manage-storage-groups ==

			The command line tool <span class="code">[[anvil-manage-storage-groups]]</span> allows for management of SGs from the command line.

			=== Showing Storage Info ===

			First, lets see all the information;

			<syntaxhighlight lang="bash">
			anvil-manage-storage-groups --show --dr
			</syntaxhighlight>
			<syntaxhighlight lang="text">
			Anvil Node: [an-anvil-01] - Demo VM Anvil! Node 1
			- Subnode: [an-a01n01] volume groups;
			- [an-a01n01_vg0], size: [248.41 GiB], free: [152.68 GiB], internal UUID: [m3Qkdi-ts8I-ZOwG-Dw41-117f-X0fz-g8gI1f]
			- Subnode: [an-a01n02] volume groups;
			- [an-a01n02_vg0], size: [248.41 GiB], free: [152.68 GiB], internal UUID: [LG8Wib-poB1-ygyo-fVUj-yTks-Mpq4-4qs057]

			Anvil Node: [an-anvil-02] - Demo VM Anvil! Node 2
			- Subnode: [an-a02n01] volume groups;
			- [an-a02n01_vg0], size: [248.41 GiB], free: [50.54 GiB], internal UUID: [6Hcf5w-rzEz-rFO9-O7fe-eXUV-j82L-P1h5FW]
			- Subnode: [an-a02n02] volume groups;
			- [an-a02n02_vg0], size: [248.41 GiB], free: [50.54 GiB], internal UUID: [DDupu5-xg3R-0P5V-EEAf-ERpv-CaM7-IaoWyB]

			Anvil Node: [an-anvil-03] - Demo VM Anvil! Node 3
			- Subnode: [an-a03n01] volume groups;
			- [an-a03n01_vg0], size: [249.00 GiB], free: [147.20 GiB], internal UUID: [19Sd1Q-HA8B-Z7iy-PsEM-NzgV-t7xb-zvJm5M]
			- Subnode: [an-a03n02] volume groups;
			- [an-a03n02_vg0], size: [249.00 GiB], free: [147.20 GiB], internal UUID: [10GAjf-E2yA-81kr-d1sV-JerO-Fbbn-ZwtDgV]

			Disaster Recovery Hosts:
			- DR Host: [an-a01dr01] VGs:
			- [an-a01dr01], size: [77.88 GiB], free: [4.00 MiB], internal UUID: [BlabZw-Q4Ji-a208-LeFR-CIns-w4Ee-nqJCrJ]
			- DR Host: [an-a03dr01] VGs:
			- [an-a03dr01], size: [81.80 GiB], free: [4.00 MiB], internal UUID: [Nn4LOd-Mb3P-4cs0-GaVS-AClk-gVsy-U1FxI7]
			</syntaxhighlight>

			Here we see three nodes and two DR hosts. For now, lets simplify and just look at <span class="code">an-anvil-01</span>.

			<syntaxhighlight lang="bash">
			anvil-manage-storage-groups --show --anvil an-anvil-01
			</syntaxhighlight>
			<syntaxhighlight lang="text">
			Anvil Node: [an-anvil-01] - Demo VM Anvil! Node 1
			- Subnode: [an-a01n01] volume groups;
			- [an-a01n01_vg0], size: [248.41 GiB], free: [152.68 GiB], internal UUID: [m3Qkdi-ts8I-ZOwG-Dw41-117f-X0fz-g8gI1f]
			- Subnode: [an-a01n02] volume groups;
			- [an-a01n02_vg0], size: [248.41 GiB], free: [152.68 GiB], internal UUID: [LG8Wib-poB1-ygyo-fVUj-yTks-Mpq4-4qs057]
			</syntaxhighlight>

			Here we see two [[VG]]s, but no storage groups. So lets manually create <span class="code">Storage Group 1</span>.

			<syntaxhighlight lang="bash">
			anvil-manage-storage-groups --anvil an-anvil-01 --add --group "Storage Group 1"
			</syntaxhighlight>
			<syntaxhighlight lang="text">
			The storage group: [Storage Group 1] on the Anvil! node: [an-anvil-01] has been created with the UUID: [a92f4dde-de77-48b3-ae86-e6e8af80e3ad].
			</syntaxhighlight>

			Now we can check to see that the group exists now.

			<syntaxhighlight lang="bash">
			anvil-manage-storage-groups --show --anvil an-anvil-01
			</syntaxhighlight>
			<syntaxhighlight lang="text">
			Anvil Node: [an-anvil-01] - Demo VM Anvil! Node 1
			- Subnode: [an-a01n01] volume groups;
			- [an-a01n01_vg0], size: [248.41 GiB], free: [152.68 GiB], internal UUID: [m3Qkdi-ts8I-ZOwG-Dw41-117f-X0fz-g8gI1f]
			- Subnode: [an-a01n02] volume groups;
			- [an-a01n02_vg0], size: [248.41 GiB], free: [152.68 GiB], internal UUID: [LG8Wib-poB1-ygyo-fVUj-yTks-Mpq4-4qs057]
			- Storage group: [Storage Group 1], UUID: [a92f4dde-de77-48b3-ae86-e6e8af80e3ad]
			- <no members in this storage group yet>
			</syntaxhighlight>

			The group now exists, but there are no members to the group yet. So lets add the subnode <span class="code">an-a01n01</span>'s VG <span class="code">an-a01n01_vg0</span>. To do this, we'll use the internal UUID <span class="code">m3Qkdi-ts8I-ZOwG-Dw41-117f-X0fz-g8gI1f</span>.

			<syntaxhighlight lang="bash">
			anvil-manage-storage-groups --anvil an-anvil-01 --add --group "Storage Group 1" --member m3Qkdi-ts8I-ZOwG-Dw41-117f-X0fz-g8gI1f
			</syntaxhighlight>
			<syntaxhighlight lang="text">
			Added the volume group: [an-a01n01_vg0] on the host: [an-a01n01] to the storage group: [Storage Group 1]. The new member UUID is: [04a08c72-ded9-4394-a31b-12e714ebf42a].
			</syntaxhighlight>

			Now verify it's added;

			<syntaxhighlight lang="bash">
			anvil-manage-storage-groups --show --anvil an-anvil-01
			</syntaxhighlight>
			<syntaxhighlight lang="text">
			Anvil Node: [an-anvil-01] - Demo VM Anvil! Node 1
			- Subnode: [an-a01n01] volume groups;
			- [an-a01n01_vg0], size: [248.41 GiB], free: [152.68 GiB], internal UUID: [m3Qkdi-ts8I-ZOwG-Dw41-117f-X0fz-g8gI1f]
			- Subnode: [an-a01n02] volume groups;
			- [an-a01n02_vg0], size: [248.41 GiB], free: [152.68 GiB], internal UUID: [LG8Wib-poB1-ygyo-fVUj-yTks-Mpq4-4qs057]
			- Storage group: [Storage Group 1], UUID: [a92f4dde-de77-48b3-ae86-e6e8af80e3ad]
			- [an-a01n01]:[an-a01n01_vg0]
			- [an-a01n02]:[an-a01n02_vg0]
			</syntaxhighlight>

			Oh hey, look at this! See how <span class="code">[an-a01n02]:[an-a01n02_vg0]</span> was also added? If we look in the logs;

			<syntaxhighlight lang="text">
			2025/04/08 00:55:06:[27727]:Database.pm:6762; [ Note ] - The Anvil!: [an-anvil-01]'s storage group: [Storage Group 1] didn't have an entry for the host: [an-a01n02.alteeve.com]. The volume group: [LG8Wib-poB1-ygyo-fVUj-yTks-Mpq4-4qs057] is a close fit and not in another storage group, so adding it to this storage group now.
			</syntaxhighlight>

			This happened because the sizes of both VGs are very close (within 1 [GiB]).

			<span class="code"></span>
			<syntaxhighlight lang="bash">
			</syntaxhighlight>
			<syntaxhighlight lang="text">
			</syntaxhighlight>

	{{footer}}		{{footer}}

Digimer at 06:33, 19 September 2024

2024-09-19T06:33:01Z

@@ Line 27: / Line 27: @@
 !Subnode
 !Physical Volume
 !Volume Group
 !Type
@@ Line 32: / Line 33: @@
 |class="code"|an-a01n01
 |class="code"|/dev/sda3
 |class="code"|an-a01n01_vg0
 |rowspan="2"|Bulk storage, slow drives. The subnode's OS is installed on this array.
@@ Line 37: / Line 39: @@
 |class="code"|an-a01n02
 |class="code"|/dev/sda3
 |class="code"|an-a01n02_vg0
 |}
@@ Line 47: / Line 50: @@
 !Subnode
 !Physical Volume
 !Volume Group
 !Type
@@ Line 52: / Line 56: @@
 |class="code"|an-a01n01
 |class="code"|/dev/sdb1
 |class="code"|an-a01n01_vg1
 |rowspan="2"|Smaller but faster drives, reserved for specific guest servers with high speed storage requirements.
@@ Line 57: / Line 62: @@
 |class="code"|an-a01n02
 |class="code"|/dev/sdb1
 |class="code"|an-a01n02_vg1
 |}
@@ Line 90: / Line 96: @@
 = Storage Groups; Linking VGs =
-<span class="code"></span>
+{{note|1=The Anvil! tries to auto-form storage groups by matching VG sizes. There is no requirement to name volume groups in any specific way, so we can't use the VG names as a reliable way to form storage groups, so size is the only way we can guess which belong together.}}
 {{footer}}

Digimer: Created page with "{{howto_header}} In an Anvil! cluster, a "''storage group''" is a logical group of LVM Volume Groups. When a server is created, the selected storage group tells the cluster where to pull the physical storage from to create the server's virtual hard drive. Most Anvil! nodes have only one VG per subnode and they are generally the same size. As such, the Anvil! is able to automatically link them into a storage group automatically. = Multi-VG Example = Consider a..."

2024-09-19T06:05:29Z

Created page with "{{howto_header}} In an Anvil! cluster, a "''storage group''" is a logical group of LVM Volume Groups. When a server is created, the selected storage group tells the cluster where to pull the physical storage from to create the server's virtual hard drive. Most Anvil! nodes have only one VG per subnode and they are generally the same size. As such, the Anvil! is able to automatically link them into a storage group automatically. = Multi-VG Example = Consider a..."

Páàjì titun

{{howto_header}}

In an Anvil! cluster, a "''storage group''" is a logical group of [[LVM]] [[Volume Groups]]. When a server is created, the selected storage group tells the cluster where to pull the physical storage from to create the server's virtual hard drive. Most Anvil! nodes have only one VG per subnode and they are generally the same size. As such, the Anvil! is able to automatically link them into a storage group automatically.

= Multi-VG Example =

Consider a more complex storage configuration, however.

Lets use the example of subnodes with two RAID arrays; The first is made of high speed flash drives, and the second made up of lower speed bulk storage drives. In this case, there will be two storage devices on the nodes;

{| class="wikitable" style="margin:auto"
!Block Device
!Purpose
|-
|class="code"|/dev/sda
|Bulk storage, slow drives. The subnode's OS is installed on this array.
|-
|class="code"|/dev/sdb
|Smaller but faster drives, reserved for specific guest servers with high speed storage requirements.
|}

During the OS installation stage, /dev/sda3 is used as the [[LVM]] physical volume, or "PV".

{| class="wikitable" style="margin:auto"
|+ Node: an-anvil-01
|-
!Subnode
!Physical Volume
!Volume Group
!Type
|-
|class="code"|an-a01n01
|class="code"|/dev/sda3
|class="code"|an-a01n01_vg0
|rowspan="2"|Bulk storage, slow drives. The subnode's OS is installed on this array.
|-
|class="code"|an-a01n02
|class="code"|/dev/sda3
|class="code"|an-a01n02_vg0
|}

After the OS is installed, the /dev/sdb1 partition is used as the PV and used to back a second VG;

{| class="wikitable" style="margin:auto"
|+ Node: an-anvil-01
|-
!Subnode
!Physical Volume
!Volume Group
!Type
|-
|class="code"|an-a01n01
|class="code"|/dev/sdb1
|class="code"|an-a01n01_vg1
|rowspan="2"|Smaller but faster drives, reserved for specific guest servers with high speed storage requirements.
|-
|class="code"|an-a01n02
|class="code"|/dev/sdb1
|class="code"|an-a01n02_vg1
|}

= Virtual Hard Drives =

When a server is created, a virtual hard drive is created to back the storage of that server. Behind the scenes though, an LVM [[logical volume]] is created on each subnode, and those are used to back the replicates storage device.

Consider an example server we'll call 'srv01-database'. This looks like this

{| class="wikitable" style="margin:auto"
|+ Server: srv01-database on an-a01n01.
|-
!Subnode
!Volume Group
!Logical Volume
!Replicated Volume
|-
|class="code"|an-a01n01
|class="code"|an-a01n01_vg0
|class="code"|/dev/an-a01n01_vg0/srv01-database_0
|rowspan="2"|/dev/drbd/by-res/srv01-database/0
|-
|class="code"|an-a01n02
|class="code"|an-a01n02_vg0
|class="code"|/dev/an-a01n02_vg0/srv01-database_0
|}

At this point, you might be asking yourself; "How did the new server decide to use the bulk storage array? What if I wanted to use the high speed storage?".

This is where Storage Groups come in to play!

= Storage Groups; Linking VGs =



{{footer}}