July 24, 2014 at 10:44 am
Perry Whittle (7/23/2014)
Jeff Moden (7/21/2014)
Perry Whittle (7/21/2014)
Steve Jones - SSC Editor (7/21/2014)
GilaMonster (7/16/2014)
Steve Jones - SSC Editor (7/16/2014)
Yes. I believe you can use copy only, which avoids thisFull backups do not break the log chain. Copy only on full backups is solely to avoid resetting the differential base.
Ahh, sorry, was thinking you mentioned extra log backups, which are problematic.
Fulls don't matter, as Gail mentioned
They don't affect log backups but they do affect differential backups 😉
Technically, I agree but if you do a full backup to a different drive or folder than where the backups are normally stored at (or even the same folder) and someone deletes it, I believe (haven't tried it in a very long time and don't remember for sure) that can screw up the GUI for doing a restore because MSDB still thinks the file exists.
If you take a log backup to different drive or delete it the same is true, so I don't see your point.
Ah. Apologies. Missing information. I'm talking about folks that may take an ad hoc backup for purposes of doing a restore to a different machine (as some do to make "Dev Copies") and then deleting them (as they should) when they're done. They forget that MSDB is going to remember that the backup was made and deleting the file can mess up what the GUI sees for doing a restore. It doesn't "kill" anything but it can make it a bit confusing.
I haven't actually tried it for several revs of SQL Server. It may be that the GUI now simply ignores missing full backups if the log file chain is intact and, of course, having a missing full backup doesn't change the log file chain.
--Jeff Moden
Change is inevitable... Change for the better is not.
Viewing post 16 (of 15 total)
You must be logged in to reply to this topic. Login to reply