Timeline for Log size is different between primary and secondary node with log_since_last_log_backup_mb
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 30, 2018 at 0:11 | comment | added | Ola Hallengren | I have been talking to Microsoft about this. Unfortunately it is by design. The documentation has been updated. "When running sys.dm_db_log_stats against a database that is participating in an Availability Group as a secondary replica, only a subset of the fields described above will be returned. Currently, only database_id, recovery_model, and log_backup_time will be returned when run against a secondary database." learn.microsoft.com/en-us/sql/relational-databases/… | |
| Jul 17, 2018 at 20:50 | comment | added | Ola Hallengren | It looks like sys.dm_db_log_stats only has information in a few columns (database_id, recovery_model, and log_backup_time) when you query it on the secondary replica. All other columns are NULL. I think that this is regardless of where log backups have been performed. I will write back when I get an update from Microsoft. | |
| Jul 17, 2018 at 20:35 | comment | added | S3S |
@OlaHallengren should it not return NULL if a backup hasn't happened on that node, especially if the node was the primary?
|
|
| Jul 17, 2018 at 20:29 | comment | added | Ola Hallengren | I am aware of this issue. I am in contact with Microsoft about it. | |
| Jul 17, 2018 at 19:57 | history | answered | S3S | CC BY-SA 4.0 |