cancel
Showing results for 
Search instead for 
Did you mean: 

why does SQL transaction log taking too long after enabling the backup policy?

manatee
Level 6

NBU 7.6.0.3

we did upgrade of SQL Server over the weekend and during that time i have to disable the backup policies for SQL. included in that backup policies are the policies for transaction logs that occurs every 15 minutes.

when the upgrade of SQL server is done, i reactivated the backup policies. the policy for the database backup ran immediately because the backup window is already upon us. but the backup for the transaction logs (there are 2 of them) didn't run immediately. one ran after 9 minutes while the other is scheduled to run after 12 hours!

i don't want to run it manually as i know i have to issue the CLI command again to set it to 15 minutes interval. the question is, why do transaction log backups take hours to resume?

1 ACCEPTED SOLUTION

Accepted Solutions

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

Impossible for anyone to say without having any insight into Policy config and Global Settings.

Next time you see perceived abnormal behaviour, please post Policy output for at least one Policy misbehaving (bppllist <policy-name> -U) and nbpemreq output. 

 

View solution in original post

2 REPLIES 2

Michael_G_Ander
Level 6
Certified

Could be caused by the retry option in Master properties, which is default 2 tries per 12 hours.

The standard questions: Have you checked: 1) What has changed. 2) The manual 3) If there are any tech notes or VOX posts regarding the issue

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

Impossible for anyone to say without having any insight into Policy config and Global Settings.

Next time you see perceived abnormal behaviour, please post Policy output for at least one Policy misbehaving (bppllist <policy-name> -U) and nbpemreq output.