QNAP QuObjects Backup Issues

[NorthGuard]

I have multiple clients running the latest versions of Veeam, QNAP, and QuObjects... using S3 compatible storage to backup devices.

Two clients have suddenly started throwing the same error when attempting to backup:

Error: REST API error: 'S3 error: The specified bucket does not exist Code: NoSuchBucket', error code: 404 Other: Failed to download disk 'fb3c5edb-27fc-406b-9b11-4e9d7ba825a7'. Reconnectable protocol device was closed. Failed to upload disk. Agent failed to process method {DataTransfer.SyncDisk}

I should add that ALL of the following procedures work without an error:
- scanning repository
- stepping through properties of repository and reconnecting to it
- restoring files from the repository

While I have an open case number, I wanted to be more proactive and see if anyone else is recently seeing anything similar?

[NorthGuard]

Follow-Up:

In waiting for support, I created an entirely new bucket on the QNAP, created a new backup job, and tried to run that. Getting a new error. <sigh>

Error: S3 returned empty versionId for newly uploaded object [/Veeam/Backup/Nightly/Clients/{c0960192-2982-442c-a7db-daaa5fa7e182}/17904c60-9d9a-442d-9d1e-4ccc860670c5/CloudStg/Data/{3fac646b-8fb0-4a9a-9e01-6e8ef8e715f3}/{cee3400a-a64c-4b04-8680-a5cf46eebf85}/36031_fdff183d2c20ef6d511138f9d11e8b56_aded6b7ef6bc3514f845eb858a8be9c7], check that versioning is enabled on the bucket Failed to download disk '0d21721b-d1da-433c-b8d3-566e7377b6b7'. Reconnectable protocol device was closed. Failed to upload disk. Agent failed to process method {DataTransfer.SyncDisk}

I should note that setting up a NFS share on the QNAP and backing up to that works fine.

[totoche]

Hello,
same problem, but it was working before
QTS 5.1.0.2444
QuObjects 2.4.1536

[NorthGuard]

Mine as well as Veeam support has had open tickets since my original post.

Interesting that I am not the only one experiencing it though.

Do you have a workaround yet?

[avdohe]

hi,
same problem here.
Is there any solution?

TS-h886, 16GB, 32TB, QuTS hero, 5.1.0.2446

Axel

[NorthGuard]

No solution and dead silence from Veeam.

For one client, I implemented NFS as a repo on the NAS and that has been solid, so it isn't network related. For another client, i completely ditched the NAS and went with a hardened Linux repo.

But I *really* wish we could get the QuObjects issues fixed.

[Gostev]

This sounds like some S3 API implementation issue on the QNAP side. If this worked before, then perhaps they broke something in a more recent update. As a first troubleshooting step, I would try rolling back QNAP firmware to an earlier one to confirm an absence of the issue.

[NorthGuard]

It has occurred on QNAPs with updated firmware and with firmware that hasn't changed.

I have also already tried rolling back firmware on the ones that it changed with no result.