Feature Request: Proxmox Backup to cloud repository

[edvxpert]

Hi,
we would like to backup Proxmox directly to a cloud repository.

Currently it is only possible to backup to a local repository and add a backup copy job to the cloud repository.

Thank you!

[Gostev]

Hi, have you considered hosting an object storage based repository to achieve the same?

[edvxpert]

Hi,
we have some small customers that do not want to store their backups locally. They want us to keep their backups as we are a cloud connect provider.

[Gostev]

Yes but have you considered hosting an object storage for them to use? Or reselling something like Wasabi? This lets you achieve the same result while avoiding the overhead of managing a cloud connect infrastructure.

[AlexComputerGuy]

I make the same suggestion to Proxmox directly yo Cloud Connect or in my case it's a configured Service Provider ! Have a great day!

---------------------

Here is the ticket that requested that I do a feature request


After reviewing the case history I see that you are unable to select a cloud repository to directly backup a Proxmox host.

Per the link below this is by design. https://helpcenter.veeam.com/docs/vbpro ... html?ver=1

Veeam Backup for Proxmox VE does not support storing backups in Veeam Cloud Connect and HPE Cloud Bank Storage repositories. However, you can use them for storing copies of backups created with Veeam Backup for Proxmox VE. Backup copies can be stored on Cloud Connect repository: https://helpcenter.veeam.com/docs/vbpro ... html?ver=1

At this time, we don't have any information whether direct backup to cloud connect repositories is going to be implemented or not. If this is an important feature for you, I recommend submitting a feature request on our forum https://forums.veeam.com/ by creating a topic marked as FeatureRequest and stating the desired change. Our Product Management Team is actively engaged in the forums and would be happy to discuss your request.

Case # 07466949

[m.roth-bpedv]

We would also like this feature to be available in a future update, since we do actually get customers with proxmox servers wanting a cloud only backup storage, which we currently cannot provide using veeam if we don't have any local backup repository as intermediary for a copy job.

I was kinda hopeful that VBR 13 would support this since the documentation for the Veeam Plug-In for Proxmox 2 did not list Cloud Connect as unsupported anymore (see Archive.org Snapshot) but it has since been updated after I opened a case #03828504 asking about it. Now it once again specifies that direct backups to cloud connect are unsupported.

I'm hoping that there'll be enough demand for them to consider adding direct proxmxo to cloud connect backup support.

[Gostev]

we do actually get customers with proxmox servers wanting a cloud only backup storage, which we currently cannot provide using veeam if we don't have any local backup repository as intermediary for a copy job.

That's not correct though, you can have your Proxmox backup go directly to cloud object storage?

[gerdesj]

As Gostev says: You can do something like Minio, which I do. You can start with one box and scale out as required. There are NASs eg QNAP with it ready to go if you need an easy path to start with.

[edh]

Sometimes it feels like the product is being released with hard-coded limitations that make absolutely no sense—such as blocking users from uploading their data to Cloud Connect repositories. As a cloud provider, this is not just concerning… it's frankly alarming.

How can a feature or plugin be released without proper transfer rates for restores? Is there really no minimum performance threshold before something goes public? Because this looks and feels like a plugin that was pushed out in a rush, without the necessary validation.

Are we seriously expected to rely on nload and manually guess how many terabytes a Gartner TOP 1 solution has transferred? Is this the level of tooling we’re supposed to work with?

And even worse are we supposed to tell our users that they cannot upload directly to the cloud and must spin up a MinIO instance instead… in 2025… in the supposed era of cloud-first everything? This is absurd.

@Gostev, this direction is beyond concerning. It’s a worrying trend, and it undermines the trust and reliability expected from a leading platform.

[Gostev]

There's no "trend" of any kind. V1 will always be V1. It's only goal is to be a minimum viable product to gage the opportunity before I can convince the business to invest into the offering (aka "show me the money"). Until this happens, I have to find spare resources here and there but ultimately there's not much manpower to work with.

Sorry if this results in sharp corners but the reality is, Proxmox is still the fastest growing workload for Veeam so it would seem we're making largely right calls when it comes to delivering minimum viable product with very limited R&D resources.