TSM Backup Failures

When a backup fails, the following steps need to be taken to initiate trouble-shooting the problem.

Backup Failure
Windows:

• Log on to the client/node that had the failed back up
• Open up Windows Explorer and go to C:\Program Files\Tivoli\TSM\baclient
• Open up "dsmerror.log" in Notepad and go to the bottom for the latest entry

AIX:

• Log on to the client/node that had the failed back up
• Go to directory: /usr/tivoli/tsm/client/ba/bin
• Open up "dsmerror.log", and go to the bottom for the latest entry.

Common Backup Failures:

• ANS1329S - Server out of data storage space (no available scratch tapes at the time of the backup)
• ANS4037E - The file was in use during the backup and could not be backed up. Quite common on Windows nodes.
• ANE4046E - The file trying to be backed up is corrupt and unreadable. Chkdsk for Windows needs to be run, or for AIX you need to run fsck. Before running those commands, you will need to require approval from CE and also the customer.

Backup Missed:

A backup missed is caused when the client could not be contacted by the server, or the client could not contact the server during the backup-window. There are a number of possible reasons for this, but the common ones are:

• The TSM node is locked
• The TSM node password has expired for access to the TSM server
• The TSM node was not connected to the network, or the node was not running at the time.
• The TSM scheduler on the node was not running

To resolve these, we'll look at them one by one:

The TSM node is locked:

On the TSM server, run the following command: query node

tsm: TSMSERVER01>q node

Node Name Platform Policy Domain Days Since Days Since Locked?

Name Last Acce- Password

ss Set

------------------------- -------- -------------- ---------- ---------- -------

BIGRED_PRD DB2/NT DB2 10 13 No

MICHAELSPC WinNT WINDOWS 14 15 No

MIGSPC WinNT WINDOWS 14 14 Yes

As you can see above, the node "MIGSPC" is Locked. There's normally a good reason for why a node is locked, so you will need to check with the CE and customer before unlocking. If you have been given approval to go ahead and unlock the node, execute the following command:

unlock node MIGSPC

The output should be: ANR2066I Node MIGSPC unlocked.

TSM V6.2.1 Windows Installation Issue (ANR0238E)

Over the last couple of weeks, I've been studying for the Implementation of IBM Tivoli Storage Manager V6.2 certification. Since I hadn't touched TSM for over a year and a half, it was probably best that I went ahead and installed it.

I decided to download the latest version (6.2) for Windows, mainly because I don't actively have access to a Linux or AIX machine at the moment.

When installing IBM Tivoli Storage Manager V6.2.1 for Windows (X64), I ran across a painful issue whereby I was unable to initialize the server instance at the completion of the installation.

When I would start the TSM server, I would receive the following error:

(C) Copyright IBM Corporation 1990, 2010.
All rights reserved.
U.S. Government Users Restricted Rights - Use, duplication or disclosure
restricted by GSA ADP Schedule Contract with IBM Corporation.

ANR4726I The ICC support module has been loaded.
ANR0990I Server restart-recovery in progress.
ANR0152I Database manager successfully started.
ANR0238E A database recovery task is prohibiting activation of TSMDB1 with

sqlcode -1116.

Error SQLCode 1116 definition is: A connection to or activation for database name cannot be made because of BACKUP PENDING.

To resolve the problem, you need to do the following steps:

1. Delete any data inside the TSM database, activelog, archivelog directories.
2. Drop the DB2 TSM database
3. Execute dsmserv format command specifying the database, active and archivelog directories.

Once Step 3 is complete, a successful backup of the TSM DB will have hopefully completed. Then simply initialize the server!