AlwaysOn Secondary backup (Full & Log) - Primary T-Log not shrinking

Question

AlwaysOn Secondary backup (Full & Log) - Primary T-Log not shrinking

Viewing 3 posts - 16 through 18 (of 18 total)

You must be logged in to reply to this topic. Login to reply

Gail Shaw SSC Guru Points: 1004514 More actions · Answer 1

Roger Mac - Wednesday, September 20, 2017 11:26 AM
Perhaps as we move DB's to the AO clusters I just need to make sure I run a Full normal backup on the Primary before kicking off daily Full copy-only backups on the Secondary so that the Secondary Log backups are properly "set"?

Full backups, normal or copy-only, have no effect on the log other than to initialise a log chain, and that they both do exactly the same. Your problem is going to be related to where the log backups are running, NOT the option on the full backup.

The only difference between a normal full backup and a copy-only full backup is that the copy-only does not reset the differential base.

Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Perry Whittle SSC Guru Points: 234064 More actions · Answer 2

One straight after the other!

-----------------------------------------------------------------------------------------------------------

"Ya can't make an omelette without breaking just a few eggs" 😉

Roger Mac Old Hand Points: 323 More actions · Answer 3

GilaMonster - Wednesday, September 20, 2017 11:42 AM
Roger Mac - Wednesday, September 20, 2017 11:26 AM
Perhaps as we move DB's to the AO clusters I just need to make sure I run a Full normal backup on the Primary before kicking off daily Full copy-only backups on the Secondary so that the Secondary Log backups are properly "set"?
Full backups, normal or copy-only, have no effect on the log other than to initialise a log chain, and that they both do exactly the same. Your problem is going to be related to where the log backups are running, NOT the option on the full backup.
The only difference between a normal full backup and a copy-only full backup is that the copy-only does not reset the differential base.

Gail, once again, excellent info! Thank you so much for this. 😀
The reason I was wondering about a full backup on primary is because I believe the DB was in "Simple" mode at one point, either during the move or after for alternate reasons. But it sounds like any type of Full backup (regular or copy-only) on either either replica (Primary or Secondary) after returning to "Full" mode should get the log file in line for expected log file behavior.