In HPE 3PAR StoreServ environments, maintaining a healthy disk infrastructure is not limited to monitoring RAID levels or checking the status of physical drives. Another important component is the Sparing Algorithm, which defines how the system allocates spare capacity to protect against disk failures.
The Sparing Algorithm determines how HPE 3PAR reserves and manages spare space across the storage system. Depending on the selected policy, the system can prioritize either capacity efficiency or a higher level of reserved spare space.
In this article, we will look at how to check the current Sparing Algorithm setting, how to change it, and how to apply the new configuration on an HPE 3PAR StoreServ system.
What Is the Sparing Algorithm?
In HPE 3PAR architecture, sparing is used to provide protection against physical disk failures by reserving capacity that can be used when a drive becomes unavailable.
Unlike traditional storage systems where one or more dedicated physical disks are commonly configured as hot spares, HPE 3PAR uses a more distributed and dynamic approach to spare capacity management.
The Sparing Algorithm parameter controls the policy used by the system to manage this reserved space.
The available options include:
- Default
- Minimal
- Maximal
- Custom
The appropriate setting depends on the storage design, disk population, capacity requirements, and the organization’s availability and protection strategy.
Supported HPE 3PAR Systems
This configuration applies to multiple generations of HPE 3PAR systems, including:
- HPE 3PAR E-Class Storage Systems
- HPE 3PAR F-Class Storage Systems
- HPE 3PAR S-Class Storage Systems
- HPE 3PAR T-Class Storage Systems
- HPE 3PAR StoreServ 7000
- HPE 3PAR StoreServ 7450
- HPE 3PAR StoreServ 8000
- HPE 3PAR StoreServ 9000
- HPE 3PAR StoreServ 10000
- HPE 3PAR StoreServ 20000
Before making any changes, it is always recommended to verify the exact behavior and support status for your specific HPE 3PAR OS version and hardware platform.
Checking the Current Sparing Algorithm
Before changing any system parameter, first verify the existing configuration.
From the HPE 3PAR CLI, run:
showsys -paramExample output:
cs.s400.test1 cli% showsys -param
System parameters from configured settings
---Parameter---- -Value-
RawSpaceAlertFC : 0
RawSpaceAlertNL : 0
RemoteSyslog : 0
RemoteSyslogHost : 0.0.0.0
SparingAlgorithm : MinimalThe important line in this output is:
SparingAlgorithm : MinimalThis indicates that the current Sparing Algorithm is configured as Minimal.
In production environments, it is a good practice to save or record the current configuration before making any changes. This provides a reference point if rollback or troubleshooting is required later.
Changing the Sparing Algorithm
The Sparing Algorithm parameter is modified using the setsys command.
For example, if the current value is Minimal and you want to change it to Default, run:
setsys SparingAlgorithm DefaultAfter changing the parameter, verify that the new value has been applied:
showsys -paramYou should now see:
SparingAlgorithm : DefaultThis confirms that the configuration parameter has been updated successfully.
Applying the New Configuration
After changing the Sparing Algorithm, the system should re-evaluate the hardware configuration so that the new sparing policy can be applied.
Run:
admithwThis command causes the system to re-evaluate the physical hardware configuration and allows the new sparing policy to take effect.
The complete workflow is therefore:
showsys -paramCheck the current setting.
Then:
setsys SparingAlgorithm DefaultSet the new policy.
Next:
showsys -paramVerify the updated value.
Finally:
admithwApply the new hardware configuration.
Complete Example
A practical sequence may look like this:
# Check the current system parameters
showsys -param
# Change the Sparing Algorithm to Default
setsys SparingAlgorithm Default
# Verify the new setting
showsys -param
# Re-evaluate the hardware configuration
admithwAfter completing these steps, run showsys -param once more to confirm that the intended Sparing Algorithm is still configured.
Things to Consider Before Changing the Sparing Algorithm
Although the procedure itself is straightforward, the Sparing Algorithm should not be treated as just another CLI parameter. It directly affects how spare capacity is managed across the storage system.
For that reason, consider the following points before making changes:
Record the current configuration.
Save the output of showsys -param before making any modifications.
Check the physical disk status.
If the system contains failed, degraded, or rebuilding drives, address those conditions before changing spare capacity policies.
Review available capacity.
Different sparing policies may affect how much raw capacity remains available for normal data usage.
Use a formal change process.
In production environments, the modification should ideally be performed during an approved change window.
Verify the HPE 3PAR OS version.
Behavior and supported options may vary depending on the installed 3PAR OS release. Always validate the procedure against the official documentation for the relevant version.
The Sparing Algorithm in HPE 3PAR StoreServ systems is an important configuration parameter that controls how spare capacity is reserved and managed for physical disk failures.
To check the current setting, use:
showsys -paramTo change the Sparing Algorithm:
setsys SparingAlgorithm DefaultTo re-evaluate the hardware configuration and apply the new policy:
admithwWhile the configuration change itself is simple, it should always be performed with an understanding of the current disk health, capacity utilization, and storage protection requirements.
A properly planned sparing policy helps maintain the right balance between usable capacity and resilience against hardware failures in an HPE 3PAR StoreServ environment.
