Synchronizing Cache Taking Longer than Expected

[tj818]

Hi Team,

Was noticing an issue with VMWare Backups writing to Object First Storage taking longer than expected. Reviewing the Job Details, I saw that there was a long gap between the "Synchronizing cached object storage info... " Phase and "Publishing guest file system index to catalog" Phase.

Synchronizing cached object storage info... - 1:31AM
Publishing guest file system index to catalog - 7:07AM

I found in the VM Task Log, that there was a timeout during what looked to be during a sync process.

Task.<VM-Name>.log:

Code: Select all

[01.02.2026 01:24:01.566]    <33> [000V]    Info (3)    [AP] Waiting for completion. Id: [0x184b728], Time: 00:30:00.0350367
[01.02.2026 01:24:18.845]    <75> [000V]    Info (4)            [AP] (2533f302) output: VCPCommandResult result="false" exception="HTTP exception: WinHttpReceiveResponse: 12002: The operation timed out, error code: 12002
--tr:CS3VersioningUtils::DownloadFileVersionAsync async task has failed, path ["path"/Metadata/StatsCache/CloudStg], version [], offset [0], length [0]

I have a case open with Object First to see why these timeouts are occurring.

I have a Veeam support case (03866762) and inquired about if this type of failure occurs, does a full sync need to take place. The support engineer looks to believe so, but I didn't get a full confirmation

Can anyone confirm if this sync gets an exception that a full sync needs to occur and if so, can this be noted in the job details? Other operations that get this particular type of timeout such as setting the backup files as immutable displays in the Job Details.

Thanks!
Tim

[tj818]

Case 07973537*

[david.domask]

Hi Tim,

I've moved your case to the Object Storage as a Backup Target forum as at first blush the issue sounds more related to Object Storage repositories.

I'm not sure what you mean by "full sync" (Active Full?), but if it's about timeouts to the Object Storage repository, a rescan of the repository ought be enough, if that even is necessary.

Please continue with Veeam Support on the case, as we won't be able to meaningfully troubleshoot such issues over the forums. If you have concerns on the case processing / handling, use the Talk to a Manager button from the case portal to connect with Support Management, they will allocate additional resources as needed for the case.