backup to Azure "Waiting for next task"

[peeky1323]

Hi All. After upgrade to V12 we have just setup a repository in Azure for direct back to Azure. We already had with V11 an SOBR with an immediate offload to to capacity tier in Azure which still runs just fine. This new repository is a new folder in the same container. When I target a job at the new repository the job just sits there forever with a status of "Waiting for the next task". Any ideas? TIA, Matt

[Mildur]

Hello,

That sounds like a technical issue. Please provide a support case ID for this issue, as requested when you click New Topic.
Without case number, the topic will eventually be deleted by moderators.

Support will be able to tell you why tasks are not available. Does this happen with direct connection method or through gateway server?

Best regards,
Fabian

PS: support can only help if you upload logs https://www.veeam.com/kb1832

[peeky1323]

FYI - I changed the object repository connection from "Direct" to use the Gateway of the server that connects to the repository. It's now working. The previous SOBR offload that I thought was working was also stuck so I made this change to that REP and it is also now working.

[Gostev]

Well, this is really weird because one of our goals for V12 was to avoid additional hops through gateways and enable customers to go direct to object, so it should certainly work...

[doktornotor]

Same story with Wasabi and backup copy jobs (no SOBR). Nothing gets done with "Direct".