Multiple virtual machines experience performance impact simultaneously.
Storage or application throughput (I/O) drops to 0 during the scheduled backup window.
Throughput degradation is observed during backup operations or snapshot consolidation.
Throughput returns appears normal once the backup or snapshot consolidation process completes.
No persistent performance degradation or data loss appears after the operation finishes.
VMware vSAN 8.x
Vmware.log :
2025-10-27T13:41:08.150Z In(05) vmx - SNAPSHOT: SnapshotPrepareTakeDoneCB: Prepare phase complete.2025-10-27T13:41:08.590Z In(05) vcpu-0 - SnapshotVMXTakeSnapshotComplete: Done with snapshot '__G#_BACk##__': 4892025-10-28T13:33:06.256Z In(05) vcpu-0 - Checkpoint_Unstun: vm stopped for 385332 us2025-10-28T13:33:06.285Z In(05) vcpu-0 - CPT: vm was stunned for 414878 us2025-10-29T13:27:47.591Z In(05) vcpu-0 - Checkpoint_Unstun: vm stopped for 408370 us2025-10-29T13:27:47.620Z In(05) vcpu-0 - CPT: vm was stunned for 437796 us2025-10-29T13:48:37.386Z In(05) vcpu-0 - ConsolidateEnd: Snapshot consolidate complete: The operation completed successfully (0).This is expected behavior in VMware environments during snapshot consolidation. However, the impact can be mitigated by implementing the following best practices:
Schedule backups during off-peak hours to minimize production impact.
Reduce snapshot size by increasing backup frequency or retention rotation.
Verify storage performance ensure datastores and underlying storage can sustain high I/O throughput during consolidation.
Use Change Block Tracking (CBT)-enabled backup tools to reduce data delta sizes.
Monitor consolidation duration using vCenter performance metrics or VMware Aria Operations.
If the stun duration exceeds expected levels (seconds ,minutes), review snapshot size and storage latency for potential bottlenecks.