Hi,
We started using VeeamJeos as Proxy/Gateway. Sadly there is a big limitation. We can't share it with multiple remote clients, something we do with Windows VM.
Is there any possibility to add this feature with a new version?
Thanks
-
Dric_IT
- Novice
- Posts: 6
- Liked: never
- Joined: Oct 25, 2023 11:47 am
- Contact:
-
Mildur
- Product Manager
- Posts: 11941
- Liked: 3390 times
- Joined: May 13, 2017 4:51 pm
- Full Name: Fabian K.
- Location: Switzerland
- Contact:
Re: Infrastructure Appliance as shared Proxy/Gateway Limitation
Hi,
Sharing of our Infrastructure Appliances will not be possible in the upcoming version. And there are no plans to "enable" this option.
Also, sharing it with multiple remote clients seems wrong from a design perspective and likely from a licensing perspective as well.
Perhaps you can explain your scenario. I believe Veeam Cloud Connect would be the better design choice, but I would first like to understand why you need to share the proxy and gateway server with multiple remote clients.
Best,
Fabian
Sharing of our Infrastructure Appliances will not be possible in the upcoming version. And there are no plans to "enable" this option.
Also, sharing it with multiple remote clients seems wrong from a design perspective and likely from a licensing perspective as well.
Perhaps you can explain your scenario. I believe Veeam Cloud Connect would be the better design choice, but I would first like to understand why you need to share the proxy and gateway server with multiple remote clients.
Best,
Fabian
Product Management Analyst @ Veeam Software
-
Dric_IT
- Novice
- Posts: 6
- Liked: never
- Joined: Oct 25, 2023 11:47 am
- Contact:
Re: Infrastructure Appliance as shared Proxy/Gateway Limitation
Hi,
Also, sharing it with multiple remote clients seems wrong from a design perspective and likely from a licensing perspective as well => Could you explain why?
The use case is: multiple remote sites sending over WAN copy backup to dedicated S3 buckets. We allowed some time range for every client.
The sharing is motivated by the cost of licence of course (Windows..)
Also, sharing it with multiple remote clients seems wrong from a design perspective and likely from a licensing perspective as well => Could you explain why?
The use case is: multiple remote sites sending over WAN copy backup to dedicated S3 buckets. We allowed some time range for every client.
The sharing is motivated by the cost of licence of course (Windows..)
Who is online
Users browsing this forum: AdsBot [Google], Semrush [Bot] and 1147 guests