Tivoli Storage Manager version 6.3 Effective Chargeback Practices using Reporting/Monitoring

Transcription

1 Tivoli Storage Manager version 6.3 Effective Chargeback Practices using Reporting/Monitoring By Bill Komanetsky Version 1.0

2

3 Copyright Notice Copyright IBM Corporation All rights reserved. May only be used pursuant to a Tivoli Systems Software License Agreement, an IBM Software License Agreement, or Addendum for Tivoli Products to IBM Customer or License Agreement. No part of this publication may be reproduced, transmitted, transcribed, stored in a retrieval system, or translated into any computer language, in any form or by any means, electronic, mechanical, magnetic, optical, chemical, manual, or otherwise, without prior written permission of IBM Corporation. IBM Corporation grants you limited permission to make hardcopy or other reproductions of any machine-readable documentation for your own use, provided that each such reproduction shall carry the IBM Corporation copyright notice. No other rights under copyright are granted without prior written permission of IBM Corporation. The document is not intended for production and is furnished as is without warranty of any kind. All warranties on this document are hereby disclaimed, including the warranties of merchantability and fitness for a particular purpose. U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corporation. Trademarks IBM, the IBM logo, Tivoli, the Tivoli logo, AIX, Cross-Site, NetView, OS/2, Planet Tivoli, RS/6000, Tivoli Certified, Tivoli Enterprise, Tivoli Enterprise Console, Tivoli Ready, and TME are trademarks or registered trademarks of International Business Machines Corporation or Tivoli Systems Inc. in the United States, other countries, or both. Lotus is a registered trademark of Lotus Development Corporation. Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both. UNIX is a registered trademark of The Open Group in the United States and other countries. C-bus is a trademark of Corollary, Inc. in the United States, other countries, or both. PC Direct is a trademark of Ziff Communications Company in the United States, other countries, or both and is used by IBM Corporation under license. ActionMedia, LANDesk, MMX, Pentium, and ProShare are trademarks of Intel Corporation in the United States, other countries, or both. For a complete list of Intel trademarks, see SET and the SET Logo are trademarks owned by SET Secure Electronic Transaction LLC. For further information, see Java and all Java-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and other countries. Other company, product, and service names may be trademarks or service marks of others. Notices References in this publication to Tivoli Systems or IBM products, programs, or services do not imply that they will be available in all countries in which Tivoli Systems or IBM operates. Any reference to these products, programs, or services is not intended to imply that only Tivoli Systems or IBM products, programs, or services can be used. Subject to valid intellectual property or other legally protectable right of Tivoli Systems or IBM, any functionally equivalent product, program, or service can be used instead of the referenced product, program, or service. The evaluation and verification of operation in conjunction with other products, except those expressly designated by Tivoli Systems or IBM, are the responsibility of the user. Tivoli Systems or IBM may have patents or pending patent applications covering subject matter in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to the IBM Director of Licensing, IBM Corporation, North Castle Drive, Armonk, New York , U.S.A. iii

4 About the Tivoli Field Guides Sponsor Tivoli Customer Support sponsors the Tivoli Field Guide program. Authors Those who write field guides belong to one of these three groups: Audience Tivoli Support and Services Engineers who work directly with customers Tivoli Customers and Business Partners who have experience using Tivoli software in a production environment Tivoli developers, testers, and architects The field guides are written for all customers, both new and existing. They are applicable to external audiences including executives, project leads, technical leads, team members, and to internal audiences as well. Types of Field Guides Two types of Tivoli Field Guides describe how Tivoli products work and how they are used in real life situations: Purposes Field Guides for technical issues are designed to address specific technical scenarios or concepts that are often complex to implement or difficult to understand, for example: endpoint mobility, migration, and heartbeat monitoring. Field Guides for business issues are designed to address specific business practices that have a high impact on the success or failure of an ESM project, for example: change management, asset Management, and deployment phases. The Field Guide program has two major purposes: Availability To empower customers & business partners to succeed with Tivoli software by documenting and sharing product information that provides accurate and timely information on Tivoli products and the business issues that impact an enterprise systems management project To leverage the internal knowledge within Tivoli Customer Support and Services and the external knowledge of Tivoli customers and Business Partners All completed field guides are available free to registered customers and internal IBM employees at the following Web site: Authors can submit proposals and access papers by mailto:tivoli_esupport_feedback@us.ibm.com iv

5 Table of Contents (if you need it) Effective Chargeback Practices using Reporting/Monitoring... 1 Effective Chargeback Practices... 1 The New TSM Data... 1 Categorizing the New Data... 3 Creating the Report... 4 Filtering for certain Categories... 6 Summarizing for the entire Category... 7 More Detailed Charge- Back... 7 De- Duplication Issues... 7 v

6

7 Tivoli Storage Manager 6.3 Effective Chargeback Practices Tivoli Storage Manager (from now on referred to as TSM) includes within it, the IBM Cognos Business Intelligence offering, which in itself is a purchasable product sold by the IBM software division. Cognos is more than just a reporting tool, it is a business intelligence offering giving the customer real information manipulation and analysis capabilities normally not available in a storage management solution like TSM. TSM version 6.3 also includes in it more complete data collection for those Attribute Groups (tables) that are needed for effective charge back reporting. Now with this newly collected data, it is possible for the TSM administrator to create usable charge back reports, schedule them, and them automatically. 1 The New TSM Data As can be seen in the diagram here, TSM s reporting and monitoring feature (as of version 6.3) includes the Cognos business intelligence offering. The Cognos tool accessing the WAREHOUS database implemented in the DB2 RDBMS (Relational Database Management System) allowing for tremendous growth and performance benefits over other database systems. Attribute Groups, or Tables in the WAREHOUS database contain the data necessary to create Cognos reports, and in this case, Charge Back reports. However, it is important for the TSM administrator to understand that the reports are only as good as the data is and an effort must be made by the administrator to put the necessary data into the TSM server itself to assure accurate charge back reports are possible. One of the attribute groups involved in the creating of charge back reports is Client Node Status. This attribute group now includes in it, additional columns, or fields, which were not available in previous versions of TSM. Operating System Level (OSLevel) System Architecture (SYSArch) Client Version (CLVersion) Client Release (CLRelease) Client Level (CLLevel) 1

8 Client Sub-Level (CLSubLevel) Contact Any or all of these new columns can be used for charge back reporting, but the one that this article will concentrate on is the Contact column. This column can store just about any type of data which can then be used to categorize the storage that the Client Node is utilizing and how it should be charged. To view the Contact Column, you can use the monitoring portion of TSM s reporting/monitoring offering called the Tivoli Enterprise Portal. Expand the TSM server you are interested in (as shown here) and navigate down to the Client Node Status attribute group, click on it. In the content portion of the window (shown above), you will see the columns which are displayed by default. The new columns previously listed do not show in this display, but they are there, you just need to customize this view to see them. To do this: Click on the slash (/) found at the top right of the content panel showing the contents of the Client Node Storage attribute group Scroll to the far right and check the Contact and checkboxes to enable them in the monitoring window. In the window displayed, click the Filters tab. You will see columns with check boxes beneath them. Some of them will be checked, others not. Now if you scroll to the right in the content panel, you will see the two new columns and their contents, Contact and . As said earlier, the Contact column is our target here as it will allow you to add text for charge back categorization purposes. 2

9 2 Categorizing the New Data Now that we have a target for our Charge Back categorization, let s put together a user story that illustrates what we will be doing in this article. The I/T director of a large insurance company would like to schedule monthly reports showing total TSM storage used and the cost of such storage to be generated and ed, automatically, to the associated departments for charge-back purposes. Each TSM client node will have a department identifier embedded in the Contact column with that node s department code. Also, the second line manager (that manager which manages the first set of departments described) would also like to see just how much money they are spending on TSM storage across their departments. The report should differentiate between Tape storage and Disk storage. Tape storage will be charged out at $1.25 per megabyte per month and tape storage will be charged at $.15 per megabyte per month. A total for each department should be shown at the bottom of the report along with a cross-department summary below that. These summary s should show total storage being used for both Disk and Tape and total charges for the same. This is a pretty simple request, but something that was not possible in previous versions of TSM without doing a lot of coding by the end user. The first thing we have to do is update the Contact column for each TSM client node we wish to categorize for this new report. To do this, we will use the TSM update node command. As an example, Client Node named DB2ACCT (DB2 accounting server) needs to have the department ACCTFIN1 added to its contact field as well as the second level department ID of ACCT1 which is the parent department of ACCTFIN1. (Note that you should map out how you wish to do this before issuing any TSM commands to assure you are architecting your charge back strategy correctly.) To do this, as previously mentioned, we will use the update node command from the TSM console. Remember however, using this command will overwrite any information in the Contact column, so it might be a good idea to either use the TEP to view the current content or the query node command from the command line interface.also allows for the analysis over time most that storage management products can only dream of. q node DB2ACCT format=detailed To actually update the Contact column, issue the command shown below: update node DB2ACCT contact= Tom Smith <ACCT1> <ACCTFIN1> You will now need to do this same type of command for each Client Node you wish to include in a charge back report. It might be a good idea to inventory all of your Client Nodes and assign them to departments before issuing each command. You could then create a Script using your favorite text editor to do this for you without having to issue each command one at a time. Also note that this method can be used for more than just departmental categorization. You can insert project ID s or names, Service Level Agreement codes or any number of categories to help with your charge back efforts. 3

10 3 Creating the Report As described in another white paper entitled Creating your first Report using Query and Report Studio, you were taught how to actually use these tools to create both a query and a report. So, to get started, open up the Cognos Query Studio user interface and navigate to the IBM Tivoli Storage Manager Cognos Reports link. This will load the data model for TSM into the Query Studio. Next, navigate to the IBM Tivoli Storage Manager Cognos Reports -> Consolidation View -> Tivoli Storage Manager Report Data -> Key Metrics -> Performance -> Monthly -> Client Node Storage Monthly attribute group. This is the attribute group that we will use to get the number from that will be used to charge the user. Now, either drag or right click -> Insert (depending on which internet browser you are using) the Server column first, then the Write Time, followed by the Client Node Name, Disk Usage (Average MB) and Total Tape Space Used (Average MB) columns into the query studio work area. Then click the Server column header, and press the Create Sections button on the tool bar of the Query Studio user interface. Next, select the Write Time column header and press the Group button on that same tool bar. This will add the appropriate columns as well as group all nodes by the date and Server. Your current query results should look something like that shown here. Notice that we picked the Monthly summarization attribute group since we are interested in average storage used over the past month and not what the node is using right now. Current storage usage can be found in the Detailed attribute groups. The next step is to link the Client Node Status and Client Node Storage attribute groups. We must do this since the Contact information is stored in the second, and the storage space in the first. With Cognos, it is easy to do this because the Cognos data model which is included in TSM 6.3 already has this relationship defined, so all that needs to be done is click/insert or drag columns from the Client Node Storage attribute group into our already existing query. So, navigate to the IBM Tivoli Storage Manager Cognos Reports -> Database View -> Tivoli Storage Manager Report Data -> Key Metrics -> Performance -> Monthly -> KSK_Client_Node_Status_MV attribute group. The reason we are using this attribute group is 4

11 because the Contact information has not been added, in the model, to the Monthly summarization tables as the storage sizes were. Now, click on the Disk Usage column and either drag or right click -> Insert (depending on which internet browser you are using) the LAT_Contact column (latest contact) into the query studio work area. This will give you a new column showing you who owns the disk and tape space used by that node. Now, let s say you are only interested in a single TSM server for this report. Right Click on the Server section header and select Filter. At the bottom of the screen, select a specific server you want to report on to and press the OK button (in this case, SS2_ADSM_GROUP_SERVER). When done, click the OK button. Now, your current query should only show this particular server and all nodes and their owners. Also, let s filter this report to only show a specific month - October, To do this, right click on the Write Time column header and select Filter, just as you did for the Server section above. You have a lot of options here, but let s just pick a range from October 1st - October 31st for the report date. If you plan on scheduling this report to run on the first of every month, you could just ask for the last 30 days, but let s do a range for this example. Click the OK button when you have finished and OK again if necessary. Next, let s calculate the charge for the indicated storage. To do this, right click on the Disk Usage (Average MB) column header and select Calculate from the displayed menu. Click on the Disk Usage (Average MB) column header Right click the Disk Usage (Average MB) column header and select Calculate from the menu displayed. Scroll down the browser window, make sure Arithmetic is select in the Operation Type drop-down list, and Multiplication from the Operation drop-down list In the Number field, type 1.25 which is the rate we were going to charge for this type of storage - Disk. Over in the New Item Name text field, type something like Disk Storage Charge Click the Insert button Do the exact same thing for the Total Tape Space Used (Average MB) column except put.15 in the number field and name the column something like Tape Storage Charge. 5

12 Now that you have both the Megabytes of storage and the charge-back amounts, you may want to reformat the numeric columns to look like currency. To do this: Click on the Disk Storage Charge column header Right click the Disk Storage Charge column header and select Format Data from the menu displayed. Scroll down the browser window and select Currency from the Category drop down list. You can leave everything else in that panel as default Click the OK button Do the same for the Tape Storage Charge column as well. Once completed, your query should not look something like this. You may, if you like, now delete the Disk Usage... and Total Tape Space Used... columns in the query. However, most customers will want to see these numbers as they may be interested in the actual amount of storage they are using and being charged for. You can also make some additional changes to the report like clicking on the Title link and add a title and subtitle to make it more consumable by the end user. Filtering for certain Categories If you remember, at the beginning of this discussion (section 2), we wrote about categorizing your TSM client nodes so you can charge based on projects or departments (as an example). We are not at a point where we can do that and then save the report to be run on a monthly basis. We decided to add the <ACCT1> and <ACCTFIN1> tags to the contact column to show those nodes that are being used by the ACCTFIN1 department and its parent department ACCT1. To filter on these strings, right click on the LAT_Contact column header and select Filter. On the top right of the filter section (found at the bottom of your browser window) click on the Type in Values link. This link will allow you to specify the exact values you are looking for. In the Operation drop down box, select Contains, then type in the value you are filter on, in this case, type <ACCT1>. Click the OK button, then the next OK button to see the results of your query. 6

13 Summarizing for the entire Category Now, the last thing we need to do is to create a total for all client nodes in the category we just filtered on (<ACCT1>). This may have been done automatically because of the way that the Cognos data model is setup. Click the bottom link at the bottom of your browser page and if you see a display that looks similar to this, then the report is automatically summarizing for you and you don t need to do another thing. But, if you need to summarize these columns (like in the Disk and Tape Usage quantity columns, here is the procedure. Right click the column you wish to summarize - let s summarize the Disk Usage column - select Summarize from the displayed menu. At the bottom of your browser screen, select Total from the Summary for Footers drop down list, and press the OK button. Do the same for the Total Tape Space Used column. More Detailed Charge-Back This charge-back example is a very simple one where the user, or in this case the department, will have a report generated that allows for only disk and tape space to be charged for. However, it may be advantageous to charge a customer differently based on Active Disk, Primary Disk and Copy Disk as well as those same three categories of tape storage. This as well is possible with TSM 6.3 reporting because of the fact that this data is also stored in the Client Node Storage attribute group. Total Active/Primary/Copy Disk Space Used (Average MB) Total Active/Primary/Copy Tape Space Used (Average MB) It is a simple matter of inserting each column into the report that we did earlier, and creating a calculated column with the appropriate charge-back rate per megabytes as we did for total disk and total tape space used. De-Duplication Issues With the advent of TSM 6.1, a new feature was added to the product called De-Duplication. This storage saving property of TSM allows for the storing of data only once across multiple nodes. Today, TSM 6.3 has the capability of showing de-duplication savings across storage pools but not at the Client Node level. This means that if your TSM servers are de-duplicating data, the amount 7

14 you are charging your customers may be incorrect since a percentage of the storage space being used may be de-duplicated. So to do this, you can either hard code a discount into your calculations of Disk Storage Charge (as we setup earlier in this discussion) or take the value directly from the Storage Pool attribute group found in the WAREHOUS database. Let s do both. Method #1: Hard Coded De-Duplication Method You may want to give a hard-coded 25% discount to customers who are storing their data on deduplicated storage devices. Disk is an obvious storage device that falls into this category. Note that you will be calculating a new column based on a previously created calculated column - Disk Storage Charge. Right click on the Disk Storage Charge column (created earlier in this discussion), and select Calculate from the displayed menu Just as you did previously, select Arithmetic and then Multiplication from the selections at the bottom of your web browser. Since you want to give a 25% discount, the number you want to multiply this value by is.75. Type.75 into the Number field Type a name for this new column in the New Item Name text field. Something like Deduplication Discounted Charge. Press the Insert button. Method #2: Storage Pool De-Duplication Method A method that might be a bit more accurate is to use the Storage Pool attribute group to calculate a de-duplication discount to apply to a charge back value. You can easily add the MAX_Dedup_Save_Pct column into your Charge Back report from the KSK_Storage_Pool_MV attribute group. Navigate to the IBM Tivoli Storage Manager Cognos Reports -> Database View -> Tivoli Storage Manager Report Data -> Key Metrics -> Performance -> Monthly -> KSK_STORAGE_POOL_MV attribute group in the query studio and press the + sign to display all of the attributes under this attribute group Next, drag or right click and select Insert the MAX_Dedup_Save_Pct attribute to put it into your Charge Back report. You do not want to use the AVG_ or MIN_ attributes here since for some storage pools the de-duplication savings percent will be zero, bringing down the savings to an unrealistic level Your report will now have the maximum savings your de-duplication settings have seen during backup/archive operations. But, to be able to multiply this into your Disk Storage Charge column, you need the value that says just how much storage is actually being used. For instance, if your de-duplication saving percentage is 63%, you will want to subtract this value from 100 to obtain a value of 37% which is the actual value that should be used for the charge-back calculations. To do this we need to create a new calculated column where we subtract the de-duplication savings percent from 100 Right click on MAX_Dedup_Save_Pct column header and select Calculate At the bottom of your browser window, select Arithmetic and Difference from the available entry fields 8

15 Select <Number> - MAX_Dedup_Save_Pct Enter 100 into the number text field Give your new column a name something like Deduplication Charge Rate Press the Insert button. You will now have a new column which contains the mathematical value you will use to create your actual charge-back amount. You can delete the MAX_Dedup_Save_Pct column if you like as it is no longer needed. To do this, just click on the MAX_Dedup_Save_Pct column header, right click and press Delete. Next, you need to create another calculated field to show the actual charge. 1. Click on the Disk Storage Charge column header. Hold down your control key (or the keyboard combination that allows you to select multiple items not in line with each other), then click on the new De-duplication Charge Rate column you just created. This will select both columns. 2. Right click on either selected column and click on Calculate from the menu 3. You will now see the two columns you just selected in the Selected report items list box. These are the two columns you will use for this calculation. Make sure Arithmetic and Multiplication are selected. 4. Check the Number check-box and type.01 to divide the result by Enter a name for your new column like we did before: Deduplication Discounted Charge and press the Insert button. 6. Right click on the new column header and select Format Data Select Currency and press the OK button Your new report should look something like this: 9

16 You can now delete the MAX_Dedup_Save_Pct and the Deduplication Discount Rate (or whatever you named these) columns if you like. 10