Skip to main content
Question

Unprotected DB from the primary node in SQL AG. Other DBs are being backed up successfully

  • August 11, 2026
  • 5 comments
  • 45 views

Forum|alt.badge.img+1

Unprotected DB from the primary node in SQL AG. Other DBs are being backed up successfully on the same primary server.

Configured to run transactional logging periodically but one large DB shows as unprotected. The problem started when the old primary node was switched over to a new server and evicted. After the eviction, it started not backing up the DB

(error: Transaction logs from some databases were not backed up for the last 8 intervals).

Ran image level backup (the parent job), this was successful but transaction logging still not working. However, the error now shows as 

(error: SQL Server transaction log backup took longer than desired log backup interval
Failed to upload SQL Server transaction log backup for DB to LogShip server: Repository agent is stopped
SQL Server transaction log backup could not be completed within 10 RPO intervals and will not be retried)

This was working before and no changes to any of the Veeam servers so this error is not accurate. 

Confirmed application-aware processing is enabled.
Other databases on the same SQL server are being protected. 
Confirmed both current AG replicas are connected and synchronization healthy.
Confirmed Primary Node is the preferred backup replica for this DB.
Confirmed the parent image-level job completed successfully after the original primary was evicted.
Confirmed both current AG replicas are connected and synchronization healthy.
Confirmed other databases on the primary node have successful transaction-log processing. 

What other configuration or setting can I check / change?

5 comments

Chris.Childerhose
Forum|alt.badge.img+22

What version of Veeam are you using and plugin for SQL?  What does the logs say about the job - C:\ProgramData\Veeam\Backup\Job Name?

You are probably better off opening a support ticket for this one.


Forum|alt.badge.img+1
  • Author
  • Influencer
  • August 11, 2026

A ticket has been opened to support over the weekend. The weekend engineer suggest to upgrade to v13.1 (we are currently at v13.0.1). Not sure if this would really help knowing that transaction logging was working before the eviction. 


Chris.Childerhose
Forum|alt.badge.img+22

Then you need to convey that in the ticket if not already.  Hopefully support gets you sorted out.


Forum|alt.badge.img+1
  • Author
  • Influencer
  • August 17, 2026

The case has been closed.

The new DB servers that were added to the SQL Always On Group did not have the Veeam Installer Service. Even though Veeam was able to back up the other transaction logs using VIX, it was not able to backup the bigger DB within the required period. This was initially increased from 15 minutes to 30 minutes but it was still throwing the same error. Had to address the error :

Failed to install Log Shipping Service using connect to guest agent via GIP, failing over to guest runtime components through VIX via GIP for guest interaction

by creating a deployment kit and installing on the new servers which installed the Veeam Installer that allowed the other Veeam services to be installed:

 


Chris.Childerhose
Forum|alt.badge.img+22

Great to hear you got a resolution for this issue.