Using hardware for capacity or archive purpose

[DanielB_Ger]

Dear all,

I have a question regarding Capacity Tier within a Scale-out Repository:

Within an existing infrastructure we changed the hardware for local Backup Repositories, now using faster machines.
Since the formerly used machines are not out of date we thought about using them for some long term retention data.

Now the Capacity Tier is cloud-only. But would there be any possibility to use some local storage for this purpose instead?
I mean for performance one probably uses more expensive machines and disks, but for some long term retention why not use less performant hardware which has a lower cost as well?

So far I don't see any possible way for this. So either I just didn't see it or this will end as a feature request at best.
Anyway thanks in advance for your reply!

Best regards,
Daniel

[Mildur]

Hi,

Capacity tier is not cloud Only. It can also be an onpremise Object storage. You could use min.io or something similar.

But why not use the old hardware as a linux hardened repo with immutability? Use a backup copy job to deliver the backup files to the hardened repo.
I think, it will give you a better performance as building you own s3 object storage. And it‘s simpler to manage.

[DanielB_Ger]

Hi Mildur,

Thanks for the quick reply!
I'll take a look into both scenarios immediately. Maybe s3 would fit our current goal better, but the alternative with Linux hardened repo you mentioned doesn't sound bad either.

Since it will take some time to come up with a plan which then has to be executed, this topic may be closed. Otherwise I could update this once we decided and implemented one or the other scenario.

Best regards,
Daniel

[Mildur]

Hi Daniel

Your welcome.
Yes, please update the topic about your decision, if you like. That could help others with a similar question