With a SQL Server 2012 availability group, you can only take
COPY_ONLY full backups on replica. You can make regular
As it's possible to restore logs backups after a database restoration from a
COPY_ONLY dump, do we really need to take full (non-
Yeah, it creates a new LSN sequence, but if we're not doing
DIFFERENTIAL backups, is it something we have to think about?
By using only
COPY_ONLY backups, I would hope to gain the ability to perform all backups on the read-only replica. My AG is asynchronous, so the backups might be behind the primary, but that is an acceptable risk.
I do take log backups. According to my tests, I'm able to restore any log backup on a database (restored from a
COPY_ONLY or not) as soon as the log backup LSN is more recent than the full backup. The full backup changes the
COPY_ONLY doesn't, but it seems it doesn't affect log restore. It seems I just can't restore DIF backups, but I don't need that.
There's a good explanation in the dba.se Q &A:
...but it does not answer my question. For now, my conclusions are: Except for the first backup (without which you will not be able to take log backups), we just can work with
COPY_ONLY backups if we don't use differentials.
My (general) question is: Do we really need non-
COPY_ONLY backups if we don't take differentials, and if yes, why?