Path: csiph.com!news.mixmin.net!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: Erland Sommarskog Newsgroups: comp.databases.ms-sqlserver Subject: Re: Make a backup only if necessary Date: Tue, 28 May 2024 20:11:54 +0200 Organization: Erland Sommarskog Lines: 10 Message-ID: References: <20240527125929.d701039c2aec3196dc3d4731@g{oogle}mail.com> <20240528124112.80ab65ec4a358da57093539b@g{oogle}mail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 8bit Injection-Date: Tue, 28 May 2024 20:11:54 +0200 (CEST) Injection-Info: dont-email.me; posting-host="be090965047f9690b38df5cfddf99516"; logging-data="760382"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18z5MOv/wHP4xbBosc/h8NI" User-Agent: Xnews/2006.08.24 Mime-proxy/2.1.c.0 (Win32) Cancel-Lock: sha1:pPi9wofvzMKCW2s+U9JlIPx38o8= Xref: csiph.com comp.databases.ms-sqlserver:2251 Anton Shepelev (anton.txt@g{oogle}mail.com) writes: > I still fail, however, to understand why `first_lsn' changes > for each subsequent diff. backup. It is described as the > "log sequence number of the first or oldest log record in > the backup set." Since the last five diff. backups were > generated with respect to the same full backup, I expected > them to have the same first_lsn. Why do they not? > Because the backup itself is logged.