Windows:2016 - Revision history

Matth: /* Managing your S2D cluster! */

2017-02-08T11:49:29Z

Managing your S2D cluster!

Matth: /* Testing S2D with VMFleet */

2017-02-08T10:59:42Z

Testing S2D with VMFleet

Matth at 10:48, 8 February 2017

2017-02-08T10:48:55Z

Matth: /* Extending volumes in size */

2017-02-02T17:35:24Z

Extending volumes in size

Matth: /* Managing your S2D cluster! */

2017-02-02T17:33:20Z

Managing your S2D cluster!

Matth: /* Finding Drive firmware versions and updating firmware versions as required */

2017-02-02T17:28:55Z

Finding Drive firmware versions and updating firmware versions as required

Matth: /* Finding Drive firmware versions and updating firmware versions as required */

2017-02-02T17:28:02Z

Finding Drive firmware versions and updating firmware versions as required

Matth: /* */

2017-02-02T17:15:36Z

Matth: /* Managing your S2D cluster! */

2017-02-02T17:08:16Z

Managing your S2D cluster!

Matth at 16:59, 2 February 2017

2017-02-02T16:59:18Z

← Older revision		Revision as of 11:49, 8 February 2017
Line 139:		Line 139:

	=== Managing your S2D cluster! ===		=== Managing your S2D cluster! ===
		+
		+	==== Ellativing your user privilege ====
		+
		+	I found when running some of the following commands that local admin was not enough and the powershell window needed to have the same access rights
		+	as my Domain administrator login (in my example this was win16.local\mh).
		+
		+	I achieved this with:
		+	<syntaxhighlight>
		+	Start-Process powershell.exe -Credential “win16.local\mh” -NoNewWindow -ArgumentList “Start-Process powershell.exe -Verb runAs”
		+	</syntaxhighlight>
		+
		+	When you run the above command (you credential should be whatever you AD administrator login is), it should generate a popup box for you to type in
		+	your password. Once you have done this, it should re open your powershell window (it will still stated "administrator: windows powershell" at the top) but you will now have the same rights as your credentials stated. in my case "win16.local\mh" which is my domain administrator user name.
		+
		+	https://blogs.technet.microsoft.com/benshy/2012/06/04/using-a-powershell-script-to-run-as-a-different-user-elevate-the-process/

	==== Adding Nodes ====		==== Adding Nodes ====

@@ Line 196: / Line 196: @@
 === Testing S2D with VMFleet ===
 https://blogs.technet.microsoft.com/larryexchange/2016/08/17/leverage-vm-fleet-testing-the-performance-of-storage-space-direct/
 https://blogs.technet.microsoft.com/larryexchange/2016/09/11/the-power-of-rdma-in-storage-space-direct-2/

← Older revision		Revision as of 10:48, 8 February 2017
Line 194:		Line 194:

	Look: https://technet.microsoft.com/en-us/windows-server-docs/storage/storage-spaces/resize-volumes		Look: https://technet.microsoft.com/en-us/windows-server-docs/storage/storage-spaces/resize-volumes
		+
		+	=== Testing S2D with VMFleet ===
		+
		+	https://blogs.technet.microsoft.com/larryexchange/2016/08/17/leverage-vm-fleet-testing-the-performance-of-storage-space-direct/
		+
		+	https://blogs.technet.microsoft.com/larryexchange/2016/09/11/the-power-of-rdma-in-storage-space-direct-2/

← Older revision		Revision as of 17:35, 2 February 2017
Line 188:		Line 188:

	==== Extending volumes in size ====		==== Extending volumes in size ====
		+
		+	Make sure you have the capacity in your storage pool that the volume you wish to extend sits in.
		+
		+	You cannot make a volume bigger in capacity than the availability capacity of the parent pool.

	Look: https://technet.microsoft.com/en-us/windows-server-docs/storage/storage-spaces/resize-volumes		Look: https://technet.microsoft.com/en-us/windows-server-docs/storage/storage-spaces/resize-volumes

← Older revision		Revision as of 17:33, 2 February 2017
Line 187:		Line 187:
	https://technet.microsoft.com/en-us/windows-server-docs/storage/update-firmware		https://technet.microsoft.com/en-us/windows-server-docs/storage/update-firmware

−	==== ====	+	==== Extending volumes in size ====
		+
		+	Look: https://technet.microsoft.com/en-us/windows-server-docs/storage/storage-spaces/resize-volumes

@@ Line 182: / Line 182: @@
 Update-StorageFirmware -ImagePath C:\Firmware\J3E160@3.enc -SlotNumber 0
 </syntaxhighlight>
 ====  ====

@@ Line 177: / Line 177: @@
 <syntaxhighlight>
 Get-PhysicalDisk | Get-StorageFirmwareInformation
 </syntaxhighlight>
 ====  ====

@@ Line 172: / Line 172: @@
 ==== Remove Drives? ====
-====  ====
+==== Finding Drive firmware versions and updating firmware versions as required ====
 ====  ====

← Older revision		Revision as of 16:59, 2 February 2017
Line 137:		Line 137:

	https://technet.microsoft.com/en-us/windows-server-docs/storage/storage-spaces/plan-volumes		https://technet.microsoft.com/en-us/windows-server-docs/storage/storage-spaces/plan-volumes
		+
		+	=== Managing your S2D cluster! ===
		+
		+	==== Adding Nodes ====
		+
		+	First much like when you first deployed the server you will need to test the server to make sure it has all updates, networking configuration etc to be added correctly to your cluster:
		+	<syntaxhighlight>
		+	Test-Cluster -Node <Node>, <Node>, <Node>, <NewNode> -Include "Storage Spaces Direct", Inventory, Network, "System Configuration"
		+	</syntaxhighlight>
		+	Then once confirmed it meets requirements (if one storage pool storage is added automatically, if not this will need to be manually added):
		+	<syntaxhighlight>
		+	Add-ClusterNode -Name NewNode
		+	</syntaxhighlight>
		+
		+	Existing volumes cannot be upgraded to a high number of mirrors or dual parity. If you wish to go from say a two-way mirror to three way since you have added another node. Then all data must be copied off the existing vol.
		+
		+	==== Removing Nodes ====
		+
		+	==== Add Drives ====
		+
		+	When adding new drives make sure that these are online and wiped within disk manager. if they have old data on S2D will not beable to add them to the storage pool. You can check whether they can be added or not with:
		+
		+	<syntaxhighlight>
		+	Get-PhysicalDisk \| Select SerialNumber, CanPool, CannotPoolReason
		+	</syntaxhighlight>
		+
		+	==== Remove Drives? ====
		+
		+	==== ====
		+
		+	==== ====