Skip to main content
  • EN

I have one job that started failing to create synthetic fulls on weekends.   The job runs just fine M-F creating incremental backups. 

I have another job that also creates synthetic full backups over the weekend.  And that job finishes with no errors.  So I know it’s not my NAS (Qnap) that is having issues.

So why is it doing this for only the one job?   Error log below.

 

02.02.2025 16:57:48.444]    <43>   Error (3)    Failed to execute full transform task
f02.02.2025 16:57:48.444]    <43>   Error (3)    Agent: Failed to process method {Transform.CompileFIB}: The semaphore timeout period has expired.
d02.02.2025 16:57:48.444]    <43>   Error (3)    Asynchronous request operation has failed. srequestsize = 700416] .offset = 1242582327296]
e02.02.2025 16:57:48.444]    <43>   Error (3)    The semaphore timeout period has expired.
e02.02.2025 16:57:48.444]    <43>   Error (3)    Asynchronous request operation has failed. nrequestsize = 540672] hoffset = 1242583027712]
602.02.2025 16:57:48.444]    <43>   Error (3)    The semaphore timeout period has expired.
a02.02.2025 16:57:48.444]    <43>   Error (3)    Asynchronous request operation has failed. Ârequestsize = 712704] ooffset = 1242583568384]
s02.02.2025 16:57:48.444]    <43>   Error (3)     (System.AggregateException)
02.02.2025 16:57:48.444]    <43>   Error (3)    Agent: Failed to process method {Transform.CompileFIB}: The semaphore timeout period has expired. (Veeam.Backup.Common.CCppComponentException)
r02.02.2025 16:57:48.444]    <43>   Error (3)    Asynchronous request operation has failed.  requestsize = 700416] roffset = 1242582327296] (Veeam.Backup.Common.CCppComponentException)
802.02.2025 16:57:48.444]    <43>   Error (3)       in c++: Error code: 0x00000079
;02.02.2025 16:57:48.444]    <43>   Error (3)    The semaphore timeout period has expired. (Veeam.Backup.Common.CCppComponentException)
02.02.2025 16:57:48.444]    <43>   Error (3)    Asynchronous request operation has failed.  requestsize = 540672] offset = 1242583027712] (Veeam.Backup.Common.CCppComponentException)
02.02.2025 16:57:48.444]    <43>   Error (3)       in c++: Error code: 0x00000079
402.02.2025 16:57:48.444]    <43>   Error (3)    The semaphore timeout period has expired. (Veeam.Backup.Common.CCppComponentException)
e02.02.2025 16:57:48.444]    <43>   Error (3)    Asynchronous request operation has failed. requestsize = 712704] ;offset = 1242583568384] (Veeam.Backup.Common.CCppComponentException)
s02.02.2025 16:57:48.444]    <43>   Error (3)       in c++: Error code: 0x00000079
202.02.2025 16:57:48.444]    <43>   Error (3)       in c++: Failed to process de-duplicated block
02.02.2025 16:57:48.444]    <43>   Error (3)       in c++: Failed to write block to blocks store.

Hi ​@bobs143 - Welcome to the Community.

Not sure if we can help here..we’re not support. But maybe we can at least give some ideas. I recommend still opening a Support case though. Thank you for sharing what your logs say, but what is the specific error the Job displays? That may help pinpoint a definitive error instead of guessing over several from the log you posted. Also, I assume this is a regular backup job? And, what Veeam version are you on?

Best.

​@bobs143 -

Did you also post in the Forums? I see a similar post there from yesterday.

https://forums.veeam.com/veeam-backup-replication-f2/synthetic-backup-creation-keeps-failing-t97381.html

It appears you do have a Support case open? I recommend waiting to hear from them on your issue.

I am on version 12.3.    

 

The error is.     

Agent: Failed to process method {Transform.CompileFIB}: The semaphore timeout period has expired. Asynchronous request operation has failed. srequestsize = 700416] =offset = 1242582327296] The semaphore timeout period has expired. Asynchronous request operation has failed. srequestsize = 540672] =offset = 1242583027712] The semaphore timeout period has expired. Asynchronous request operation has failed. srequestsize = 712704] =offset = 1242583568384]

 

I have submitted a case, but frustrated that this seems to be an issues with the one job only. 

 

A case is currently open.

Hi ​@bobs143 -

Yeah..I can understand that. I would go ahead and wait for Support. In my brief searching, I did see a somewhat similar issue (slightly diff error), and the resolution required a registry fix. This was from 2019 though so I’m sure a fix is already a part of the current VBR version. That said, what you have going on may require the same, and Support is the only ones who would be able to give this to you.

Keep us posted.

Thanks for your help.

How is your NAS connected to your VBR - with what protocol?  iSCSI, FC, NFS?  There have been posts about offset errors due to protocols that I have seen.  But you are best to wait on Support as Shane has noted.

It’s connected using SMB.   So potentially that is an issue also.  I like to change it over to iSCSI and use fast clone.  But would need to plan that out, and need to get past the current issue first. 

It’s connected using SMB.   So potentially that is an issue also.  I like to change it over to iSCSI and use fast clone.  But would need to plan that out, and need to get past the current issue first. 

Do you happen to have another target you can send the backup to like local storage?  This will get you a backup until you can get the NAS connected via iSCSI.  If you check the forums there are posts about SMB issues like this not sure if there is an answer there.

Comment


Terms & Conditions