Skip to main content
  • EN

SQL Transaction log backup seems to be failing with "Failed to perform internal backup."

We just did a big repair of one of our DBs. When I re-enable the backup job (with SQL transaction log backup), it started failing with the following error.

 

Failed to perform internal backup (DBName): Code = 0x80040e31 Code meaning = IDispatch error #3121 Source = Microsoft SQL Server Native Client 11.0 Description = Query timeout expired COM error: Code: 0x80040e31

 

We can see data being moved as shown in the Report so is the Transaction Log backup really failing or it is just doing catch up with the large change? I’m sure if we run a full backup or possibly change the log backup interval to longer, this will resolve the error. 

Thanks.

I was just about to say run a full backup to start a new chain versus waiting on it to catch up.  This might be faster.

Unsure why it is failing but would need to check the logs - C:\ProgramData\Veeam\Backup\SQLJobName

If this is a real problem them Support is the route to go.

I looked at the log and it did not indicate any error just this message:

WARN|MTA invoke thread : timed out for backup events. Wait cycle will be resumed for '336' hours.

I’ll open a ticket to support just to understand what is happening here. Our DBA seems to think that backup is running but being successful or not is another issue. Veeam shows UNPROTECTED even though it shows data being read and written. 

I looked at the log and it did not indicate any error just this message:

WARN|MTA invoke thread : timed out for backup events. Wait cycle will be resumed for '336' hours.

I’ll open a ticket to support just to understand what is happening here. Our DBA seems to think that backup is running but being successful or not is another issue. Veeam shows UNPROTECTED even though it shows data being read and written. 

Yeah that is the route I would take to check with the experts.  At least that way you will know if it is working or not and whether you need to run a full backup.

Hi ​@spider32 I’m facing also the issue that logs are not truncated but I’m considering the following things to upgrade the VBR version to the latest build and upgrade all the Veeam components. I’m trying to run the full backup and you should try to change the job schedule time and disable the job re enable again and check the server role in DB as well.

The full backup ran last night and still getting the same error (Failed to perform internal backup (DBName): Code = 0x80040e31 Code meaning = IDispatch error #3121 Source = Microsoft SQL Server Native Client 11.0 Description = Query timeout expired COM error: Code: 0x80040e31) .

 

At this point, I think changing the log interval to a longer period might help. I have already opened a ticket with support and will just send them the logs. Will let you guys know what they recommend.

 

Thanks again for your inputs.

The full backup ran last night and still getting the same error (Failed to perform internal backup (DBName): Code = 0x80040e31 Code meaning = IDispatch error #3121 Source = Microsoft SQL Server Native Client 11.0 Description = Query timeout expired COM error: Code: 0x80040e31) .

 

At this point, I think changing the log interval to a longer period might help. I have already opened a ticket with support and will just send them the logs. Will let you guys know what they recommend.

 

Thanks again for your inputs.

That is too bad the full did not work.  Keep us posted on what support says and hopefully they address it.

Support gave me 3 registry keys to be added. 2 of the Keys are added on the guest VM and the remaining one on the VBR server. Since we did extensive DB repair, timers have been adjusted to allow transaction logging to work after an image backup.

 

Hive: HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Backup and Replication\

Name: SqlExecTimeout
Type: DWORD
Value: 1800

Name: SqlLogBackupTimeout
Type: DWORD
Value: 3600

 

And for the Veeam B&R server:

Hive: HKEY_LOCAL_MACHINE\SOFTWARE\VeeaM\Veeam Backup and Replication\

Name: SqlConnectionTimeout
Type: DWORD
Value: 1200

Support gave me 3 registry keys to be added. 2 of the Keys are added on the guest VM and the remaining one on the VBR server. Since we did extensive DB repair, timers have been adjusted to allow transaction logging to work after an image backup.

 

Hive: HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Backup and Replication\

Name: SqlExecTimeout
Type: DWORD
Value: 1800

Name: SqlLogBackupTimeout
Type: DWORD
Value: 3600

 

And for the Veeam B&R server:

Hive: HKEY_LOCAL_MACHINE\SOFTWARE\VeeaM\Veeam Backup and Replication\

Name: SqlConnectionTimeout
Type: DWORD
Value: 1200

Let us know how this works and if your backups complete now.  Great to see these posted here to help others with similar issue.

Hi Spider32 or Chris,

 

Did adding the 3 registry keys work?  We have the same issue and Veeam had us add one key yesterday.  Logs still did not get truncated. 

 

Thanks

Hi Spider32 or Chris,

 

Did adding the 3 registry keys work?  We have the same issue and Veeam had us add one key yesterday.  Logs still did not get truncated. 

 

Thanks

Not sure as I will let ​@spider32 comment as he was the one with the issue.

Comment


Terms & Conditions