Measuring capacity in primary server storage pools.

Technote (FAQ)


Question

I have Tivoli Storage Manager Suite for Unified Recovery. What tools are available to help me measure capacity in Tivoli Storage Manager primary storage pools and Tivoli Storage Manager FastBack repositories?

Answer

Tivoli Storage Manager Suite for Unified Recovery is a bundle of Tivoli Storage Manager products that offers simplified pricing and licensing with a tiered per-terabyte (TB) metric. You can install as many of the individual products as needed for your environment. There is no per-server, per-installation or processor value unit (PVU) charge; you are only charged for the TB that is stored in Tivoli Storage Manager primary storage pools and FastBack repositories.
This document is organized as two main sections. These are:

  • Section 1: Instructions. This section includes the steps necessary to do the measurement along with an explanation of prerequisites, planning, and other considerations.
  • Section 2: Background. These are the detailed explanations about the Suite for Unified Recovery.

Section 1: Instructions
The following are the steps to follow in order to perform an SUR capacity measurement for one or more Tivoli Storage Manager servers:
  1. Review the known issues that will affect performing a capacity measurement:
    Server Version Issue
    5.5 The Administrative macro command will not run on TSM Server Version 5.5.5.0 or lower due to APAR IC71586. Install 5.5.5.1 or above.
    6.x TSM Version 6 server users that have enabled server deduplication or client deduplication may be affected by code defects that cause the occupancy values to be incorrect. The following two APAR's (below) should be reviewed to determine if these apply to your environment. If one or the other does apply to your environment, apply the corresponding server fix-pack or patch containing the fix for this APAR along with performing any additional corrective actions described in the APAR's or any corresponding techdocs that reference these APARs. After these fixes have been applied and corrective actions performed, the capacity values used for the measurement will no longer be affected by these.

    IC73005 - Available, or targeted to be available, in fix pack level 6.2.3, http://www.ibm.com/support/docview.wss?uid=swg1IC73005.
    IC73592 – Available, or targeted to be available, in fix packs 6.1.5, 6.2.3 and patch level 6.2.2.3, http://www.ibm.com/support/docview.wss?uid=swg1IC73592.
  2. Planning to run the macro. The following normal considerations apply:
    • Administrative SQL commands require CPU, memory, and I/O to the database for the TSM server. Generally, for V6 and V7 servers, these requirements are not an issue as the improved SQL processing engine provided by DB2 handles these without an issue. For V6 and V7 servers, running the macro usually takes many minutes to tens of minutes depending upon the size of the server and the data stored on that server.

      For V5 servers, the SQL processing is more sensitive to these resource needs. For V5 servers, running the SUR macro may take many minutes, tens of minutes, or hours to run. Also consider that the macro should be run when the overall workload for the TSM server is light. If the macro is run when client operations or database intensive operations such as EXPIRATION are running, these operations compete with the resources needed by the SQL processing and can cause the capacity measurement to take a long time to run.
    • Consider the current health of the TSM server. If the server is I/O constrained to the database or it is having difficulty supporting existing client or daily maintenance workloads, than running the capacity measurement macro may take a long time to complete or it may appear to hang or never complete.
  3. The SUR macro applies exclusions to the data that it is measuring. As such, the TB capacity value reported by the macro will not match or align directly with the results from QUERY OCCUPANCY or QUERY AUDITOCCUPANCY or their equivalent SQL statements. This is not a problem.
  4. Download the appropriate macro. This step will vary based on your platform and browser being used. Generally, when the link below is selected, you will have an option to either download this to your local filesystem or else it will open in your browser. If it is opened in your browser, it can be saved to the local file system (drive) using the "Save As" action (usually from the FILE drop down menu). When performing "Save As", be sure to save this as a plain text (*.txt) or equivalent type of document. If it is saved as "*.html" or some other format similar to that, the macro will contain extraneous tagging or other information that will interfere with how it is run.
    Macro Name Use For Server Version Used By FTP Link
    tsm_tb_cap_v5.macro V5.5 SUR V5 Capacity Macro
    tsm_tb_cap_v5_lite.macro V5.5 SUR V5 Capacity Macro (Lite)

    (See below for when and why to consider using this version of the macro for a V5.5 server)
    tsm_tb_cap_v6.macro V6.1, V6.2 SUR V6.1 and V6.2 Capacity Macro
    tsm_tb_cap_v63.macro V6.3, V7.1 SUR V6.3 and V7.1 Capacity Macro
    tsm_ar_tb_cap_V63.macro V6.3, V7.1 SUR-Archive V6.3 and V7.1 SUR-Archive Capacity Macro
  5. Once the macro is downloaded, transfer it to the TSM server machines where it will be run. This is only necessary if the macro was downloaded to a different machine than where the TSM server is installed and running. The key item in this case is that the macro needs to be available and on each of the TSM server machines. The macro can be moved from one machine to another using tools such as FTP, SCP, a shared directory/mount, or other such tools.
  6. Run the macro using the TSM command line administrative client. Note that the client needs to be run in "batch" mode in order to invoke the macro correctly and provide the appropriate output report. The TSM command line administrative client needs to be invoked with the following syntax:

    The macro is run from a command prompt and uses the administrative command line client. The macro should be invoked using the following command syntax:

    dsmadmc -id=<yourid> -password=<yourpassword> -dataonly=yes -outfile=<output_file_name> macro <macro_name>


    The input parameters that must be specified by the administrator when this is executed are the items enclosed in '<' and '>' respectively. The specific input parameters are:


    • <yourid> - This is the administrative user id that will be used to connect to the server.

    • <yourpassword> - This is the password for the administrative user id that will be used to connect to the server.

    • <output_file_name> - The results from the macro will be stored to this file. Select an appropriate file name use. For example, consider using the server name such as "server1.capacity".

    • <macro_name> - The name of the macro to be run which is tsm_ar_tb_cap_v63.macro.
  7. The report generated by the macro (see the output_file_name from the step above) provides the capacity measurement value. Specifically, the line in the report with this value will appear as:

    Data Managed by TSM Suite for Unified Recovery
    TB within PRIMARY storage pools:
    XXX

    The "XXX" value is the TB capacity value to be used for the SUR capacity licensing program. The other information in the report is provided for informational purposes to explain the SUR program, the data exclusions from the measurement relating to the SUR program, or other details about the environment when the report was run.
  8. For V5 servers, if running the macro is taking too much time (many hours without completing) or it appears to hang, there is an alternate version of the macro that can be attempted. See above for "tsm_tb_cap_v5_lite.macro". The "lite" version of the macro does NOT perform the cross-check exclusions that account for removing things like Microsoft Sharepoint or TSM HSM for Windows or other exclusions for the SUR program. The only exclusions that the "lite" macro provides is that it excludes data in copy and active data storage pools. The "lite" version of the macro should only be used if the other data exclusions are not being used for this TSM server. For example, if this server stores Microsoft Sharepoint data which is listed as one of the SUR program exclusions, than the "lite" version should not be used since the Microsoft Sharepoint data will be counted and reported in the TB capacity value. If this TSM server is not storing any of the types of client data that are not checked by the "lite" version of the macro, than the "lite" version can be used. The exclusions that are not performed by the "lite" version of the macro are:
    • Microsoft Sharepoint
    • TSM server to server virtual volumes
    • TSM HSM for Windows
    • Fastback data replicated to a TSM server

    The "lite" version of the macro typically allows the macro to run successfully and in a shorter amount of time than the regular macro in those cases where it takes a long time (many hours) to run or where it appears to be hung and not able to complete.

Section 2: Background

Overview

Tivoli Storage Manager Suite for Unified Recovery delivers a comprehensive set of data protection capabilities such as:

  • Massive scalability with broad platform support
  • Target-side and source-side data deduplication
  • Advanced support for virtual environment protection
  • Online, consistent, and centralized data protection for:
    • Databases
    • mySAP/SAP R3 environments
    • Email servers running IBM Lotus Domino or Microsoft Exchange
    • Item-level recovery of Microsoft Exchange email objects
  • LAN-free backup and restore operations that utilizes the SAN to remove data transfer from the LAN, providing high-performance backup and restore processing while helping to minimize network traffic
  • File-system and application-aware snapshots and Continuous Data Protection (CDP)
  • Bare machine recovery for Microsoft Windows and Linux servers, for servers that are already protected with Tivoli Storage Manager FastBack
  • Hierarchical storage management for Unix and Linux systems


The following products comprise Tivoli Storage Manager Suite for Unified Recovery solution:

IBM Tivoli Storage Manager Extended Edition: Use this product for highly-scalable, enterprise-class backup, restore, and archive processing, and disaster recovery
IBM Tivoli Storage Manager for Databases: Use this product for nondisruptive protection of Oracle and Microsoft SQL data
IBM Tivoli Storage Manager for Enterprise Resource Planning: Use this product to protect vital SAP R/3 system data more efficiently, consistently and reliably
IBM Tivoli Storage Manager for Mail: Use this product to secure Lotus Domino and Exchange data, and to provide granular restore processing Exchange objects
IBM Tivoli Storage Manager for Storage Area Networks: Use this product to maximize storage network connections for Tivoli Storage Manager servers and client computers
IBM Tivoli Storage Manager for Space Management: Use this product to move inactive data to reclaim online disk space
IBM Tivoli Storage Manager for Virtual Environments: Use this product to protect and provide flexible recovery of VMware environments
IBM Tivoli Storage Manager FastBack: Use this product to provide advanced data protection and near-instant recovery for Windows and Linux servers
IBM Tivoli Storage Manager FastBack for Bare Machine Recovery: Use this product to restore a Windows or Linux Server Operating System volume within an hour
IBM Tivoli Storage Manager FastBack for Microsoft Exchange: Use this product for fast and easy recovery of individual e-mail objects

For information on supported levels of bundled products see this link:
http://www-01.ibm.com/common/ssi/cgi-bin/ssialias?subtype=ca&infotype=an&supplier=897&letternum=ENUS211-201

Frequently Asked Questions

Please refer to the FAQ technote for hints, tips, guidance for performing a capacity measurement. The FAQ technote is: http://www-01.ibm.com/support/docview.wss?uid=swg21656476.

Measuring capacity

Administrative macro commands are available to help you measure TB stored in Tivoli Storage Manager Primary Storage Pools.

There are also instructions available that explain how to us the Tivoli Storage Manager FastBack graphical user interface to help you measure TB stored in Tivoli Storage Manager FastBack Repositories

How data is measured

The Administrative macro commands use the following rules when measuring data:

· Measures the amount of deduplicated data in a deduplicated primary storage pool, where Tivoli Storage Manager has deduplicated data. This measurement shows the cost efficiency of using Tivoli Storage Manager data deduplication when the number of TB in primary storage pools is reduced.
· Excludes copy pool and active data pools. These are copies of primary storage pools and not measured for capacity reporting purposes.
· Excludes data from Tivoli Storage Manager HSM for Windows and Tivoli Storage Manager for SharePoint. These OEM products are sold on a Processor Value Unit (PVU) basis and are not included in the Tivoli Storage Manager Suite for Unified Recovery.
· Measures virtual volume source data (excluding target data). TSM allows a server (a source server) to store the results of database backups, export operations, storage pool operations, and a DRM PREPARE command on another TSM server (a target server). The data is stored as virtual volumes. When querying TSM, virtual volume data appears in primary storage pools in both the target and the source server. The data that is stored on the target server is a Disaster Recovery (DR) copy of data and is not measured.
· Excludes data replicated by FastBack to Tivoli Storage Manager and excludes data that was backed up from a FastBack server using a Tivoli Storage Manager client. This data represents a copy of data on the FastBack server that is already measured.
· Excludes other duplicated data. Other duplicated data represents data that is reported in primary storage pools, which is a copy of data that is already stored by other means. For example, the table of contents for a backup set is stored in a primary storage pool. The table of contents is metadata that describes the data on a backup set so this data is excluded from the measurement.
· Excludes data from client nodes configured as REPL_MODE of RECEIVE or SYNCRECEIVE on the target server where TSM is configured to perform server to server replication.

Measuring data in FastBack repositories


You can measure data within Tivoli Storage Manager FastBack repositories by using the graphical user interface for TSM FastBack. To learn how to use the FastBack user interface to measure capacity in FastBack repositories, see the following web page:

ftp://public.dhe.ibm.com/storage/tivoli-storage-management/capacity_measurement_tools/Measuring_data_stored_in_TSM_FastBack_repositories.pdf

Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

Tivoli Storage Manager
Server

Software version:

5.5, 6.1, 6.2, 6.3, 7.1, All Supported Versions

Operating system(s):

AIX, HP-UX, Linux, Solaris, Windows

Software edition:

All Editions

Reference #:

1500482

Modified date:

2011-05-27

Translate my page

Machine Translation

Content navigation