7 December 2014

Using TSM V5 Operational Reporting with TSM V6 and TSM V7

The IBM Tivoli Storage Manager operational reporting feature automates some of the monitoring tasks you typically perform manually. Operational reports can be scheduled to run daily and are generated even if there are no problems. Operational reporting is administered through the Microsoft Management Console on a Windows machine. Operational reporting runs as a service and supports multiple Tivoli Storage Manager servers running on a single machine. 

The operational reporting installation package contains two default custom summary templates, one for a report and one for a monitor. Default e-mail messages will notify you if the server is running smoothly, or if there are issues such as failed or missed schedules. You can also link to a Web summary page to check operational reports about your server. You can run the Operational Reporting interface on Windows only, but it supports servers running on any supported operating system.

Tivoli Storage Manager V5.5 Operational Reporting is part of the Tivoli Storage Manager Management Console for V5.5 servers. TSM V5.5 Operational Reporting is not supported and not included with Tivoli Storage Manager V6 & V7packages. 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. But with some modifications, the V5.5 Operational Reporting feature can be used to work with V6 or V7 servers.  

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 or V7 reporting and monitoring feature at the same time. However, you must install and run the features on different systems. The V5.5 Operational Reporting feature cannot be installed on the same system as the V6 or V7 Management Console.

Installing and Configuring TSM V5 Operational Reporting with TSM V6 and V7

1) To modify Tivoli Storage Manager V5.5 Operational Reporting to work with a Tivoli Storage Manager V6 or V7 server, the Tivoli Storage Manager V5.5 Management Console, which includes Operational Reporting, must be installed on a separate physical or virtual Windows device. You can download the Tivoli Storage Manager V5.5 Management Console here in IBM ftp site

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. Run the file that you downloaded to install the Tivoli Storage Manager V5.5 Management Console.

3) First you have to configure Tivoli Storage Manager V5.5 Operational Reporting as usual as explained below
  • Click on the operational reporting icon. 
  • Right click on the Tivoli Storage Manager icon and choose Add TSM Computer
  • Click TSM Operational Reporting and click Add to add a report, and click OK to accept the defaults. 
  • Expand the tree view in the MMC snap-in to find your report. 
  • Right-click on your report and choose refresh to see it.

Now you need to add the TSM Server to the Tivoli Storage Management Console 
  • From Start menu on the task bar, select Programs→Tivoli Storage Manager→Management Console
  • On the Management Console, right click Tivoli Storage Manager and select Add TSM Computer
  • In the TSM Computer Resource Properties window, under the Computer Information tab, enter the machine name. 
  • Select an Operating System. 
  • Check Include Report Features to enable operational reporting features. The TSM Web Client is optional.
  • Check TSM Web Administrator to enable the Management Console to communicate with the server. 
  • Specify Tivoli Storage Manager server information Server name, TCP/IP Address, TCP/IP, Port HTTP Port 
  • Click Add. 
  • The Logon Information window pops up. Enter the Administrator name and Password. Click OK.
  • You should now see the information you entered such as the server name and TCP/IP address. Click OK.

4) After configuring the TSM V5 Operational Reporting, now you need to make some modifications to make it work with the TSM V6 & V7 servers. You have to replace the TSM V5.5 XML files with new TSM V6 XML files. You can download these new TSM V6 XML files from here. Any new reports or monitors will automatically use the new templates since they will be now the defaults.

5) Go to C:\Program Files\Tivoli\TSM\console directory and delete or rename the following two TSM V5 default files to add  _TSMold to the file name as shown below

Rename default_rep_eng.xml to default_rep_eng_TSMold.xml.
Rename default_mon_eng.xml to default_mon_eng_TSMold.xml.
6) Now you have to rename the new downloaded files to the default names, so that the operational reporting will pick up these new XML files during reporting.

Rename default_rep_eng_TSM6or7.xml to default_rep_eng.xml.
Rename default_mon_eng_TSM6or7.xml to default_mon_eng.xml.
7) If you dont want to delete or rename the old TSM V5 XML files, you can specify a template to use with a reporting or monitoring seperately. To have a report or monitor use the template file
  • Right-click a report or monitor and click Properties.
  • Click Custom Summary.
  • Click Settings.
  • Select the template file that you want to use and click OK.
Apart from the default SQL queries which are included in these XML files, you can also add your own customized SQL queries for generating you own reports. Please remember that the instructions for configuring V5.5 Operational Reporting to work with V6 or V7 servers are provided separately and please beware that no additional support will be provided by IBM.

5 December 2014

Taking file level backup of unrecognized characters in Linux servers

On Linux servers, if you have files or directories which contains characters from another language, i.e not english words, the Tivoli Storage Manager client cannot recognize these characters during manual backups, schedule backups, or when trying to view them using the BA Web Client.

If you are taking manual backup through GUI, and if you click the report button on the backup window you will notice that some files could not be backed up because of this reason. During a scheduled backup the dsmsched.log will report ANS4042E errors, and the Tivoli Storage Manager server activity log will report ANE4042E. In addition when attempting to use the Web Client to select files that contain characters from another language they will not be displayed. You will see the following error in the dsmsched.log

ANS4042E Object name ????? contains one or more unrecognized characters and is not valid.

Performing Scheduled backups (using scheduler service or dsmcad service), the scheduler and dsmcad services started from the inittab may not have the proper locale environmental settings regardless of the user’s locale settings and if you are running manual backups, the user’s locale environment settings are not able to handle foreign characters. To resolve this issue, you need to change the language settings of the operating system.

For Manual Backups

If you have to perform manual backups, change the variables LANG and LC_CTYPE to en_US by running following commands before opening BA Client GUI.

export LANG=en_US
export LC_CTYPE=en_US

Remember that these settings will be disabled once you close the current session. 


For Scheduled Backups using dsmc sched

If you are performing scheduled backups using (dsmc sched) and if the scheduler is being started from the inittab a script must be used to change the locale settings.

First create a script for starting scheduler service  for example name dsmcsched.sh

#!/bin/sh
DSM_CONFIG=/opt/tivoli/tsm/client/ba/bin/dsm.opt
DSM_DIR=/opt/tivoli/tsm/client/ba/bin/
DSM_LOG=/opt/tivoli/tsm/client/ba/bin/
LANG=en_US
LC_ALL=en_US
export DSM_CONFIG DSM_DIR DSM_LOG LANG LC_ALL
cd /opt/tivoli/tsm/client/ba/bin
dsmc sched & > /tmp/sched.txt 2> /tmp/schederr.txt

Now you have to make  entry in /etc/inittab as below

tsm2:345:once:/opt/tivoli/tsm/client/ba/bin/dsmcsched.sh > /tmp/dsmcsched.txt 2>&1


For scheduled backups using dsmcad

If you are performing scheduled backups using (dsmcad) and if the dsmcad is being started from the inittab,  a script must be used to change the locale settings.

First create a script for starting scheduler service  for example name dsmcad.sh

#!/bin/sh
DSM_CONFIG=/opt/tivoli/tsm/client/ba/bin/dsm.opt
DSM_DIR=/opt/tivoli/tsm/client/ba/bin/
DSM_LOG=/opt/tivoli/tsm/client/ba/bin/
LANG=en_US
LC_ALL=en_US
export DSM_CONFIG DSM_DIR DSM_LOG LANG LC_ALL
cd /opt/tivoli/tsm/client/ba/bin
dsmcad & > /tmp/dsmcad.txt 2> /tmp/dsmcaderr.txt

Now you have to make  entry in /etc/inittab as below

tsm1:345:once:/opt/tivoli/tsm/client/ba/bin/dsmcad.sh > /tmp/dsmcad.txt 2>&1

Any changes made to the inittab might require server restart, so you have to plan accordingly.