<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Crash-Consistent on Anthony Nocentino&#39;s Blog</title>
    <link>https://www.nocentino.com/tags/crash-consistent/</link>
    <description>Recent content in Crash-Consistent on Anthony Nocentino&#39;s Blog</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 08 May 2026 05:00:00 -0500</lastBuildDate>
    <atom:link href="https://www.nocentino.com/tags/crash-consistent/rss.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Crash-Consistent Snapshot Cloning - Hyper-V Edition</title>
      <link>https://www.nocentino.com/posts/2026-05-08-crash-consistent-snapshot-cloning-hyper-v-edition/</link>
      <pubDate>Fri, 08 May 2026 05:00:00 -0500</pubDate>
      <guid>https://www.nocentino.com/posts/2026-05-08-crash-consistent-snapshot-cloning-hyper-v-edition/</guid>
      <description>&lt;p&gt;If you&amp;rsquo;ve been following my &lt;a href=&#34;https://www.nocentino.com/categories/using-t-sql-snapshot-backup/&#34;&gt;T-SQL Snapshot Backup series&lt;/a&gt;, most of what I&amp;rsquo;ve covered requires SQL Server to participate in the snapshot: the write IO freeze, the metadata backup, the coordinated workflow. This post covers the other side of that coin: crash-consistent cloning. No write freeze. No backup. No point-in-time recovery. Just a raw volume clone that SQL Server recovers from automatically when you attach it.&lt;/p&gt;&#xA;&lt;h2 id=&#34;what-is-a-crash-consistent-snapshot&#34;&gt;What Is a Crash-Consistent Snapshot?&lt;/h2&gt;&#xA;&lt;p&gt;When people talk about snapshot backups for SQL Server, they often jump straight to application-consistent snapshots, the kind where SQL Server is asked to freeze write IO before the snapshot. That freeze guarantees every page on disk reflects a logically consistent database state.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
