Problems with GuestIndexData.zip

[Lerin]

Hi everyone,

Since one month we are having random problems with the backups (sometimes works well, and sometimes report errors and warnings). The support cas ID is: 02114460.

Yesterday we deployed a new veeam server 9.5u1 in a new 2k12R2 upgraded to the last version. and the problem persists
The job reports this errors:

Code: Select all

Processing BCN-VM1 Error: El sistema no puede encontrar el archivo especificado Failed to open file [C:\Windows\TEMP\f34ba1bd-8fae-43ca-9aa8-bdeb96845a7e\GuestIndexData.zip] in readonly mode. Failed to open file [C:\Windows\TEMP\f34ba1bd-8fae-43ca-9aa8-bdeb96845a7e\GuestIndexData.zip] for reading. Failed to backup file. File: [C:\Windows\TEMP\f34ba1bd-8fae-43ca-9aa8-bdeb96845a7e\GuestIndexData.zip]. ItemSpec: [VBK: 'veeamfs:7:db17ca95-813e-4f39-9c54-44e409beb7ae (vm-59)\GuestIndexData.zip@E:\Backups\
Processing BCN-VM2 Error: El sistema no puede encontrar el archivo especificado Failed to open file [C:\Windows\TEMP\4cfb4bdf-032e-45e1-bd15-fc97cbbde343\GuestIndexData.zip] in readonly mode. Failed to open file [C:\Windows\TEMP\4cfb4bdf-032e-45e1-bd15-fc97cbbde343\GuestIndexData.zip] for reading. Failed to backup file. File: [C:\Windows\TEMP\4cfb4bdf-032e-45e1-bd15-fc97cbbde343\GuestIndexData.zip]. ItemSpec: [VBK: 'veeamfs:7:db17ca95-813e-4f39-9c54-44e409beb7ae (vm-61)\GuestIndexData.zip@E:\Backups\
Processing BCN-VM3 Error: Failed to parse block info XML document. Failed to open disk for read. Failed to upload disk. Agent failed to process method {DataTransfer.SyncDisk}. 
Processing BCN-VM4 Error: Failed to parse block info XML document. Failed to open disk for read. Failed to upload disk. Agent failed to process method {DataTransfer.SyncDisk}.

We don't know how to fix it, anybody has the same isue with GuestIndexData.zip file?
Thx!!

[nielsengelen]

Best would be to let support handle this as the snippet doesn't provide enough info to tell which is (might be) the solution.

[Lerin]

Hi,

At the moment seems that the problem was motivated by the proxy (Automatic selection). In our case, Veeam choose automatically the worst proxy (in other site, with lowest comunication bw). Enforcing the localhost proxy, the problem has gone at the moment.
But, we must wait to close the case after the full backup works correctly.

Regards,