154 ILM Library: Techniques with Tivoli Storage and IBM TotalStorage Products
8.1 Moving from the initial ILM scenario
With the initial ILM implementation explained in Chapter 7, “ILM initial implementation” on
page 119, we related the data placement to the initial value of the data. This means that each
data class is mapped to a certain storage tier (based on input received from the service level
management process), and that these mappings are static in overtime (see Figure 8-1). In
addition, mapping was performed at the logical volume level, meaning that data class
granularity was limited.
Figure 8-1 Initial static ILM implementation
As a second step, we maintain the static mapping over time, but we add a function that allows
automatic data placement as a function of its data class, thus enforcing mapping the correct
data class to the correct storage tier (see Figure 8-2 on page 155). In addition, we will allow
data classes to become more detailed, adding individual data types rather than individual
applications or systems (which was done in Chapter 7, “ILM initial implementation” on
page 119).
Service Level
Management
Tier 1
Data
Class 1
Tier 2
Data
Class 2
Tier 3
Data
Class 2

Get ILM Library: Techniques with Tivoli Storage and IBM TotalStorage Products now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.