Oct 12

Modifying V5.5 Operational Reporting for use with Tivoli Storage Manager V6 servers

Reporting Comments Off on Modifying V5.5 Operational Reporting for use with Tivoli Storage Manager V6 servers
Abstract
This document assists customers who want to use the Tivoli® Storage Manager V5.5 Operational Reporting feature with Tivoli Storage Manager V6 servers, before making the transition to the reporting and monitoring feature that is available in V6. The instructions for configuring V5.5 Operational Reporting to work with V6 servers are provided as is, and no additional support will be provided by IBM. See the full document for restrictions and instructions.
 
 
 
Content
 

Rules of use
Background information
Preparation
Modifying reports
Modifying monitors
Modifying custom reports 

Rules of use

  • The instructions for configuring V5.5 Operational Reporting to work with V6 servers are provided as is. No additional support will be provided by IBM.
  • Follow the instructions to modify the V5.5 Operational Reporting feature to make the default reports and monitors work with V6.1 and V6.2 servers.
  • You may run both the V5.5 Operational Reporting feature and the V6.1 or V6.2 reporting and monitoring feature at the same time. However, you must install and run the features on different systems.
  • Apply the latest fix pack for the Tivoli Storage Manager V6.1 or V6.2 server to ensure that any available fixes are in place for SELECT statements or output.

V5.5 Operational Reporting is part of Tivoli Storage Manager V5.5 and as such, continues to be supported by IBM for use with V5.5 servers.

Back to top

Background information

Tivoli Storage Manager V6 introduces the reporting and monitoring feature, which has new, extensive reporting functions that replace Tivoli Storage Manager V5.5 Operational Reporting. The Tivoli Storage Manager V6 reporting and monitoring feature collects historical Tivoli Storage Manager data, so a separate server is required to run the feature. The Tivoli Storage Manager V6 reporting and monitoring feature supports reporting for both Tivoli Storage Manager V5.5 and V6 servers. For details, see Installing the reporting and monitoring feature.

Also introduced with Tivoli Storage Manager V6 is the change from a proprietary Tivoli Storage Manager database to a DB2® database. Because the DB2 program is the database manager, Tivoli Storage Manager V6 introduces fundamental changes to the database and recovery log architecture. The Tivoli Storage Manager database schema and the SELECT syntax also changed, both of which are used by Tivoli Storage Manager Operational Reporting. For information about the V6 changes, see Server database updates overview and Changes to the SELECT command.

Tivoli Storage Manager V5.5 Operational Reporting is part of the Tivoli Storage Manager Management Console for V5.5 servers, which runs only on Windows® systems. V5.5 Operational Reporting is not supported and not included with Tivoli Storage Manager V6. If a Tivoli Storage Manager V5.5 server on a Windows system is upgraded to Tivoli Storage Manager V6, the Tivoli Storage Manager V6 Management Console is installed without the Operational Reporting feature.

Without modification, the V5.5 Operational Reporting feature does not work with V6 servers. The default Custom Summary report sections in reports and monitors fail for a Tivoli Storage Manager V6 server, typically with error messages that cite syntax errors or references to columns that do not exist in the V6 server database. Customized reports might also fail.

Back to top

Preparation

To modify Tivoli Storage Manager V5.5 Operational Reporting to work with a Tivoli Storage Manager V6 server, the Tivoli Storage Manager V5.5 Management Console, which includes Operational Reporting, must be installed on a separate physical or virtual Windows device.
Important: After you make the changes that are described in this document, the reports and monitors that you modify will not work with a V5 server.
  1. If you do not already have the Tivoli Storage Manager V5.5 Management Console installed on a separate physical or virtual Windows device, download the program and install it.
    1. Go to the FTP site for V5.5 downloads for Windows systems: ftp://public.dhe.ibm.com/storage/tivoli-storage-management/maintenance/server/v5r5/WIN/LATEST
    2. Download the file for the Tivoli Storage Manager V5.5 Management Console, which has a name like 5.5.x.x-TIV-TSMCON-Windows.exe, where the x.x are numbers that indicate the fix level.
    3. Run the file that you downloaded to install the Tivoli Storage Manager V5.5 Management Console.
  2. Configure Tivoli Storage Manager V5.5 Operational Reporting according to the instructions at this link: http://publib.boulder.ibm.com/infocenter/tivihelp/v1r1/index.jsp?topic=/com.ibm.itsmcw.doc/anrwgd55668.htm
  3. Back up the default XML template files for reports and monitors:
    C:\Program Files\Tivoli\TSM\console\default_rep_eng.xml
    C:\Program Files\Tivoli\TSM\console\default_mon_eng.xml
  4. Create a report XML template file to use for modification of reports by copying this file:
    C:\Program Files\Tivoli\TSM\console\default_rep_eng.xml

    Rename the copy of the file:

    C:\Program Files\Tivoli\TSM\console\default_rep_eng_TSM6.xml
  5. Create a monitor XML template file to use for modification of monitors by copying this file:
    C:\Program Files\Tivoli\TSM\console\default_mon_eng.xml

    Rename the copy of the file:

    C:\Program Files\Tivoli\TSM\console\default_mon_eng_TSM6.xml

Back to top

Modifying reports

When first installed, Tivoli Storage Manager Operational Reporting contains a model template for a Daily Report. You must modify the Custom Summary report section of this Daily Report.

  1. Start the Tivoli Storage Manager 5.5 Management Console: Start > All Programs > Tivoli Storage Manager > Management Console
  2. Click Operational Reports and create a new report or update the properties of an existing report.
  3. On the Report Details tab, select Custom Summary and click Settings.
  4. Click Browse and select the report template file that you created in a previous step: C:\Program Files\Tivoli\TSM\console\default_rep_eng_TSM6.xml
  5. Edit each of the following Select Variables, and modify the select statements.
    LDBB (Last Database Backup)
    Original select statement:

    select substr(char(last_backup_date), 1, 16) as
    LDBB from db where cast((current_timestamp-last_backup_date)hours
    as decimal)<%s

    Modified select statement:

    select substr(char(last_backup_date), 1, 16) as
    LDBB from db where cast(hour(current_timestamp-last_backup_date)
    as decimal)<%s
    PCTUTILIZED (%Database Utilization)
    Original select statement:
    select pct_utilized from db

    Suggested modified select statement:

    select sum(100-(free_space_mb*100) / tot_file_system_mb) as PCT_UTILIZED
    from db

    The PCT_UTILIZED variable has no direct equivalent in Tivoli Storage Manager V6 servers. To monitor the usage of database space, the ratio of FREE_SPACE_MB to TOT_FILE_SYSTEM_MB can be used to give similar results. The suggested select statement gives the percent utilized of the space available to the database.

    To be automatically warned when the space available to the database is nearly full, activate a notification rule to receive a message if this value reaches a high percentage, for example 85%.

    CACHE_PCT (Database Cache Hit Ratio)
    Original select statement:

    select CACHE_HIT_PCT as CACHE_PCT from DB

    Modified select statement:

    select BUFF_HIT_RATIO as CACHE_PCT from DB
    MAX_PCT_UTILIZED (% Maximum Recovery Log Utilization)
    Original select statement:

    select max_pct_utilized from log

    You can either delete this Select Variable, or change it to report on the file system where the active log is located. A suggested modified select statement:

    select cast(sum(used_space_mb *100 / total_space_MB) as decimal(3,1))
    as MAX_PCT_UTILIZED from log

    The suggested select statement reports the percent utilized of the file system where the active log resides. The number is important because problems occur if the file system where the active log resides fills up.

    RESET_BUFFPOOL
    Original select statement:

    reset bufpool

    Delete this Select Variable. Tivoli Storage Manager servers at V6.1 and later do not reset the buffer pool.

    TMS (Number of tape mounts)
    Original select statement:

    select count(*) as TMS from summary
    where activity='TAPE MOUNT' and cast((current_timestamp-start_time)hours
    as decimal)<%s

    Modified select statement:

    select count(*) as TMS from summary
    where activity='TAPE MOUNT' and cast(hour(current_timestamp-start_time)
    as decimal)<%s
    MTM (Total number of minutes tape were mounted)
    Original select statement:

    select (sum(end_time-start_time))minutes as MTM from summary
    where activity='TAPE MOUNT' and
    cast((current_timestamp-start_time)hours as decimal)<%s

    Modified select statement:

    select (sum(minute(end_time-start_time))) as MTM from summary
    where activity='TAPE MOUNT' and
    cast(hour(current_timestamp-start_time) as decimal)<%s
  6. Click OK, then click Yes to save the changes.

Back to top

Modifying monitors

When first installed, Tivoli Storage Manager Operational Reporting contains a model template for an Hourly Monitor. You must modify the Custom Summary report section of the Hourly Monitor.

  1. Start the Tivoli Storage Manager V5.5 Management Console: Start > All Programs > Tivoli Storage Manager > Management Console
  2. Click Operational Monitors and create a new Hourly Monitor, or update the properties of an existing monitor.
  3. On the Monitor Details tab, select Custom Summary, then click Settings.
  4. Click Browse and select the monitor template file that you created in a previous step: C:\Program Files\Tivoli\TSM\console\default_mon_eng_TSM6.xml
  5. Edit the following Select Variables, and modify the select statements.
    PCTUTILIZED (%Database Utilization)
    Original select statement:
    select pct_utilized from db

    Suggested modified select statement:

    select sum(100-(free_space_mb*100) / tot_file_system_mb) as PCT_UTILIZED
    from db

    The PCT_UTILIZED variable has no direct equivalent in Tivoli Storage Manager V6 servers. To monitor the usage of database space, the ratio of FREE_SPACE_MB to TOT_FILE_SYSTEM_MB can be used to give similar results. The suggested select statement gives the percent utilized of the space available to the database.

    MAX_PCT_UTILIZED (% Maximum Recovery Log Utilization)
    Original select statement:

    select max_pct_utilized from log

    You can either delete this Select Variable, or change it to report on the file system where the active log is located. A suggested modified select statement:

    select cast(sum(used_space_mb *100 / total_space_MB) as decimal(3,1))
    as MAX_PCT_UTILIZED from log

    The suggested select statement reports the percent utilized of the file system where the active log resides. The number is important because problems occur if the file system where the active log resides fills up.

  6. Click OK, then click Yes to save the changes.

Back to top

Modifying custom reports

If custom reports have been created in the Operational Reporting feature, verify that the syntax of custom select statements is correct for V6 servers. Review the information in the following document to learn about the changes that were made to the Tivoli Storage Manager server SELECT command between V5.5 and V6: Changes to the SELECT command.

For additions and corrections to this information about the SELECT command, see the technote: http://www.ibm.com/support/docview.wss?uid=swg21380830

written by Bosse

Oct 07

Windows 2003 Volume Shadow Copy Service (VSS) Hotfixes for Systemstate Backup

Windows VSS Comments Off on Windows 2003 Volume Shadow Copy Service (VSS) Hotfixes for Systemstate Backup

Problem(Abstract)

TSM client backups of Windows 2003 system state fail with varying VSS errors

Cause

Microsoft VSS failures

Resolving the problem

This list represents fixes available from Microsoft, listed in historical order, for Windows 2003 systemstate backup problems experienced by 3rd party backup vendors, including Tivoli Storage Manager (TSM).

KB # in bold represents the most current fix that is available. All the below VSS fixes should be reviewed for applicability and requested from Microsoft support.

    KBASE# FIX #
    ————–
    826936 139876
    833167 158865
    867686 188827 (No web link)
    887827 unknown (No web link)

All of the above fixes are rolled into Windows 2003 SP1. Microsoft KBase# 824721 documents the list of fixes included in SP1.

Subsequent to Win2k3 SP1, Microsoft has provided VSS Post SP1 fix packages:

    KBASE# FIX #
    ————–
    891957 unknown
    903234 unknown
    913648 unknown Note: 903234 is a prerequisite for the above patch and replaces 891957.
    915331 unknown
    923628 unknown

All of the above fixes are rolled into Windows 2003 SP2. Microsoft KBase# 914962 documents the list of fixes included in SP2.

Subsequent to Win2k3 SP2, Microsoft has provided VSS Post SP2 fix packages:

    KBASE# FIX #
    ————–
    940349 unknown
    934016 unknown Note: This is a COM+ rollup package required for VSS

Additional KB information from Microsoft:

    951568 – VSS-based backup operations may fail if VSS tracing is enabled on a Windows Server 2003-based computer that has hotfix 940349 applied.

written by Bosse

Oct 07

Distinguish the Management Class a Directory Will Be Bound To

Versions files and directories Comments Off on Distinguish the Management Class a Directory Will Be Bound To
Question
Since directories are bound to the management class with the longest retention setting (if dirmc is not set), what happens if there are several management classes with the same retention settings? Which management class will the directories be bound to?
 
 
Answer
Unless the DIRMC option is set in the Tivoli Storage Manager client options file, the directories for a Tivoli Storage Manager client backup will be bound to the management class in the active policy set containing the copygroup with the largest retention settings (highest RETONLY value).
If there are several management classes with the same retention settings, then the directories will be bound to the copygroup of the management class listed LAST in alphabetical order.Here is an example:In the domain STANDARD, this is a list of management classes and copygroups defined to the server for the active policy set:
The default management class is STANDARD. When an incremental backup of directory c:\temp is done, the directory is bound to the XYZ management class. To verify which management class the directory is bound to, the following select statement can be run from a Tivoli Storage Manager administrative client commandline:select class_name from backups where node_name=’YOURNODENAME’ and type=’DIR’ group by class_name

The output from the select statement in this example is:
CLASS_NAME
——————
XYZ

This shows that even though there are several management classes which have the same retention settings, the directories are bound to the last alphabetical listing.

written by Bosse

Oct 07

Directories not displayed for point in time restores using GUI client

Versions files and directories Comments Off on Directories not displayed for point in time restores using GUI client
Problem(Abstract)
Tivoli Storage Manager client fails to show folders in the GUI or web client GUI using a point in time restore
 
 
Cause
Tivoli Storage Manager server policy management for directories is preventing the Tivoli Storage Manager client GUI from properly displaying them.
 
 
Resolving the problem
The Tivoli Storage Manager point in time restore function is used to restore a file space, directory, or file to a previous condition. While a point in time restore can be useful for restoring the state of a system to an earlier date, it also carries a restriction – it can indirectly restrict what files and folders are selectable for the restore (such as from the GUI or web interface). Take the following example, which assumes that directories are bound to the same management class as files:
Filespace:
C:\
|
|-folder1
|
|-file1.txt(static)
|
|-file2.txt(changes before each backup)
|
|-folder2(static)Copygroup settings for this client (for both directories and files):
Verexists = 7 versions of a file(file exists on the original system)
Verdelete = 7 versions of a file(file no longer on the original system)
Retextra = 7 days
Retonly = 7 daysActions:
Assume that file2.txt changes every day, and a schedule backs up this filespace every day. When each incremental backup occurs, it sends a new active version of file2.txt, and a NEW ACTIVE version of folder1. In this example, the following table would result. This shows the backups that are available on Day 8, looking back for each of the prior 8 days (including Day 8). Active copies of the backed up file and folder are represented by the letter “A”, inactive copies by the letter “I”, and versions deleted from the filespace by the letter “X”, as shown below.

Active/Inactive/Deleted
———————————————-
Day 1 | A I I I I I I X
Day 2 | A I I I I I I
Day 3 | A I I I I I
Day 4 | A I I I I
Day 5 | A I I I
Day 6 | A I I
Day 7 | A I
Day 8 | A

On Day 8, if a point in time restore of either file1.txt or folder2, using Day 1 as the point in time criteria, it would fail to see any folders under C:\ (as viewed by the GUI or web client). That is, folder1 and any of its contents are not visible for selection under a point in time restore.

Why is this so?

The Tivoli Storage Manager client GUI/web client GUI point in time restore requires an active or inactive version of that folder to exist (at the point in time specified by the user) so that it can display items from within that folder to restore. Since folder1 now has a point in time scope going back only to Day 2, folder1 and its contents are unavailable because a backup version for that folder no longer exists at that point in time. Thus, nothing within that folder (active or not) can be selected for restore from the Tivoli Storage Manager client GUI/web client GUI.

To restore a folder or file to a particular point in time (such as file1.txt or folder2), use the ‘display active/inactive files’ option instead. With the Tivoli Storage Manager client GUI/web client GUI, select the ‘View’ menu, then select the ‘Display active/inactive files’ option. This is the equivalent of using the Tivoli Storage Manager command line client command ‘restore c:\* -pick -inactive -subdir=yes’. Select the version to be restored, based on the date and time criteria. Refer to the Tivoli Storage Manager B/A client manual for further information regarding the use of the client command line and its available options.

Alternatively, restore the filespace using the Tivoli Storage Manager client command line, which does not have this restriction. Use the PITDATE and PITTIME options to specify the desired point in date/time.

Managing proper versions of directories can be maintained using the DIRMC option in the dsm.opt file. See the Tivoli Storage Manager client manual for details. Also review technote solution 1447142 for learning how this works with Tivoli Storage Manager server policy management.

written by Bosse