I want to adjust storage job priority levels which will speed up storage rebalancing in our S2D cluster.

Hello,

By default, Storage Spaces Direct (S2D) relies on background storage jobs that run with low priority to avoid impacting production workloads. These jobs include repair, rebalancing, and scrubbing. When you replace a failed HDD, the cluster automatically triggers a repair job to redistribute data, but the priority is intentionally throttled to minimize performance disruption. That’s why you’re seeing localized high disk utilization during rebuilds-it’s working, but not aggressively enough to finish quickly.

You can adjust this behavior using PowerShell. The relevant cmdlet is Set-StorageSubSystem -ThrottleLimit. For example, running:

Get-StorageSubSystem | Set-StorageSubSystem -ThrottleLimit 100

will increase the throttle limit to 100 percent, effectively allowing repair and rebalancing jobs to consume more I/O and CPU resources. The default is usually 30, which keeps jobs in the background. Raising it speeds up rebalancing significantly, but you must be aware that it can impact live workloads if the cluster is under heavy use.

Another option is to use Set-StorageJob to change the priority of a currently running job. For example:

Get-StorageJob | Set-StorageJob -Priority High

This forces the repair/rebalance job to run at higher priority immediately. It’s particularly useful right after replacing a failed drive when you want the cluster to heal faster.

Best practice is to temporarily raise the throttle or job priority during maintenance windows or after hardware replacement, then return it to default once the cluster is healthy again. This balances recovery speed with workload stability.

I hope you've found something useful here. If it helps you get more insight into the issue, it's appreciated to accept the answer. Should you have more questions, feel free to leave a message. Have a nice day!

HP.