Database Reference
In-Depth Information
Care should be taken when implementing Storage DRS on backend storage that is
thin provisioned if it doesn't include data de-duplication capabilities. Traditional
thin provisioned backend storage capacity could become full if a storage
migration takes place between one thin provisioned data store and another if the
space is not reclaimed. Because the IO injector is used to determine performance
capabilities when IO metric collection is enabled, it should not be used with
auto-tiering arrays because the data it gathers will be inaccurate and your array is
already managing the performance of each LUN. In the case of auto-tiering arrays,
you should only use Storage DRS for initial placement and capacity-based load
balancing.
The example in
Figure 6.34
shows the Storage DRS Advanced Options expanded. Here,
you can set whether to keep VMDKs together by default and other settings. These
parameters will influence how much of an imbalance there needs to be before Storage
DRS will consider taking action. The most relevant settings for SQL Server are “Keep
VMDKs together by default” and the advanced option shown in this figure,
“IgnoreAffinityRulesForMaintenance.”
