Different used spaces for the same data

[Pagrossman]

Hi,

this is only question, I didn't create any ticket.

We are using local object repository and backup copy job to AWS object repository.
I don't know why, but the used space in the local object repository is more than 2TB and on AWS only about 500GB even I see that backup copy jobs sent more than 1.5TB.

Does AWS object storage some deduplication/compression that saved more than 75% space, or somewhere is issue?

Thank you,
Jan

[Mike Resseler]

Hey Jan,

That difference is kind of huge to be honest. But to be clear. The local object repository is your primary backup and the AWS repository is the backup copy?

[Pagrossman]

Yes, local object repository is primary storage and AWS is backup copy.

[Polina]

Hi Jan,

1.5TB hardly can be compressed to 500GB. Could you please open a support case to let our engineers investigate it and share the case ID here?

Thanks!

[Pagrossman]

I finished migration of data from file repository to object repository + copied data in Glacier.

It seems that Veeam shows amount of copied data, not real used space.
Now it is ok. Minio shows very similar used space as Amazon and after some restore tests, it seems that all data are there...

So, if somebody have this question, here is answer



I didn't create ticket and now it is not needed by my opinion

[Polina]

Hi Jan,

Good news, thanks for getting back on this!
I'll double-check the accuracy of labels/numbers in the UI, but mainly it's good to see that there're no issues with the data itself.

Cheers!

[Polina]

Jan,

In the console, we display the used space, i.e. real stored data. Which means that either your minio usage from the screenshot is incorrect or there's some problem with minio calculations on our side. Could you please open a support case to check it? Post your case ID here, please, so that I could follow it up.

Thanks!