V12 - direct copy object storage - waiting for next task

[frankive]

In my lab I have a clean VBR V12 setup with Wasabi object storage.
Trying to create a backup job to wasabi directly, but when executing the job it gets stucked at "waiting for next task" and "queued for processing".
There is no other jobs on this server..
Any ideas what could cause this?

[Dima P.]

Hello Frank,

When saying direct copy object storage you mean backup copy or regular VM backup job? What is set as a job source? Can you please also clarify how your object storage is configured i.e. does it have a gateway assigned or not? Thank you!

[frankive]

Its a regular vm backup job directly to wasabi. The source is a vm running on the same hyper-v server veeam is running on.
Connection mode is Direct.

Created a case with following casenumber with logs:

# 05878877

[frankive]

update: after edit from Direct to use Gateway it started to work.
Isnt Direct that the Veeam server just should be able to connect to the Internet directly?

[Gostev]

It's direct from a backup proxy, Veeam server does not participate in the data movement.
Pretty sure I documented this in the What's New document, like in the very first bullet

[frankive]

OMG, I actually read the whole document.. guess it was much to remember on the first reading..