IBM Tivoli Storage Productivity Center, V5.2.4 storage grouping: a consumer oriented view of storage
bobby_g 060000DF9B Visits (10423)
Not all storage is created equal.Sometimes you need to access different parts of your storage environment more frequently than others;that’s a reality.
One of the best practices for storage capacity planning is to make sure that the most productive parts of your business organization are using their storage as efficiently as possible.
The Tivoli Storage Productivity Center, V5.2.4 storage-grouping concept entails instituting application and department models that systematically enable you to support the SAN resources that your business infrastructure uses on a daily basis.
"The new grouping function within IBM's Tivoli Storage Productivity Center and Virtual Storage Center is very impressive. I can now associate my storage resources with applications and departments which provides clarity on usage, and ultimately allows me to accurately charge application owners and department heads based on consumption." - - Marco van Meurs, Storage Specialist, Inframatica.
To model the departments in your business organization, you can create departments and subdepartments and organize the departments and subdepartments into business hierarchies.
A department might share SAN resources with another department, subdepartment or application even if they do not belong in the same hierarchy. For example, in a collaboration scenario, a single IBM® SAN Volume Controller might be shared by multiple departments. You could provide reports on the storage capacity your department uses at different levels of your business hierarchy in order to regulate and compare the capacity storage and in turn, track the trending of storage usage by specific departments.
To monitor the capacity of departments, you create a grouping model that represents the departments that you want to monitor. The department model comprises these main elements:
You can view charts and information about the capacity and space usage of the department and each of the subdepartments and applications.
The other part of a complete hierarchy is the creation of an application group. An application can be part of a department and have its own subcomponents (member applications). Applications that are grouped together can range from large line of business systems to a specialized software system, in a department that runs on either client computers or servers. For example, an application might be named Book Sales DB and it might contain business transactions, like Wholesale Transactions, Retail Transactions and Online Transactions. You would create subcomponents (member applications) for the business transactions and these subcomponents then become part of the Book Sales DB application.
The assignment of SAN resources to the applications and subcomponents that the department uses is the final piece of the modeling.You can assign eligible resources like servers, volumes, shares, and file systems among others using the dyna
You can use applications for planning purposes to diagnose how much storage a particular application is consuming in relation to the other applications in your business hierarchy.
Another applicable usage for applications might be troubleshooting performance issues. You check the application charts about the related SAN resources that make up the application to see if there is a health status issue or examine the performance of the volumes that are used by the application, and then troubleshoot along a particular data path.