Problem description

SQL Log backup fails with error “INTERNAL 65535” with an entry in detailed logs 'No last log commit information available' when backing up logs from a secondary node.

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

Follow the instructions provided in the link below to obtain job logs.
https://docs.druva.com/Knowledge_Bas...ailed_job_logs

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]

Resolution

Run a manual backup for this SQL Backup Set using ‘Backup Now’ option.

SQL log backups fail with error SQL8

SQL Log backup fails with the error SQL8: Database is already open and can only have one user at a time

SQL backups fail with snapshot error PHOENIX54

SQL backup failed: Vss Error: Operation timedout of gathering writer metadata

SQL backup fails with error VSS65535