Hitachi Command Suite 8 User Guide

							From the Actions list in the application pane, select  Element
Manager . Refer to the documentation for the native management tool
for your storage system.
3. In CLPR  on the  Migrate CLPR Resources  window, select the CLPR
number to which the resource is assigned.
4. In CU , select the CU to which the resource is assigned.
5. In Available Parity Groups  or Available Virtual Volumes , select the
resource that you want to migrate, and then click  Set>. This adds the
selected resource to the  CLPR table.
To check the information of the CLPR, select the CLPR and click  Detail to
open the  CLPR Properties  window.
6. When you are done adding resources to migrate, click  Finish.
7. On the  Confirm  window, check the settings carefully.
8. Click  Finish .
9. When you are ready to start the resource migration, enter the task name
in the  Confirm  window, and then click  Apply.
Result The specified resources are migrated.
Related tasks
•
Editing the settings of an existing CLPR  on page 321
•
Creating a CLPR  on page 318
Editing the settings of an existing CLPR You can change the following settings after creating a CLPR:• CLPR name
• Total cache size
• Resident cache size
• Number of resident cache extents
Procedure 1. On the  Resources  tab, expand the  Storage Systems  tree, and select
the target storage system.
2. Choose one of the following options.
• For Virtual Storage Platform G1000 storage systems: Select  Cache Partitions .
• For other available storage systems: From the  Actions list in the application pane, select  Element
Manager . Refer to the documentation for the native management tool
for your storage system.
3. On the  Cache Partitions  tab, select the CLPR to be edited, and then
click  Edit CLPR  to open the  Edit CLPR window.
Optimizing storage performance321Hitachi Command Suite User Guide 
						

							4.Edit the CLPR settings as follows. The CLPR number cannot be changed.
a. In  CLPR Name , edit the CLPR name as needed. You can use up to 16
alphanumeric characters but you cannot specify CLPR names that are
already reserved.
b. In  Total Cache Size , edit the CLPR cache capacity as needed. The
minimum cache size is 8 GB, and the size can be changed in
increments of 4 GB. The maximum available capacity (by subtracting the total usage capacity of other CLPRs from the total capacity of the
storage system) is displayed as the maximum size. The remaining
cache capacity (by subtracting the resident cache size from the total cache size) must be 8 GB or more. Ensure that the remaining capacityin CLPR0 is at least 8 GB when selecting the total cache size or resident cache size.
c. In  Resident Cache Size , edit the resident cache capacity as needed.
The minimum size is 0 GB, and the size can be changed in increments
of 0.5 GB. The maximum available capacity (by subtracting the total usage capacity of other CLPRs from the total capacity of the storage
system) is displayed as the maximum size. If resident cache exists in
the selected CLPR and you select a resident cache size that is smaller
than the existing resident cache, an error will occur. Before decreasing the size, check the resident cache capacity set in the selected CLPR.
d. In  Number of Resident Extents , edit the number of resident cache
extents as needed. You can specify from 0 to 16384. The maximum
available capacity (by subtracting the total usage capacity of other
CLPRs from the total capacity of the storage system) is displayed as
the maximum value. If resident cache exists in the selected CLPR and
you select fewer resident cache extents than the existing number of extents, an error will occur. Before decreasing the number, check the
number of resident extents set in the selected CLPR.
5. When you are done editing the CLPR settings, click  Finish.
6. On the  Confirm  window, check the settings carefully.
7. When you are ready to change the settings, enter the task name in the
Confirm  window, and then click  Apply.
Result
The specified resources are changed.
Related tasks
•
Adjusting the cache capacity of a CLPR  on page 322
•
Creating a CLPR  on page 318
Adjusting the cache capacity of a CLPR You need to adjust the cache capacity of a CLPR when Cache Residency
Manager operations decrease the cache capacity of the CLPR.
322Optimizing storage performanceHitachi Command Suite User Guide 
						

							Procedure1. Cancel the Cache Residency Manager bind mode or priority mode setting.
2. Edit the settings of an existing CLPR to change the cache capacity of the
CLPR.
3. Set the bind mode or priority mode again.
Result
The cache capacity is adjusted.
Related tasks
•
Creating a CLPR  on page 318
•
Editing the settings of an existing CLPR  on page 321
Deleting a CLPR You can only delete CLPRs that you created. CLPR0 cannot be deleted.
Caution: The delete CLPR operation deletes all resources and data in the
CLPR. Before deleting a CLPR, migrate all resources that you want to keep
(for example, parity groups) to another CLPR that will not be deleted.
Procedure
1. On the  Resources  tab, expand the  Storage Systems  tree, and select
the target storage system.
2. Choose one of the following options.
• For Virtual Storage Platform G1000 storage systems: Select  Cache Partitions .
• For other available storage systems: From the  Actions list in the application pane, select  Element
Manager . Refer to the documentation for the native management tool
for your storage system.
3. On the  Cache Partitions  tab, select the CLPR that you want to delete,
and then click  Delete CLPRs  to open the Delete CLPRs  window.
4. In the  Selected CLPRs  table, check the CLPR that you want to delete. If
you want to cancel the deletion, click  Cancel to go back to the  Cache
Partitions  tab.
5. Click  Apply .
Result
The CLPR is deleted.
Related tasks
•
Migrating resources to and from a CLPR  on page 320
Optimizing storage performance323Hitachi Command Suite User Guide 
						

							Data mobilityAn administrator can obtain information required to see the operating status
of storage resources and optimize data placement.
About data mobility The Mobility tab provides information required to see the operating status of
storage resources and optimize data placement.
To efficiently use a storage resource, use the Mobility tab to optimize the data arrangement. In the Mobility tab, information used to determine whether the
data arrangement is appropriate is collectively displayed. In addition, you can
use the Mobility tab to centrally perform operations regarding moving data
such as data migration. To use the Mobility tab, you must first register a Tiered Storage Manager license. Using Mobility tab information, you can
evaluate and analyze whether the hardware tiers are being used
appropriately and whether the volumes are providing the expected performance. Based on these results, you can optimize data placement by
migrating data and setting up an HDT tiering policy (which specifies the
hardware tiers in which volumes are to be placed). After completing these
operations, check their effect from the Mobility tab and then perform any
other necessary data optimization operations. By repeating this process, the
placement of data can be optimized. The following figure shows the process of optimizing data placement.
From the Mobility tab, data placement can be optimized from either the
application (logical group) perspective or from the DP pool perspective. To
respond to requests from host or application administrators, or to confirm whether HDT pools and storage resources are being used according to the
needs of each application, check the balance between the performance and
the configuration ratio of logical groups. To regularly monitor storage
resources, or if there is a problem in the analysis of logical groups, check the balance between the performance and the configuration ratio of each DP pool. If there is a problem, you must check the operating status of each
volume in the DP pool and then optimize the configuration.
324Optimizing storage performanceHitachi Command Suite User Guide 
						

							When periodically monitoring logical groups or DP pools during routine work,check the ranking reports in the Mobility tab so you can efficiently find logical groups or DP pools that have problems in their operational status.
The Mobility tab can be used to check the total capacity and usage rate for
each logical group, DP pool, or each volume in a logical group or DP pool. As with HDT pools, you can also check which volumes are using the largest
proportions of each hardware tier. In addition, the following performance information can also be viewed:
• Quantity of I/O operations compared to the calculated maximum number of I/O operations
In addition, if linked with Hitachi Tuning Manager, the following performance information can also be viewed:
• Throughput (IOPS) for DP pools, volumes, and hardware tiers
• Past volume performance data (to look for trends) • Response time of the volume
• Busy rate for parity groups
For details on linking to Hitachi Tuning Manager, see the  Hitachi Command
Suite Administrator Guide .Note: If Hitachi Tuning Manager is not linked, or information cannot be
obtained due to storage system type, or the Tuning Manager - Agent for RAID software version, hyphens are displayed in performance information columns.
From the Mobility tab, the following operations can be performed to optimize
data placement:
• Configuring and editing of an HDT tiering policy
• Migrating volumes • Manually starting or stopping the monitoring and relocation of HDT pools • Editing tier relocation of HDT volumes • Expanding, shrinking, or changing settings for DP pools
• Expanding DP volumes and reclaiming zero pages
• Referencing trend charts, which indicate capacity data and performance data for DP pools, and exporting data to CSV files
By creating tiers of volumes or DP pools based on use or performance, you can migrate data to volumes or DP pools that match the relevant conditions
simply by specifying a tier as the migration target.
Related tasks •
Optimizing data placement in a logical group  on page 328
•
Optimizing data placement in a DP pool  on page 329
Optimizing storage performance325Hitachi Command Suite User Guide 
						

							Reports for logical groups displayed in the Mobility tabSeveral reports are available on a logical group basis for monitoringperformance related items such as response time and unused capacity.
You can display one of the following ranking reports for a logical group in the
Mobility tab by selecting a top folder of the Public or Private folder, and a top-
level folder for each user group under the Private Logical Group folder:
• Bottom 10: Logical Groups with High Response Time
Checks for logical groups including volumes whose response time is slow.Used to determine logical groups which do not satisfy required performances. This ranking is displayed only when you have the license for
Hitachi Tuning Manager.
• Top 10: Logical Groups with Lowest Unused Capacity
Checks for logical groups that have little unused capacity left for the
allocated DP volumes. Used to determine logical groups which do not have
enough capacity.
• Top 10: Logical Group Used Capacity by Drive Types
Checks for logical groups that use a large amount of capacity by drive
type. Used to determine whether an unexpected volume is occupying a
high-speed drive or logical groups which have invalid data arrangements.
The following summary information is displayed when each logical group is
selected:
• Summary
Provides summarized information in a list, such as the number of volumes
and the total capacity of a logical group, or the last update date. Based on this information, you can review the usage status of the storage resources
in the logical group.
• Drive Type Summary
Checks whether the logical group has the necessary capacity. Checks thetotal capacity of the volumes and the used capacity of each drive type
within the logical group.
• Drive Type Distribution
Checks how many of each drive type is used for each DP pool that is
included in a logical group. Used to check whether the configuration of the
hardware tier is appropriate.
Related concepts
•
About data mobility  on page 324
Reports for DP pools displayed in the Mobility tab The Mobility tab displays several types of reports for DP pools related toperformance and capacity utilization.
Ranking reports for DP groups displayed in the Mobility tab are as follows: • Top 10: Pools with the Highest Used %
326Optimizing storage performanceHitachi Command Suite User Guide 
						

							Check on a regular basis for DP pools with a high capacity usage rate todetermine DP pools that need pool expansion or data migration.
• Top 10: Pools with the Highest Subscription
Check on a regular basis for DP pools with a high reservation rate to
determine DP pools that need pool expansion or data migration on a regular basis.
• Top 10: Tiers with the Highest Performance Utilization
Check on a regular basis for hardware tier configurations with high ratio ofactual I/O operations to the calculated maximum number of I/O
operations. Used to determine HDT pools that include hardware tier
configurations with saturated performance.
The information displayed when each DP pool is selected is as follows: • Summary
Summarizes information in a list, such as the total capacity and usage of DP pools, and the reservation rate. Based on this information, you can
review the usage status of the DP pool.
In addition, you can determine whether you need to add capacity to the
DP pool by selecting Show Trend Chart from the Actions menu, and then
checking each pool's trends in the increase of IOPS and in capacity usage.
You can change the display period of the trend chart as needed, or save
the trend chart as a report after exporting it to a CSV file.
If an HDT pool is selected, the following information can also be viewed:
• Tier Summary
Check information such as drive type, drive rotational speed, and capacity
usage rate for each hardware tier. Based on this information, you can
review the usage status of hardware tiers. Note that this summary only
appears for HDT pools.
• Capacity & Performance Utilization
Check the total capacity and used capacity of the HDT pools for each hardware tier. This lets you confirm whether the HDT pool has the
necessary capacity and identifies which hardware tier needs more capacity
added to it. This summary only appears for HDT pools. For example, if
capacity is increasing, but IOPS shows little change, then adding more
capacity for future use is suggested with this capacity added to Tier 2 or
Tier 3. If capacity shows little change, but IOPS is increasing, then adding
more capacity for future use is suggested with this capacity added to the upper tiers (Tier 1 and Tier 2), or reducing Tier 3 by the amount needed.
If both capacity and IOPS are increasing, then adding more capacity for future use is necessary. You can determine to which tiers this capacity is
added based on the trend graph and distribution chart for each tier.
• Show Trend Chart
Check the trend chart, which combines and displays the capacity usage and performance information for each hardware tier. Based on this information, you can determine whether the hardware tier configuration in
the HDT pool is appropriate, and which hardware tiers need additionalOptimizing storage performance327Hitachi Command Suite User Guide 
						

							capacity. You can change the display period of the trend chart as needed,
or save the trend chart as a report after exporting it to a CSV file. If the
display period of the trend chart is seven days or more, the chart displays
the average of the obtained information for each day.
• Capacity Utilization
Check the total capacity and used capacity of the HDT pools for each
hardware tier. Based on this information, you can check whether the HDT
pool has the necessary capacity. You need to perform capacity planning for
pools in which the remaining capacity is small. Look at the trends for how
pool contents increase, and estimate when you must increase capacity,
and possibly add additional media.
• Performance Utilization
Check the ratio of actual I/O operations to the calculated maximum number of I/O operations for each hardware tier. Based on this
information, you can determine the hardware tiers whose performance is
in a saturated state that then require an optimization operation (such as
editing the tiering policy or data migration).
• Top 10: Volumes Sharing Tier Capacity
Check the usage ranking of volumes that have the largest use capacity in
each hardware tier. Based on this information, you can check whether data
placement is appropriate, for example by checking whether an unexpected
volume is occupying a high-speed drive. This summary only appears for
HDT pools.
• View Tier Properties
Check the page access distribution per average number of I/O operations,
which is based on the monitoring information of HDT pools.
Based on this information, you can check whether the hardware tier
configuration or tiering policy settings are appropriate.
From the page access distribution for HDT pools, you can narrow the range
of displayed items to only tiering policies or only HDT volumes, as
required.
Related concepts
•
About data mobility  on page 324
Optimizing data placement in a logical group Data placement can be optimized in either of the supported logical grouptypes (Public Logical Groups or Private Logical Groups).
Prerequisites
• A registered Tiered Storage Manager license.
• A registered Hitachi Tuning Manager license (when referencing performance information).
328Optimizing storage performanceHitachi Command Suite User Guide 
						

							Procedure1. From the tree view of the  Mobility tab, select  Logical Groups .
2. From  Logical Groups , select either Public Logical Groups  or Private
Logical Groups , and in the logical group ranking, check for logical
groups that are responding late, have a small unused capacity, or have a
large used capacity for each drive type (for example: FMD, SSD, SAS, or
SATA).
3. If the capacity or performance of the entire logical group is not
satisfactory, click the link of the logical group name to check the totalcapacity of the volumes and the used capacity of each drive type (for
example: FMD, SSD, SAS, or SATA) within the logical group. If the
Hitachi Tuning Manager license is registered, click the  Analyze
Performance  button to check performance information as required.
4. If the balance between the logical group performance and configuration
ratio is not satisfactory, select the row of the target volume, and click
Migrate Data , Edit Tiering Policy , or one of the other buttons to
remedy the problem.
5. Select  Logical Groups  from the Mobility tab to check optimization of
the data placement.
Related concepts
•
About data mobility  on page 324
Related tasks •
Optimizing data placement in a DP pool  on page 329
Optimizing data placement in a DP pool Data placement can be optimized in a DP pool.
Prerequisites
• A Tiered Storage Manager license must be registered.
• A Hitachi Tuning Manager license must be registered (when referencing performance information).
• Ensure that HDT pools are being monitored (when referencing Performance Utilization, IOPS for a hardware tier, or View Tier Properties).
Procedure 1. From the tree view of the  Mobility tab, select  DP Pools.
2. Select  DP Pool  to check for DP pools whose usage rate, reservation rate,
or performance usage rate is high.
3. If a DP pool does not meet the expectations for capacity or performance,
click the link of the DP pool in the ranking.
4. Check the usage status and performance of each hardware tier in the DP
pools by performing the following:
Optimizing storage performance329Hitachi Command Suite User Guide 
						

							• To check if the usage capacity of the HDP pool is appropriate, from theActions  menu, select  Show Trend Chart , and then check the IOPS
and usage capacity of each pool.
• To check if the configuration and performance of each hardware tier in the HDT pool is appropriate, from the  Actions menu (or from the
Capacity & Performance Utilization  link), select Show Trend
Chart , and then check the capacity and performance of each
hardware tier. To save the contents of the Trend Chart as a report, click  Export to CSV  and save the contents as a CSV file to a location
of your choice.
• To check page access distribution per average number of I/O operations, from the  Actions menu, select  View Tier Properties .
5. Select the DP volumes that have a problem and optimize the data
placement by clicking:
• Migrate Data
• Edit Tiering Policy
• Expand DP Volume , or one of the other buttons
6. On the  Mobility  tab, select  DP Pools to confirm data placement
optimization.
Related concepts
•
About data mobility  on page 324
Related tasks
•
Optimizing data placement in a logical group  on page 328
Data migration This module describes data migration.
About data migration Data migration involves moving data from a set of source volumes to a set ofdestination volumes or DP pools, including those in externally-connected
storage systems.
For example, you can migrate data when your volume performance decreases
or your environment changes. When relocating data based on the results of performance monitoring for volumes being used by servers and applications,
or when migrating data from an old storage system to a newly set-up storage
system, the data in multiple volumes can be migrated to other volumes or DP
pools.
The source volume can be selected by host, file server or by logical group. The source volume also can be selected from some of the volumes allocated
to a host, file server, some of the volumes displayed in the list of volumes in
the file server, some of the volumes in a logical group, some of the volumes
330Optimizing storage performanceHitachi Command Suite User Guide