Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

2
  • So there's nothing inherently bad about the "Full Backup without COPY_ONLY" in the first diagram. It's just now you can't lose that backup - it's not just a backup you can stick on a USB stick and ship off somewhere for testing - because it is part of the chain. The virtue of COPY_ONLY is to let SQL Server know it's a one-off backup that not to worry about it. Commented Dec 16, 2021 at 16:32
  • In the first diagram, withOUT COPY_ONLY, why don't the future differential backups work against the [new, withOUT COPY_ONLY] full backup? That is, I realize you couldn't use them with the previous entries in the line, but it seems like the purple and green would simply move down to the withOUT full backup in that case and continue diff backups successfully. In other words, why make those final differential backups at all if they can't be applied to something? Commented Mar 25, 2022 at 20:48