Managing Storage Groups - Revision history

Digimer: /* Renaming Storage Groups */

2023-11-16T17:18:42Z

Renaming Storage Groups

← Older revision		Revision as of 17:18, 16 November 2023
Line 110:		Line 110:
	- [an-a01n02]:[cs_mk-a07n02_hdd1]		- [an-a01n02]:[cs_mk-a07n02_hdd1]

	<snip>		<...snip...>
	</syntaxhighlight>		</syntaxhighlight>

Digimer: /* Adding a Volume Group to a Storage Group */

2023-11-16T17:18:24Z

Adding a Volume Group to a Storage Group

← Older revision		Revision as of 17:18, 16 November 2023
Line 151:		Line 151:
	- [an-a01n02]:[cs_mk-a07n02_hdd1]		- [an-a01n02]:[cs_mk-a07n02_hdd1]

	<snip>		<...snip...>
	</syntaxhighlight>		</syntaxhighlight>

Digimer: /* Renaming Storage Groups */

2023-11-16T01:34:51Z

Renaming Storage Groups

← Older revision		Revision as of 01:34, 16 November 2023
Line 115:		Line 115:
	Excellent!		Excellent!

			= Adding a Volume Group to a Storage Group =

			In this example, the <span class="code">an-a01dr01</span> [[DR host]] needs to have it's volume group <span class="code">rhel_an-a01dr01</span> joined to <span class="code">HDD-Backed Storage</span> storage group. This is not uncommon when a DR host has different hardware or storage from the nodes. We need to do this before we can

			Context;

			* [[Disaster Recovery Tasks]]

			<syntaxhighlight lang="bash">
			anvil-manage-storage-groups --add --group "HDD-Backed Storage" --member kqFk0c-3QDz-nM8c-jWlB-byuN-6A4G-hOuoHS --anvil an-anvil-01
			</syntaxhighlight>
			<syntaxhighlight lang="text">
			Added the volume group: [rhel_an-a01dr01] on the host: [an-a01dr01] to the storage group: [HDD-Backed Storage]. The new member UUID is: [0aea3507-d1e6-4839-8412-ef46f7fb19f6].
			</syntaxhighlight>

			Now we can confirm;

			<syntaxhighlight lang="bash">
			anvil-manage-storage-groups --show
			</syntaxhighlight>
			<syntaxhighlight lang="text">
			Anvil Node: [an-anvil-01] - Demonstration anvil node
			- Subnode: [an-a01n01] volume groups;
			- [cs_mk-a07n01_hdd1], size: [3.82 TiB], free: [3.72 TiB], internal UUID: [FZDBL7-XSpK-KZ5E-JRwF-U1yH-7RrV-T2jioq]
			- [rhel_an-a01n01], size: [277.87 GiB], free: [203.87 GiB], internal UUID: [uYRAK8-Czf0-jUQ1-4ilh-Axj8-TlLO-3SO2kp]
			- Subnode: [an-a01n02] volume groups;
			- [cs_mk-a07n02_hdd1], size: [3.82 TiB], free: [3.72 TiB], internal UUID: [NyFHtO-zAoK-H6Cd-1v2B-AGT7-54j1-pUfOBM]
			- [rhel_an-a01n01], size: [277.87 GiB], free: [203.87 GiB], internal UUID: [NeV8y4-9DZQ-vau0-iIE8-A1AQ-qJX3-bjsOIV]
			- Storage group: [Fast Storage], UUID: [d12658d3-e0ae-40c1-b2db-11126a2eaf04]
			- [an-a01n01]:[rhel_an-a01n01]
			- [an-a01n02]:[rhel_an-a01n01]
			- Storage group: [HDD-Backed Storage], UUID: [4c57dba7-bdb0-4244-8655-8d7aaa93255e]
			- [an-a01dr01]:[rhel_an-a01dr01]
			- [an-a01n01]:[cs_mk-a07n01_hdd1]
			- [an-a01n02]:[cs_mk-a07n02_hdd1]

			<snip>
			</syntaxhighlight>

	~~In this example, the <span class="code">an-a01dr01</span> [[DR host]] needs to have it's volume group joined to <span class="code"></span>~~

	<span class="code"></span>		<span class="code"></span>

Digimer at 18:59, 15 November 2023

2023-11-15T18:59:15Z

@@ Line 8: / Line 8: @@
 Generally speaking, the Anvil! tries to auto-assemble storage groups for you. When all the hardware is the same size, this works pretty well. However, if the [[volume group]]s on two subnodes, or on a DR host differ, this may not work. In such cases, you can manually configure storage groups using the <span class="code">anvil-manage-storage-group</span> tool.
 To start, lets look at the storage groups on an example Anvil! cluster with three nodes and a DR host.
@@ Line 15: / Line 17: @@
 </syntaxhighlight>
 <syntaxhighlight lang="text">
 </syntaxhighlight>
 <span class="code"></span>

Digimer at 04:34, 15 November 2023

2023-11-15T04:34:22Z

← Older revision		Revision as of 04:34, 15 November 2023
Line 1:		Line 1:
	{{howto_header}}		{{howto_header}}

			{{note\|1=There are plans to add storage group management to the Striker UI. Until then, this is a command-line process.}}

	If you're unfamiliar with what a storage group is, see:		If you're unfamiliar with what a storage group is, see:
Line 7:		Line 9:
	Generally speaking, the Anvil! tries to auto-assemble storage groups for you. When all the hardware is the same size, this works pretty well. However, if the [[volume group]]s on two subnodes, or on a DR host differ, this may not work. In such cases, you can manually configure storage groups using the <span class="code">anvil-manage-storage-group</span> tool.		Generally speaking, the Anvil! tries to auto-assemble storage groups for you. When all the hardware is the same size, this works pretty well. However, if the [[volume group]]s on two subnodes, or on a DR host differ, this may not work. In such cases, you can manually configure storage groups using the <span class="code">anvil-manage-storage-group</span> tool.

	~~{{note\|1~~=~~There are plans to add~~ storage ~~group management to the Striker UI. Until then, this is a command~~-~~line process.~~		To start, lets look at the storage groups on an example Anvil! cluster with three nodes and a DR host.

			<syntaxhighlight lang="bash">
			anvil-manage-storage-groups --show
			</syntaxhighlight>
			<syntaxhighlight lang="text">
			</syntaxhighlight>

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

	{{footer}}		{{footer}}

Digimer: Created page with "{{howto_header}} If you're unfamiliar with what a storage group is, see: * Storage Group Generally speaking, the Anvil! tries to auto-assemble storage groups for you. When all the hardware is the same size, this works pretty well. However, if the volume groups on two subnodes, or on a DR host differ, this may not work. In such cases, you can manually configure storage groups using the anvil-manage-storage-group tool. {{note|1=There a..."

2023-11-15T03:49:06Z

Created page with "{{howto_header}} If you're unfamiliar with what a storage group is, see: * Storage Group Generally speaking, the Anvil! tries to auto-assemble storage groups for you. When all the hardware is the same size, this works pretty well. However, if the volume groups on two subnodes, or on a DR host differ, this may not work. In such cases, you can manually configure storage groups using the anvil-manage-storage-group tool. {{note|1=There a..."

Páàjì titun

{{howto_header}}

If you're unfamiliar with what a storage group is, see:

* [[Storage Group]]

Generally speaking, the Anvil! tries to auto-assemble storage groups for you. When all the hardware is the same size, this works pretty well. However, if the [[volume group]]s on two subnodes, or on a DR host differ, this may not work. In such cases, you can manually configure storage groups using the anvil-manage-storage-group tool.

{{note|1=There are plans to add storage group management to the Striker UI. Until then, this is a command-line process.



{{footer}}