Crash-Consistent and Application-Consistent Snapshots

  • 30 October 2019
  • 1 reply
  • 7535 views

Userlevel 4
Badge +5

Confused regarding crash-consistent snapshot and application-consistent snapshot?

 

Crash-Consistent Snapshot

VM snapshots are by default crash-consistent, which means that the vDisks captured are consistent with a single point in time. The snapshot represents the on-disk data as if the VM crashed or the power cord was pulled from the server—it doesn’t include anything that was in memory when the snapshot was taken. Today, most applications can recover well from crash-consistent snapshots.

 

Application-Consistent Snapshot


Application-consistent snapshots capture the same data as crash-consistent snapshots, with the addition of all data in memory and all transactions in process. Because of their extra content, application-consistent snapshots are the most involved and take the longest to perform.

While most organizations find crash-consistent snapshots to be sufficient, Nutanix also supports application-consistent snapshots. The Nutanix application-consistent snapshot uses Nutanix Volume Shadow Copy Service (VSS) to quiesce the file system for ESXi and AHV prior to taking the snapshot. You can configure which type of snapshot each protection domain should maintain.


Want to know more about Data Protection and Recovery?

Give the following document a read?

Data Protection and Recovery


This topic has been closed for comments

1 reply

Hi there, thanks for a clear-cut explanation between the two consistent snapshots. BUT on the server application side, does Application-Consistent Snapshot  if enabled would affect the negative performance of the server vs disabling application-consistent? Thanks - LC