Storage Operations • Infrastructure Capacity Management

Primary NVMe Datastore Capacity Exhaustion Risk

Operational storage capacity incident involving Proxmox VM datastore growth, workload redistribution, and infrastructure storage management within the PatrickHomeLab virtualization environment.

Overview

Incident Summary

The Forge Proxmox hypervisor began approaching primary NVMe datastore capacity thresholds due to increased VM disk utilization and expanding infrastructure workloads.

Selected virtual machine workloads were migrated from the primary NVMe datastore to a dedicated SSD datastore to restore operational storage capacity and improve infrastructure scalability.

Environment

Infrastructure Components

Infrastructure Environment
  • Hypervisor Platform: Forge (Proxmox VE)
  • Primary Storage: NVMe datastore
  • Secondary Storage: Dedicated SSD datastore
  • Affected Infrastructure:
    • media-01
    • monitoring infrastructure
    • supporting VM workloads
Problem

Operational Risks

The primary NVMe datastore was approaching operational storage thresholds, creating infrastructure risks and reducing future deployment flexibility.

Operational Risks Identified
  • Reduced available capacity for future VM deployment
  • Increased risk of datastore exhaustion
  • Limited flexibility for snapshots and maintenance
  • Reduced storage headroom for infrastructure growth
  • Potential impact to virtualization stability
Objective

Migration Goals

The migration effort focused on redistributing VM storage workloads to a dedicated SSD datastore while maintaining operational continuity across lab infrastructure services.

Migration Objectives
  • Restore available NVMe datastore capacity
  • Improve storage allocation strategy
  • Preserve infrastructure operational stability
  • Maintain service availability during migration
  • Improve future scalability
Migration Actions

Actions Performed

Several operational tasks were completed to safely redistribute storage workloads across available datastores.

Migration Workflow
  • Provisioned SSD datastore within Proxmox
  • Evaluated VM storage utilization
  • Selected workloads appropriate for migration
  • Migrated VM disks from NVMe storage to SSD storage
  • Validated successful VM boot operations
  • Verified service availability post-migration
qm move_disk <vmid> scsi0 <target-storage>
Validation

Post-Migration Validation

Validation procedures confirmed infrastructure stability and successful workload redistribution following storage migration operations.

Validation Results
  • VM startup behavior confirmed
  • Plex services operational
  • Storage mounts verified
  • No data loss observed
  • Infrastructure services remained stable
Result

Operational Outcome

The migration successfully reduced pressure on the primary NVMe datastore while maintaining operational continuity across infrastructure services.

The updated storage allocation strategy improved capacity management and restored additional storage headroom for future infrastructure expansion.

Lessons Learned

Operational Takeaways

  • Early storage planning is critical for virtualization environments
  • Infrastructure growth can rapidly impact datastore utilization
  • Segregating workloads across storage tiers improves flexibility
  • Capacity monitoring should be integrated into routine workflows
  • Storage scalability planning becomes increasingly important