I just have a little question,
What about impact of replication on auto-tiering array ? Do the replication via VMware CBT impact tiers level choice ?
Thx
-
- Expert
- Posts: 245
- Liked: 58 times
- Joined: Apr 28, 2009 8:33 am
- Location: Strasbourg, FRANCE
- Contact:
-
- Chief Product Officer
- Posts: 31805
- Liked: 7299 times
- Joined: Jan 01, 2006 1:01 am
- Location: Baar, Switzerland
- Contact:
Re: Replication and auto-tiering
I am sure this would depend on the specific array and the logic the array's vendor uses for tiering... you should check with the specific vendor what kind of workloads trigger tier changes.
-
- Expert
- Posts: 245
- Liked: 58 times
- Joined: Apr 28, 2009 8:33 am
- Location: Strasbourg, FRANCE
- Contact:
Re: Replication and auto-tiering
EMC VNX (5200).
Do you have some feedback on this kind of system (VNX) ?
Do you have some feedback on this kind of system (VNX) ?
-
- VeeaMVP
- Posts: 6166
- Liked: 1971 times
- Joined: Jul 26, 2009 3:39 pm
- Full Name: Luca Dell'Oca
- Location: Varese, Italy
- Contact:
Re: Replication and auto-tiering
I remember there are some VNX users in these forums, just wait and see if someone wants to jump in.
Generally speaking, maybe the I/O produced by Veeam is going to change the calculations made by the tiering algorytm, but "how" it's going to react is up to the given storage array. As an example, on other storage system where tiering is scheduled, we usually configure it to be executed outside of the veeam operations timeframe.
But this is imho more about not stressing even more the storage, because about the moving of hot blocks from low to high tier, I would say a Veeam backup is not going to change the "score" of a block, since it's only read once per job. If an algorythm is going to move a block up in a tier only after one read, it's not such an optimized algorythm if you ask me.
On the other side, if you are going to read a block that is already inside the high tier, well you're simply getting it faster...
Luca.
Generally speaking, maybe the I/O produced by Veeam is going to change the calculations made by the tiering algorytm, but "how" it's going to react is up to the given storage array. As an example, on other storage system where tiering is scheduled, we usually configure it to be executed outside of the veeam operations timeframe.
But this is imho more about not stressing even more the storage, because about the moving of hot blocks from low to high tier, I would say a Veeam backup is not going to change the "score" of a block, since it's only read once per job. If an algorythm is going to move a block up in a tier only after one read, it's not such an optimized algorythm if you ask me.
On the other side, if you are going to read a block that is already inside the high tier, well you're simply getting it faster...
Luca.
Luca Dell'Oca
Principal EMEA Cloud Architect @ Veeam Software
@dellock6
https://www.virtualtothecore.com/
vExpert 2011 -> 2022
Veeam VMCE #1
Principal EMEA Cloud Architect @ Veeam Software
@dellock6
https://www.virtualtothecore.com/
vExpert 2011 -> 2022
Veeam VMCE #1
Who is online
Users browsing this forum: Bing [Bot], Google [Bot], ken.tyrrell, LaurentiuChiva, mbrzezinski and 120 guests