Problems Starting TSM Services - Cryptic Messages

When attempting to start TSM services, I recieved some cryptic messages that looked like memory error failures. Upon further investigation, I found some interesting errors in the Application Eventlog of Windows:

TSM Client Acceptor terminated abnormally: appMain exit code 959.

Error Opening/Creating Registry Path 'SOFTWARE\IBM\ADSM\CurrentVersion\BackupClient\Scheduler Service'

TSM Central Scheduler Service terminated abnormally: Error Obtaining Registry Parameters..

These eventually led me to believe the services were corrupted. I uninstalled and reinstalled them and I was able to start them.

Cryptic Messages when Starting Services

I was receiving some cryptic error messages when trying to start TSM services. They looked like memory errors. Upon further investigation and checking the event logs. I noticed entries that reported this:

TSM Central Scheduler Service terminated abnormally: Error Obtaining Registry Parameters..

or

Error Opening/Creating Registry Path 'SOFTWARE\IBM\ADSM\CurrentVersion\BackupClient\Scheduler Service'
or
TSM Client Acceptor terminated abnormally: appMain exit code 959.

Domino TDP "Return Code is 804 Error"

I am documenting this error here because I can never find this on a web search:

Error was found in domarch.log

Return Code is 804
Current date is:
Sun 03/08/2009
Current time is:
08:01 AM

IBM Tivoli Storage Manager for Mail:
Data Protection for Lotus Domino
Version 5, Release 4, Level 2.01
(C) Copyright IBM Corporation 1999, 2007. All rights reserved.

ACD0053E License file (C:\Program Files\Tivoli\TSM\domino\domclient.lic) could not be opened.

Return Code is 804

TSM 6.1 Data Dump for Reference

TSM 6.1 Data Dedupe and DB2 - Curtis Preston

http://www.backupcentral.com/content/view/223/47/

Volume Shadow Services (VSS) - Bane of TSM Administrators

Persistent and frustrating VSS errors have been plaguing our systems. I recently found some good info I wanted to document.


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

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

Cause
Microsoft VSS failures

Solution
This list represents current 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).
Blue represents the most current fix that is available. All the below VSS fixes should be requested from Microsoft.

KBASE# FIX ### WEBSITE LINK:



--------------------------------------------------------------------------------
826936 139876 http://support.microsoft.com/kb/826936
833167 158865 http://support.microsoft.com/kb/833167
867686 188827 No web link
887827 unknown No web link

All of the above fixes are rolled into Windows 2003 SP1. The Microsoft kbase document with the list of fixes included in SP1:
http://support.microsoft.com/?kbid=824721

Subsequent to Win2k3 SP1, Microsoft has provided VSS Post SP1 fix packages:
KBASE# FIX ### WEBSITE LINK:

--------------------------------------------------------------------------------
891957 unknown http://support.microsoft.com/?id=891957
903234 unknown http://support.microsoft.com/?id=903234

Both of the above fixes require this fix as a pre-requisite:
913648 unknown http://support.microsoft.com/?id=913648

http://www-1.ibm.com/support/docview.wss?uid=swg21242128

Redirected Restore for DB2 using TSM

I was asked last week about restoring a DB2 database from one server to another server. After a quick bit of searching, I found this article. The DBA's are going to test it this week to see how well it works. I thought I would document it so I don't lose the link:


http://www.ibm.com/developerworks/db2/library/techarticle/0212mulligan/0212mulligan.html

NetApp Quick Learnings

• 16 TB's of raw storage per aggregate.
• Data not shared between aggregates.
• Always leave at least one spare disk in NetApp. If you don't, NetApp freaks out.
• A mixture of SATA and FC drives can be used in the same NetApp device. However, you cannot mix drives in an aggregate. They must all be the same type of drive.
• Min number of drives per array is 3, but drives can be added to expand the array.
• When creating an array, 2 drives must be used as parity.

Maximum and default RAID group sizes - from NetApp

Maximum and default RAID group sizes vary according to the storage system model, level of RAID group protection provided, and the types of disks used in the RAID group. Generally, you should use the default RAID group sizes.

Table 1. RAID group sizing for RAID-DP groups
Disk type Minimum group size Maximum group size Default group size
ATA or SATA 3 16 14
FC or SAS 3 28 16

Table 2. RAID group sizing for RAID4 groups
Storage system model Minimum group size Maximum group size Default group size
FAS250 2 14 7
All other models using ATA or SATA disks 2 7 7
All other models using FC or SAS disks 2 14 8

NetApp Ontapp Simulator + CentOS + Computer Hardware = NetApp Learning Fun!!

You'll need a NOW account to get the Ontap Simulator. Here's a link to some general info about it:
http://partners.netapp.com/go/techontap/matl/sample/0206tot_monthlytool.html
CentOS to get some RH Linux experience:
http://www.centos.org/
http://centos.mirrors.tds.net/pub/linux/centos/5.2/isos/x86_64/

TSM Operational Reporter

What is TSM Operational Reporter and where to get it?

http://www.tek-tips.com/faqs.cfm?fid=5643

Old PPT file showing TSM-OR:

ftp://service.boulder.ibm.com/storage/tivoli-storage-management/techprev/tsmopreport/latest/tsmrept_walk_through_d7.ppt

The IBM FTP site:

ftp://ftp.software.ibm.com/storage/tivoli-storage-management/maintenance/server/v5r4/WIN/5.4.3.0

Download: tsmcon54X0_win.exe

View DSMError.log and DSMSched.log Files Batch File

This batch file has been invaluable to me in checking error and sched logs every day. Drop this into a text file and save it as a batch. When launched the batch file deletes the current Z drive mapping, asks for the server name you would like to view. After entering a server name and hitting enter the batch pings the server and maps a new Z drive to the baclient folder of TSM. It then copies over the DSMError.log and DSMSched.log files to your C:\Temp folders and opens them one at a time starting with the DSMError.log. You have to close the error log for the DSMSched.log to come up. If the batch file cannot map the drive, it may hang or a message in the command line window and then open the last dsm files that were copied. So in a way, it troubleshoots the connection to the server right off the bat.

@echo off
net use z: /delete
Echo View TSM DSMError Logss
Echo Enter the name of the server you would like to view:
SET /p servername=
ping "%servername%"
net use z: "\\%servername%\c$\program files\tivoli\tsm\baclient"
z:
copy "z:\dsmerror.log" "C:\temp"
copy "Z:\dsmsched.log" "C:\temp"
"C:\temp\dsmerror.log"
"C:\temp\dsmsched.log"
quit

TSM Client for Windows 2k and Windows 2k3 Regarding Core System File Restores

Windows Server 2k refers to registry and other core files as System Objects.Windows Server 2k3 refers to registry and other core files as System State and System Services.

Both groups of files can only be restored while connected to TSM through the original machine. You cannot restore these files to another server first. Restore will then prompt for registry activation. It is not recommended to restore these files and not activate them. If you choose to activate, TSM will prompt for restart when restore is complete.