Database Reference
In-Depth Information
Figure 6.32 vSphere storage policies.
Tip
In vSphere 5.5, you assign tags to data stores and then use those tags to create
storage policies. This is much like using hash tags on social media. They can
easily be searched on afterward and queried or manipulated using orchestration
and scripting (such as PowerCLI).
By pooling multiple (up to 32) similar data stores into data store clusters and using
Storage DRS, you can ensure that initial placement of virtual disks to the best data store
is automated, and this reduces the number of individual elements you need to actively
manage. Storage DRS can be configured to load balance based on capacity, IO
performance, or both, and can be set to simply make recommendations (manual) or be
fully automated. If your array does not include automated storage block tiering, you can
use Storage DRS to load balance data stores for IO performance, in addition to simply
load balancing for capacity. When IO Load Balancing is enabled, Storage DRS works
cooperatively with Storage IO Control and will collect IO metrics from the data stores
and uses the IO injector to determine performance capabilities. The data is then
analyzed periodically (by default, every 8 hours) to make IO load-balancing decisions.
Importantly, the cost of any storage migrations is taken into consideration when making
 
Search WWH ::




Custom Search