Snapshot Architecture

• FlashArray snapshots are crash consistent snapshots. SQL Server data and log files are preserved however uncommitted transactional data is lost.
• Cloned SQL Server database files from FlashArray snapshots can be attached to a SQL Server instance creating a database copy. During the attach process SQL Server automatically will perform its own crash recovery to either persist committed transactions, or not persist uncommitted transactions to storage.
• FlashArray snapshots rely on copying the metadata mapping of data location information managed by Purity operating environment. These snapshots are immutable there are no parent/child relationships.
• Any subsequent writes that occur on the source volume (Volume 1) in the example below are redirected for efficiency.
• A new volume (Volume 2) can be activated with no hierarchical relationship to the snapshot or parent volume offering flexible deployment. See picture below.

• FlashArray snapshots are immutable. The source volume can be deleted, and eradicated without affecting any subsequent created snapshots, or activated volumes.
• In the example below the blocks that were associated with the deleted source volume are now marked for reuse.