Veeam: How to deploy Dell EMC ECS Community Edition (OVA) to have Object Storage on-prem and use it as Cloud/Capacity Tier

Greetings friends, some time ago I showed you all the news of Veeam Availability Suite v9.5 U4, and among them, I have told you in several articles all the power of Veeam Capacity/Cloud Tier, which allows us to take advantage of Object Storage providers to store large numbers of backups that normally require a long retention, months, semesters or years.Many of you, and in the Community, have wondered if you can use storage that we have in our Datacenters that offer Object Storage services, and the answer is YES, of course, as long as the product publishes the S3 service following modern standards should work. Veeam has an unofficial list of products and solutions that you can deploy in your Datacenter.And it's from this list that I've got one of the products that most caught my attention, because of the company behind it, Dell EMC, and because they have a Community Edition, I'm talking about Dell EMC ECS.As this blog entry is quite long, I leave you the menu here to jump wherever you want:

Dell EMC ECS at a Glance

Dell EMC ECS is an industry-leading object storage platform designed to support traditional and next-generation workloads. Available in multiple consumer models: it is defined software and can be purchased as a turnkey device or as a service operated by Dell EMC-ECS. It enables organizations of all sizes to economically store and manage unstructured data at any scale and for any length of time.EMC ECS is an object storage system that makes use of persistent storage containers for cloud storage protocols. ECS supports AWS S3 and OpenStack Swift. In file-enabled buckets, ECS can provide NFS exports for access to file-level objects.We find two main models, in the smallest we can start with a not inconsiderable 60TB and in the largest we can find configurations of up to 8.6PB per rack.As we can imagine what Dell EMC ECS provides us with is object-based storage, scalable and at a reduced price, if we think of an architecture in which a user writes a block using an S3 connector, it would be like this: We see how all nodes are replicated between them, and that only if the block has been stored in all nodes is considered valid.If we thought of a similar operation, but this time reading an S3 block, it would be like this:We see how the request enters through Node 1, which gathers the information of all nodes and at the end it is sent from node 3 to node 1 and from there it is presented to the client.