ProxMox Worker as S3 Gateway?

[squebel]

Hello,

We have a lot of remote office clusters that will be running PVE soon and we are working on protecting them with Veeam and sending data direct to our in house S3 platform. I was hoping the workers could be set up so they would send the data direct to the s3 bucket and not have to go through some separate gateway that we'd have to build for each cluster. Is there maybe something I am missing in the configuration that would allow this?

[Mildur]

Hi squebel,

Unfortunately, Workers cannot be used for any other role at this time.
I recommend deploying a Veeam Infrastructure Appliance (requires Veeam Backup & Replication v13) in each remote cluster and using it as the Gateway Server.

Best,
Fabian

[squebel]

Hi Fabian. Thanks for the reply. Are there any plans to add that functionality in future releases?

[bgagnon]

If I'm reading this right, is this saying the Proxmox Worker can't write directly to S3?

[squebel]

Correct. You need some kind of managed machine that is not a PVE worker that you can set as the remote gateway server. We deployed a small linux vm into each cluster to act as a local repository to hold a couple days worth of restore points and then set up copy jobs to S3 and have the S3 repo set to use that local repository vm as the gateway server.

[Mildur]

It can’t today, but our team has noted it as a potential enhancement for a future version.

Best,
Fabian

[bgagnon]

Interesting - so from an architectural perspective, you need the workers and then another VM that is set up as a proxy with access to S3? So basically Worker -> "Proxy" -> S3? I'm also planning a decent sized S3 repo for Veeam + Proxmox and I was not aware of this, so this is great to read... but also just adds another bump in the road to get to a repo.