What happens with a failed offload to S3 Wasabi?

[TonioRoffo]

Hello,

After 40h of offload over a really slow line, I got the following error from Veeam:

Code: Select all

23/09/2022 11:23:39 :: Processing File Servers FP01 Error: HTTP exception: WinHttpWriteData: 12030: The connection with the server was terminated abnormally
, error code: 12030
Shared memory connection was closed.

At that moment, 57GB were written to Wasabi S3.
The job didn't retry, it just closed with an error. No offloaded objects visible on "Object Storage"

To retry the offload, I've done an incremental run on said FP01 server and the offload started again. However, it seems to be starting again from 0%, at the same speed. I would assume the already written blocks would be recognized somehow?

* Does Veeam simply start again from scratch?
* What about the 57GB written data which is immutabe for 30 days?
* Is there no resiliency for temporaty internet connection issues?

Thanks for your feedback.

[TonioRoffo]

Resync gives me the following error:

Code: Select all

23/09/2022 14:26:07 Warning    Failed to import backup File Servers. Item [6bb99f79-371e-4410-8ad3-f0bc05815c93] is locked by running session File Servers Offload [SOBR Tiering]
23/09/2022 14:26:14 Warning    Smartsys Wasabi: Failed to synchronize 1 backups.
23/09/2022 14:26:17 Warning    Backup repositories synchronization completed with warnings

So that data is simply "lost"?

[sfirmes]

@TonioRoffo have you opened a support ticket with Veeam Support for this issue? If so, could you please note what it is?

[TonioRoffo]

I will do so, as soon as I have access to create a ticket in my client's name.