Cause

• When the backup preference is set to ‘secondary’ in an AAG configuration, the Hybrid workload agent for SQL performs a backup from the secondary node.
• If a transaction log entry for the database is not found in msdb.dbo.backupset on the secondary node transaction log backup fails.

Traceback

1. Follow the instructions provided in the link below to obtain job logs.
   https://docs.druva.com/Knowledge_Bas...ailed_job_logs
2. Extract the logs and go to Phoenix<YYYYMMDD>_<timestamp>.log file to see the below traceback in the logs.
   [ERROR] <_MainThread(MainThread)> Error <type 'exceptions.Exception'>:No current entry in backupset for [Instance_Name:DB_Name] for LOG backup type. Traceback -Traceback (most recent call last):
File "agents\sqlserver\VssHelper.pyc", line 723, in __is_log_chain_stable_for_ag
File "agents\sqlserver\sql_vss_2.pyc", line 177, in get_current_backupset_details
Exception: No current entry in backupset for [Instance_Name:DB_Name] for LOG backup type
[WARNING] <_MainThread(MainThread)> No Last log commit information available Instance_Name:DB_Name
[ERROR] <_MainThread(MainThread)> Unable to process database[DB_Name] for log backup: No last log commit information available[Instance_Name:DB_Name]
[ERROR] <_MainThread(MainThread)> Unable to discover databases for log backup: No last log commit information available[Instance_Name:DB_Name]