HPE MSA Storage Configuration and Management Guide

3 Nov 2026, 17:5317 min readby ITYantra Admin

Complete guide to HPE MSA storage array configuration, management, pools, volumes, snapshots, and replication.

# HPE MSA Storage Configuration and Management Guide

Introduction

HPE MSA (Modular Smart Array) is HPE's entry-level to mid-range storage array family, designed for small to medium businesses and remote office/branch office (ROBO) deployments. The MSA 2060/2062 and MSA 2064/2066 current generations provide affordable shared storage with features typically found in enterprise arrays, including storage pools, thin provisioning, snapshots, and replication.

This guide covers complete HPE MSA storage configuration and management using both the web interface and CLI.

You will learn:

  • MSA hardware architecture and components
  • Initial setup and configuration
  • Storage pools and disk groups
  • Volumes and LUNs
  • Thin provisioning
  • Snapshots and replicas
  • Performance management
  • Troubleshooting common issues

Technical Background

MSA Hardware Architecture

**MSA 2060/2062 (2U, 24/12 SFF drives):**

  • Dual controllers (active-active)
  • 8 GB cache per controller (16 GB total)
  • 12 Gb/s SAS backend
  • Front-end: 1GbE/10GbE iSCSI, 8/16 Gb/s FC, or 10/25 GbE iSCSI (depending on model)
  • 24 SFF or 12 LFF drive bays

**MSA 2064/2066 (2U, 24 SFF drives):**

  • Dual controllers (active-active)
  • 16 GB cache per controller (32 GB total)
  • 12 Gb/s SAS backend
  • Front-end: 10/25 GbE iSCSI, 8/16/32 Gb/s FC
  • All-flash or hybrid options

Controller Architecture

MSA uses active-active dual controllers:

  • Both controllers can own volumes simultaneously
  • Automatic failover if one controller fails
  • Cache mirroring between controllers
  • Load balancing across controllers

Storage Pools vs Disk Groups

**Storage Pools (MSA 2060+):**

  • Multiple disk drives grouped into a pool
  • Volumes created from pool capacity
  • Thin provisioning support
  • Automatic data distribution across drives
  • Online expansion (add drives to pool)

**Disk Groups (traditional):**

  • Fixed RAID groups (RAID 1, 5, 6, 10)
  • Volumes created from disk groups
  • No thin provisioning
  • Simpler but less flexible

Thin Provisioning

Thin provisioning allocates storage on-demand rather than upfront.

**Benefits:**

  • Reduced initial storage purchase
  • Better capacity utilization
  • Over-provisioning (allocate more than physical capacity)

**Risks:**

  • Capacity exhaustion if not monitored
  • Performance degradation when near full
  • Requires careful capacity planning

Snapshots

Snapshots are point-in-time copies of volumes.

**MSA Snapshot Characteristics:**

  • Copy-on-write (initial snapshot is space-efficient)
  • Can be scheduled or manual
  • Can be mounted to hosts for backup
  • Can be promoted to become the base volume
  • Snapshot space allocated from pool

Remote Replication

MSA supports asynchronous replication between arrays.

**Characteristics:**

  • Block-level replication
  • Scheduled or continuous
  • Can replicate snapshots or volumes
  • Requires replication licenses on both arrays

Prerequisites

Hardware Requirements

  • HPE MSA 2060/2062/2064/2066 array
  • Compatible drives (SAS, SATA, or NVMe depending on model)
  • Front-end connectivity (FC, iSCSI, or both)
  • Management network port
  • Dual power supplies connected to different PDUs

Software Requirements

  • HPE MSA Storage Management Utility (web interface)
  • HPE MSA CLI (optional)
  • Host operating system with MSA support
  • MSA Snapshot License (for snapshots)
  • MSA Replication License (for replication)

Network Requirements

  • Management network (for web interface)
  • Storage network (iSCSI or FC)
  • DNS, NTP, SMTP configuration

Step-by-Step Implementation

Step 1: Initial Hardware Setup

**Physical Installation:** 1. Rack mount the MSA array 2. Install drives in drive bays 3. Connect power supplies to different PDUs 4. Connect management port to management network 5. Connect front-end ports to storage network 6. Power on the array

**Verification:**

  • Both controllers show healthy status
  • All drives detected
  • Management interface accessible

Step 2: Initial Configuration via Web Interface

**Access:** 1. Open browser to `https://<management-ip>` 2. Accept certificate warning 3. Log in with default credentials (from array label) 4. Change default password immediately

**Initial Setup Wizard:** 1. Configure system name and location 2. Set date/time or configure NTP 3. Configure DNS servers 4. Configure email alerts (SMTP) 5. Create administrator accounts 6. Configure front-end ports (iSCSI or FC) 7. Apply and save configuration

Step 3: Create Storage Pool

**Via Web Interface:** 1. Navigate to Storage → Pools 2. Click "Create Pool" 3. Select drives to include 4. Choose RAID level (default is RAID 5 for pools) 5. Configure:

6. Review and create

  • Pool name
  • RAID level
  • Drive type (SAS, SATA, NVMe)
  • Spare drives (optional)

**Via CLI:**

# Show available disks
show disks

# Create pool
create pool poolname=StoragePool1 raidlevel=raid5 disks=1:1,1:2,1:3,1:4,1:5,1:6

**Verification:** Pool shows "OK" status, capacity displayed correctly.

Step 4: Create Volumes (LUNs)

**Via Web Interface:** 1. Navigate to Storage → Volumes 2. Click "Create Volume" 3. Select pool 4. Configure:

5. Create volume

  • Volume name
  • Size (can be thin-provisioned)
  • Thin provisioning (enabled/disabled)
  • Allocation (full or thin)
  • Volume type (standard, snapshot, etc.)
  • Host access settings

**Via CLI:**

# Create thick volume
create volume volname=DB_Volume1 size=500GB pool=StoragePool1

# Create thin volume
create volume volname=VM_Datastore1 size=2TB pool=StoragePool1 thin=yes

# Map volume to host
create volume volname=vol1 size=1TB pool=StoragePool1
add volume volname=vol1 host=Server1 lun=1

**Verification:** Volume shows "OK", accessible from host.

Step 5: Configure Host Access

**iSCSI Configuration:** 1. Navigate to Storage → Hosts → iSCSI Initiators 2. Add initiator (IQN from server) 3. Create host object 4. Associate initiators with host 5. Map volumes to host with LUN IDs

**FC Configuration:** 1. Navigate to Storage → Hosts → FC Initiators 2. Add WWN from server HBA 3. Create host object 4. Map volumes to host

**Verification:** Host can see LUNs (`iscsiadm -m session` or `lspci | grep -i fc`)

Step 6: Configure Thin Provisioning (Optional)

**Enable thin provisioning on volume:** 1. Edit volume properties 2. Enable "Thin provisioning" 3. Set allocation threshold alerts 4. Monitor actual vs. provisioned capacity

**Capacity Planning:**

  • Monitor pool usage regularly
  • Set alerts at 70%, 80%, 90%
  • Add drives to pool before exhaustion

**Verification:** Thin volumes show allocated < provisioned capacity.

Step 7: Configure Snapshots

**Create Snapshot Schedule:** 1. Navigate to Storage → Snapshots 2. Click "Create Schedule" 3. Configure:

4. Enable schedule

  • Schedule name
  • Volume(s) to snapshot
  • Frequency (hourly, daily, weekly)
  • Retention count
  • Start time

**Manual Snapshot:** 1. Select volume 2. Click "Create Snapshot" 3. Provide name 4. Create

**Mount Snapshot to Host:** 1. Select snapshot 2. Click "Map to Host" 3. Select host and LUN ID 4. Host sees snapshot as separate LUN

**Verification:** Snapshots created, accessible from hosts.

Step 8: Configure Replication (Optional)

**Prerequisites:**

  • Replication license on both arrays
  • Network connectivity between arrays
  • Matching volume sizes

**Configuration:** 1. Navigate to Data Protection → Replication 2. Add remote array (IP, credentials) 3. Create replication set 4. Select volumes to replicate 5. Configure schedule 6. Enable replication

**Verification:** Replication status shows "OK", target array has replicated volumes.

Configuration Examples

Complete MSA Setup Script (CLI)

# Login to MSA CLI
# Show system information
show system

# Create pool
create pool poolname=ProductionPool raidlevel=raid5 disks=1:1-1:12 spare=1:13

# Create volumes
create volume volname=VM_Datastore size=2TB pool=ProductionPool thin=yes
create volume volname=DB_Data size=500GB pool=ProductionPool
create volume volname=DB_Log size=100GB pool=ProductionPool

# Create host
create host hostname=ESXi-Host1

# Add iSCSI initiator
add host hostname=ESXi-Host1 initiator=iqn.2024-01.com.example:esxi1

# Map volumes
add volume volname=VM_Datastore host=ESXi-Host1 lun=1
add volume volname=DB_Data host=ESXi-Host1 lun=2

# Enable snapshots
create snapshot schedname=DailySnap volume=VM_Datastore frequency=daily count=7 time=02:00

# View status
show pools
show volumes
show hosts

Thin Provisioning Monitoring

# Check pool capacity
show pool poolname=ProductionPool

# Check volume allocation
show volume volname=VM_Datastore
# Look for: Allocated vs. Provisioned capacity

Snapshot Management

# List snapshots
show snapshots

# Delete old snapshot
delete snapshot snapname=DailySnap_20240101

# Promote snapshot to volume
promote snapshot snapname=DailySnap_20240105 newvolname=Recovered_Volume

Verification

Storage Health Verification

# Check system status
show system

# Check pool status
show pools

# Check volume status
show volumes

# Check controller status
show controllers

# Check drive status
show disks

**Expected:** All components show "OK" status.

Host Access Verification

**Linux iSCSI:**

iscsiadm -m session
lsblk
multipath -ll  # If multipathing enabled

**Linux FC:**

lspci | grep -i fc
fcoe_cfg -l

**Windows:**

  • Disk Management: LUNs visible and online
  • MPIO: Multiple paths active

Replication Verification

show replication
# Check status: "OK" or "Synchronizing"

Troubleshooting

| Scenario | Symptom | Possible Cause | Diagnostic | Corrective Action | Verification | |----------|---------|----------------|------------|-------------------|--------------| | Cannot access web interface | Connection timeout | Network issue, wrong IP | `ping <mgmt-ip>` | Check network, verify IP | Interface loads | | LUN not visible on host | Disk not in `lsblk` | Zoning, masking, host not mapped | `show volumes`, host mapping | Map volume to host, check zoning | LUN visible | | Pool capacity full | Cannot write to volumes | Thin provisioning over-committed | `show pool poolname=` | Add drives to pool, delete snapshots | Capacity available | | Controller failover | Path errors on host | Controller failover event | `show controllers`, event log | Verify failover completed, check host MPIO | Both controllers active | | Slow performance | High latency | Pool near full, wrong RAID, controller overload | Performance metrics | Add drives, adjust RAID, balance load | Performance improved | | Snapshot creation fails | Error creating snapshot | Insufficient pool space, license missing | Event log, license status | Free pool space, install license | Snapshot created | | Replication fails | Replication status error | Network, license, version mismatch | Replication log, event log | Fix network, install license, match versions | Replication OK | | Drive failure | Degraded pool | Physical drive failure | `show disks`, LED amber | Replace drive, verify rebuild | Pool status OK | | Cannot add drives to pool | Error adding drives | Wrong drive type, incompatible | Drive compatibility list | Use compatible drives | Drives added to pool | | Thin volume near full | Allocation warning | Actual usage approaching pool capacity | Pool capacity monitor | Add capacity, delete data, reduce over-provision | Allocation below threshold |

Best Practices

1. **Use storage pools over disk groups** — Pools provide thin provisioning and easier expansion 2. **Configure dual controllers** — Active-active provides redundancy and load balancing 3. **Connect to different PDUs** — Each controller to different power source 4. **Monitor pool capacity** — Alert at 70%, 80%, 90% for thin pools 5. **Use snapshots for backup** — Quick point-in-time copies before changes 6. **Test failover regularly** — Quarterly controller failover tests 7. **Keep firmware updated** — MSA firmware fixes improve stability 8. **Document zoning and masking** — Critical for troubleshooting 9. **Use redundant paths** — MPIO for iSCSI/FC redundancy 10. **Plan capacity ahead** — Add drives before pool reaches 85%

Conclusion

HPE MSA storage arrays provide affordable, reliable shared storage for SMB and ROBO environments. The MSA 2060/2066 generation brings enterprise features like storage pools, thin provisioning, snapshots, and replication to a cost-effective platform.

Success with MSA depends on proper initial configuration, capacity monitoring, and regular maintenance including firmware updates and failover testing.

References

  • HPE MSA 2060 Storage User Guide: https://www.hpe.com/info/msa-docs
  • HPE MSA 2064 Storage User Guide: https://www.hpe.com/info/msa2064-docs
  • HPE MSA CLI Reference: https://www.hpe.com/info/msa-cli
  • HPE SPOCK (Storage Compatibility): https://www.hpe.com/info/spock
  • HPE MSA Best Practices: https://www.hpe.com/info/msa-best-practices
#hpe#msa#storage-array#storage-configuration#enterprise-storage#infrastructure