What are the drawbacks/reasons users shouldn implement thin provisioning?
Thin provisioning is not a magic elixir to solve your problems at the storage site and it’s not a substitute for sloppy storage management practices. In many cases, storage is just provisioned in an ad hoc manner and there is very little effort that goes into ensuring that storage is being provisioned the right way, that the server is using it the right way, and that you have control over how it gets provisioned. Thin provisioning does not solve these problems. You need to have a tight storage discipline and then thin provisioning will enhance the value of that discipline. It is also not a magical solution to reclaim all unused storage. What I really mean is that it is very easy to fall into the trap and say that if I have 100 terabytes and if I provision 200 terabytes, I am really getting 200 terabytes. Not really. If all of the 200 terabytes are required by the servers, then you will physically need 200 terabytes. It’s not a magical solution that suddenly gives you two times more sto
Related Questions
- How does the proposed legislation implement the SCC decision regarding reviews of the reasons for continuing to detain individuals?
- Does my organisation need to fully implement OLM in order to access elearning and do users still need to be set up if it is not?
- What are the drawbacks/reasons users shouldn implement thin provisioning?
