Skip to main content
Bumped by Community user
Bumped by Community user
Bumped by Community user
Tweaked grammar and formatting
Source Link
András Váczi
  • 31.6k
  • 13
  • 101
  • 149

We get log backups from the secondary node. But now I see that log_since_last_log_backup_mb in sys.dm_db_log_stats returns null for databases which are in Availability groups, so Ola Hallengren's log backup procedure with

@LogSizeSinceLastLogBackup = 25,@TimeSinceLastLogBackup = 21000 

limitations works on those databases. But theThe backup process is currently working on the secondary node.

But I could not understand why it returns null? Have you encountered such a situation?

The following pictures show result of log size since last log backup on the primary and secondary nodes.

Primary Node

enter image description here

Secondary Node

enter image description here

We get log backups from the secondary node. But now I see that log_since_last_log_backup_mb in sys.dm_db_log_stats returns null for databases which are in Availability groups, so Ola Hallengren's log backup procedure with

@LogSizeSinceLastLogBackup = 25,@TimeSinceLastLogBackup = 21000 

limitations works on those databases. But the backup process is currently working on the secondary node.

But I could not understand why it returns null? Have you encountered such a situation?

The following pictures show result of log size since last log backup on the primary and secondary nodes.

Primary Node

enter image description here

Secondary Node

enter image description here

We get log backups from the secondary node. But now I see that log_since_last_log_backup_mb in sys.dm_db_log_stats returns null for databases which are in Availability groups, so Ola Hallengren's log backup procedure with

@LogSizeSinceLastLogBackup = 25,@TimeSinceLastLogBackup = 21000 

limitations works on those databases. The backup process is currently working on the secondary node.

But I could not understand why it returns null? Have you encountered such a situation?

The following pictures show result of log size since last log backup on the primary and secondary nodes.

Primary Node

enter image description here

Secondary Node

enter image description here

We get log backupbackups from the secondary node. But now I see that log_since_last_log_backup_mb in sys.dm_db_log_stats returns null for databases which are in Availability groups, so theOla Hallengren's log backup procedure(of Ola Hallengren) with @LogSizeSinceLastLogBackup = 25,@TimeSinceLastLogBackup = 21000

@LogSizeSinceLastLogBackup = 25,@TimeSinceLastLogBackup = 21000 

limitations works works on those databases. But the backup process is currently working on the secondary node. But

But I could not understand why it returns null? Have you encountered such a situation? Following

The following pictures show result ofof log size since last log backup inon the primary and secondary node nodes.

Primary Node

enter image description here

Secondary Node

enter image description here

We get log backup from the secondary node. But now I see that log_since_last_log_backup_mb in sys.dm_db_log_stats returns null for databases which in Availability groups, so the log backup procedure(of Ola Hallengren) with @LogSizeSinceLastLogBackup = 25,@TimeSinceLastLogBackup = 21000 limitations works on those databases. But the backup process is currently working on the secondary node. But I could not understand why it returns null? Have you encountered such a situation? Following pictures show result of log size since last log backup in primary and secondary node enter image description here

enter image description here

We get log backups from the secondary node. But now I see that log_since_last_log_backup_mb in sys.dm_db_log_stats returns null for databases which are in Availability groups, so Ola Hallengren's log backup procedure with

@LogSizeSinceLastLogBackup = 25,@TimeSinceLastLogBackup = 21000 

limitations works on those databases. But the backup process is currently working on the secondary node.

But I could not understand why it returns null? Have you encountered such a situation?

The following pictures show result of log size since last log backup on the primary and secondary nodes.

Primary Node

enter image description here

Secondary Node

enter image description here

Source Link

Log size is different between primary and secondary node with log_since_last_log_backup_mb

We get log backup from the secondary node. But now I see that log_since_last_log_backup_mb in sys.dm_db_log_stats returns null for databases which in Availability groups, so the log backup procedure(of Ola Hallengren) with @LogSizeSinceLastLogBackup = 25,@TimeSinceLastLogBackup = 21000 limitations works on those databases. But the backup process is currently working on the secondary node. But I could not understand why it returns null? Have you encountered such a situation? Following pictures show result of log size since last log backup in primary and secondary node enter image description here

enter image description here