Best Practice Suggestion: Why You Should Treat Your 7-Snapshot Limit as a Strict Performance Safety Net

George Fady Lv2Posted 2026-Jun-30 19:09

When configuring VM Snapshot Policies in Sangfor HCI, the platform natively allows a maximum retention of 7 snapshots per virtual instance or VM Consistency Group. This is applicable only to instances operating on distributed Virtual Storage.
I highly suggest that infrastructure teams enforce a strict 24-to-48-hour lifecycle policy for all system-state snapshots instead of letting them sit indefinitely.
Why?
  • The Merging Overhead: Snapshots rely on redirection or delta-tracking mechanisms. When you keep a long chain of snapshots active, the virtualization layer must read across multiple block layers, drastically increasing disk read/write I/O latency.
  • The Proper Alternative: Snapshots are designed for temporary system rollbacks (e.g., right before an OS patch or major software upgrade). For resilient data retention, transition the workload immediately to Scheduled Backups (Hourly/Daily/Weekly with periodic full backups to reduce merge time) or Continuous Data Protection (CDP) under Reliability > Scheduled Backup/CDP.

Feel alike? Bump to help this suggestion accepted by developers.

An accepted suggestion earns you 100 to 1000 coins. For more active members in Suggestions board, a badge Product Consultant may be rewarded. What is Coin?

Enter your mobile phone number and company name for better service. Go