-
- Service Provider
- Posts: 128
- Liked: 11 times
- Joined: May 15, 2012 9:06 am
- Full Name: Martin Broaders
- Contact:
Hardened Repository in Cloud
Is it fully supported to run a Linux VM in Azure or Amazon as a Veeam Hardened Repository as a location for copy jobs?
-
- Product Manager
- Posts: 9848
- Liked: 2607 times
- Joined: May 13, 2017 4:51 pm
- Full Name: Fabian K.
- Location: Switzerland
- Contact:
Re: Hardened Repository in Cloud
I don‘t see why it is not supported. A Linux Vm in Azure with a xfs partitin will just work like a linux VM onsite.
A VPN connection should be used for the connection.
The performance depends on the connection between Azure and your onpremise datacenter and the type of Azure subscription for your vm.
Why are you not considering Object Storage in Azure Blob (Capacity Tier)?
Because of the missing feature for immutable Flag for objects in Blob Storage?
A VPN connection should be used for the connection.
The performance depends on the connection between Azure and your onpremise datacenter and the type of Azure subscription for your vm.
Why are you not considering Object Storage in Azure Blob (Capacity Tier)?
Because of the missing feature for immutable Flag for objects in Blob Storage?
Product Management Analyst @ Veeam Software
-
- Product Manager
- Posts: 20413
- Liked: 2302 times
- Joined: Oct 26, 2012 3:28 pm
- Full Name: Vladimir Eremin
- Contact:
Re: Hardened Repository in Cloud
Correct, there are no additional limitations brought by such deployment - hardened repository can be deployed in public cloud (AWS EC2 instance, Microsoft Azure VM, etc.)
-
- Chief Product Officer
- Posts: 31814
- Liked: 7302 times
- Joined: Jan 01, 2006 1:01 am
- Location: Baar, Switzerland
- Contact:
Re: Hardened Repository in Cloud
Except it cannot really be truly "hardened" since it will have to have remove management interfaces enabled and thus potentially exploitable.
The bigger question is why would anyone want to go this route for copy jobs, when it is:
1. Less secure than immutable S3 object storage.
2. More expensive than object storage.
The bigger question is why would anyone want to go this route for copy jobs, when it is:
1. Less secure than immutable S3 object storage.
2. More expensive than object storage.
-
- Service Provider
- Posts: 128
- Liked: 11 times
- Joined: May 15, 2012 9:06 am
- Full Name: Martin Broaders
- Contact:
Re: Hardened Repository in Cloud
Thanks all for the replies. I agree with everything said. I have been asked the question by clients who have a preference for Azure and want to keep backups there but also have immutability. Immutability is on everyone's tongue at the moment! We are seeing a huge interest in Wasabi due to the recent certification by Veeam for Object Lock and that is what we are recommending for these scenarios.
Who is online
Users browsing this forum: Bing [Bot], Google [Bot] and 69 guests