Hi team,
My customer is planning to use Scality object storage as the repository of Veeam O365. Scality has two different data storing architecture both mirroring and erasure coding. If the size of storing data is less than 60kb (default setting), the data will be stored by mirroring. If the size of storing data is more than 60kb, the data will be stored by erasure coding. The mirroring is faster than erasure coding. However, when it comes to data size efficiency, the erasure coding is better than mirroring. I think it’s better to store the metadata of VBO backup by mirroring for the performance aspects. So my question is which size should I use for the threshold of the two writing methods? Is that ok to leave it as the default setting 60kb?
Thanks,
Yusaku
-
- Influencer
- Posts: 22
- Liked: never
- Joined: Sep 16, 2020 6:46 am
- Full Name: Yusaku Furuhashi
- Contact:
-
- Product Manager
- Posts: 8191
- Liked: 1322 times
- Joined: Feb 08, 2013 3:08 pm
- Full Name: Mike Resseler
- Location: Belgium
- Contact:
Re: Object size of metadata for VBO.
@yusaku
The size of the objects depends on the type of object you store. If you look here, you will see we splitup every object in many pieces: https://helpcenter.veeam.com/docs/vbo36 ... tml?ver=50
Depending on the type, it will be stored in objects of different size.
The size of the objects depends on the type of object you store. If you look here, you will see we splitup every object in many pieces: https://helpcenter.veeam.com/docs/vbo36 ... tml?ver=50
Depending on the type, it will be stored in objects of different size.
Who is online
Users browsing this forum: Bing [Bot] and 16 guests