Skip to main content
  • EN

Hi,  

I have a problem with the transaction log backup.

I have 4 SQL servers in one backup job.  The full backup and incremental backup are running fine.  However, the transaction log backup stop running on Nov 30.  They were running fine before it stopped.  I also have configuration set to run the transaction log backup every 8 hours and it doesn’t run neither.

Here is what i have done and what I observe so far:
1.  I also did something that’s suggested on the internet forum, disable and then enable the backup job.  However, the transaction log backup is still not triggered/started.
2.  It seems like the transaction log backup never starts after the failure on Nov 30.  So there is no report for the transaction log backup after Nov 30.  
3.  The statistic page shows the transaction log backup job failed, not pending.  So, apparently, the transaction log job is stopped or shutdown and won’t re-run
4.  The Veeam server was rebooted last Saturday and it didn't help.
5.  The last time it ran had a failure, the error message (except for the server name, the message is the same in all 4 servers) is 

Failed to retain SQL Server transaction log backups for VM "SQL server name"
Exception has been thrown by the target of an invocation. 
Error: Safe handle has been closed

Any idea how to get the transaction log backup running again.

Thanks.

What version of Veeam are you using?  What OS is the servers?  What version of SQL server?

Did you check the logs - C:\ProgramData\Veeam\Backups\Jobname

Hi Chris,

VBR is version 12.  VBR server is Windows Server 2022 Standard.  I don’t have information for the SQL server.  

I checked the log  - C:\ProgramData\Veeam\Backups\Jobname, the error was on Nov 30 and it seems like the connection was closed by the remote host.  I believe there is something wrong with the network/server on that date.  However, the connection should already be re-established because full backup and incremental are running fine everyday.  But the log for the transaction log backup has nothing after Nov 30 which means it never run after that date.

 

The following is part of the log on Nov 30.  This is the log for the transaction log backup only.

u30.11.2024 17:54:19.086] < 19372> cli      | WARN|MTA invoke thread : timed out for backup events. Wait cycle will be resumed for '336' hours.
'30.11.2024 17:56:03.679] < 18760> cli      | Closing socket device.
30.11.2024 17:56:03.679] < 18760> alg      | WARN|Receiver stage had run into an error. Waiting till connection will be recovered...
l30.11.2024 17:56:03.679] < 18760> alg      | >>  |An existing connection was forcibly closed by the remote host
s30.11.2024 17:56:03.679] < 18760> alg      | >>  |--tr:Cannot read data from the socket. Requested data size: h13].
R30.11.2024 17:56:03.679] < 18760> alg      | >>  |--tr:Receiver stage cycle finished with error
t30.11.2024 17:56:03.679] < 18780> alg      | WARN|Sender stage had run into an error. Trying to recover the connection...
y30.11.2024 17:56:03.679] < 18780> alg      | >>  |An existing connection was forcibly closed by the remote host
a30.11.2024 17:56:03.679] < 18780> alg      | >>  |--tr:Cannot read data from the socket. Requested data size: e13].
o30.11.2024 17:56:03.679] < 18780> alg      | >>  |--tr:Data send queue is broken.
|30.11.2024 17:56:03.679] < 18780> alg      | >>  |--tr:Sender stage cycle finished with error
t30.11.2024 17:56:03.679] < 17192> cli      | Closing socket device.

I am unsure what the issue could be based on this so it might be better to open a support ticket as that will be much quicker for you.

hi ​@vyan 

I’m not sure to understanding your issue. 

But you can consider Full and incremental backup are made directly from vCenter while logs backup via SQL LogShipper, a little component on Guest VM.

Normal troubleshooting I use to check these situations are: 

vssadmin list writers command to check if all VSS on guest server are ok, and free space on disks because transaction log backups are temporarily stored on a SQL server before being transferred to the repository.

Correct connections from Veeam components and 1433 SQL port.

Check (I hope you have configured this role) if log shipping server running correctly.

 

you can see how MSSQL backup works here: 
https://helpcenter.veeam.com/docs/backup/vsphere/sql_backup_hiw.html?ver=120

LEt me know… 

 

 

PS: I’ve just found this… if you use a NFS repo

https://www.veeam.com/kb3131

 

Hi,

I agree in opening a support ticket. Maybe you should check the status of the SQL servers itself. It can happen that VSS services on the SQL site get stuck so that they have to be manually restarted.

It also may happen that the support tells you to get access to the SQL server to check some logs.

 

Maybe the credentials have changed? Could be interesting to know that happened on November 30.

Comment


Terms & Conditions