OPT File Domain Statements

I've been working to clean up duplicate backups in our Windows Cluster environment. The general backup was also picking up all the cluster drives, so a modification of the domain statement was needed. Here are two examples of domain statements I wanted to document for future use:

Win2k3 Server TSM Client
DOMAIN C: D: SYSTEMSTATE SYSTEMSERVICES

Win2k Server TSM Client
DOMAIN C: D: SYSTEMOBJECT

You should also restart the Sched and CAD services after you modify the domain statement to ensure that the TSM server sees the update OPT file.

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