Comprehensive data protection for all workloads
foggy
Veeam Software
Posts: 18348
Liked: 1575 times
Joined: Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson
Contact:

Re: Backup SQL Always ON 2016 Basic Availiblity Group

Post by foggy » Feb 26, 2019 4:01 pm

Starting next update there will be no logs truncation for excluded databases.

csmall
Enthusiast
Posts: 27
Liked: 2 times
Joined: Mar 20, 2018 1:19 pm
Full Name: Colin Small
Contact:

Re: Backup SQL Always ON 2016 Basic Availiblity Group

Post by csmall » Feb 28, 2019 4:27 pm

The warnings about in the transaction log backup of the secondary node, are they just annoying or should I be concerned about them? In other words, is it cosmetic or is it an actual problem?

foggy
Veeam Software
Posts: 18348
Liked: 1575 times
Joined: Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson
Contact:

Re: Backup SQL Always ON 2016 Basic Availiblity Group

Post by foggy » Feb 28, 2019 4:53 pm

Hi Colin, do you mean logs truncation, not backup? It's not a problem, since you cannot truncate logs there anyway.

csmall
Enthusiast
Posts: 27
Liked: 2 times
Joined: Mar 20, 2018 1:19 pm
Full Name: Colin Small
Contact:

Re: Backup SQL Always ON 2016 Basic Availiblity Group

Post by csmall » Feb 28, 2019 7:18 pm

I think so, yes. I apologize for the confusion. We had an eventful morning related to the backup of a SQL Availability Group.

The job will warn that it can't truncate logs on the inactive node because it doesn't have read access etc..

We had a failover or two happen in the AG and the log backup job never seemed to recover from it. It just failed repeatedly to backup the logs of the one database in the AG and eventually seemed to stop trying. I'm hoping it resolves itself if I disable the job and re-enable it again.

Or maybe running an Active Full would help?

foggy
Veeam Software
Posts: 18348
Liked: 1575 times
Joined: Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson
Contact:

Re: Backup SQL Always ON 2016 Basic Availiblity Group

Post by foggy » Mar 01, 2019 11:37 am

Depending on the actual error message you saw. It is better to verify with the support team, since we can just guess here. Typically issues caused by failover go away after the next parent job successful run.

Post Reply

Who is online

Users browsing this forum: bytewiseits, Google [Bot] and 20 guests