Cannot install TSM 6.x instance after server rename.

The server was renamed after the TSM server installed. so when trying to installing the instance with the new name it failed.

Solution:


You actually don't have to rename back the server.
Try the following:

db2extsec /r /a DB2ADMNS /u DB2USERS

Remove a server instance without uninstalling the TSM server 6.x

1) Open a DOS command prompt and run “db2ilist”. This will list the TSM instances that are defined to DB2.

2) From the DOS command prompt issue “db2idrop <instance name>”. So if the instance you want to remove is “SERVER1? you would issue “db2idrop server1?

3) Open the registry to HKEY_LOCAL_MACHINE\SOFTWARE\IBM\ADSM\CurrentVersion\Server. Here you will find the instance. Remove the instance directory. Do not remove HKEY_LOCAL_MACHINE\SOFTWARE\IBM\ADSM\CurrentVersion\Server itself.

NOTE: Before making any registry changes it is always advised to export the registry incase you need to recover.

4) While in the registry the TSM instance service needs to be removed as well. It is located in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services

NOTE: Before making any registry changes it is always advised to export the registry incase you need to recover.

5) Delete all files located in the instance directory. By default, they are located in C:\Program Files\Tivoli\TSM\<instance name>

6) Delete all log and DB volumes for the instance. The location of these volumes was determined at the time of configuration. There is no default location.

NOTE: Ensure that you are deleting the correct volumes for the instance. If you delete volumes for a different instance than you are removing, that instance will no longer be operational.

7) Also ensure that c:\<instance name> is deleted.

You are now ready to run the config again.

Troubleshooting/Testing VSS using DiskShadow on Windows 2008 By IBM

Problem(Abstract)

When diagnosing problems with SystemState backup or Open File Support/Online Image using VSS, it is sometimes useful to test the VSS portion by itself..

Resolving the problem

With Windows 2008, Microsoft included a tool called DiskShadow.exe that can be used to take snapshots of the system and much more. For the purpose of this technote, we will be limited to performing tests similar to what happens when Tivoli Storage Manager (TSM) performs a SystemState backup, Open File Support backup or an Online Image backup.

Obtain Writer Information:

When troubleshooting a problem, sometimes it is useful to obtain information about the writers, their status and the metadata.

You can start diskshadow and logging all outputs to a file by starting a Command Prompt and launching this command:
diskshadow /l c:\diskshadow.out

From the diskshadow prompt, issue the following commands:

reset
list writers
list writers status
list writers metadata
list writers detailed
list providers
exit

The output of all the above commands will be found in c:\diskshadow.out. The output can use useful to see the list of files which are reported by the VSS writers to be included and excluded by the backup.

Test a snapshot of SystemState

When dealing with SystemState backup failures, sometimes the problem is with TSM, sometimes on Windows either with VSS itself or with one of its writers. Testing outside TSM helps determine if the problem is within TSM or outside.

You can start diskshadow and logging all outputs to a file by starting a Command Prompt and launching this command:
diskshadow /l c:\diskshadowsys.out

From the diskshadow prompt, issue the following commands:

reset
set verbose on
set option differential
set context volatile
add volume c: (if the system is on more than one disk, specify them separated by a space)
create
exit

The output of all the above commands will be found in c:\diskshadowsys.out. Review this file for errors. Any failure during the create phase indicate a problem either with VSS or one of the writers which should be pursued with Microsoft.

Test a snapshot of a disk for Open File Support or Online Image with snapshot provider to VSS

When dealing with a problem doing an open file support backup or online image backup when VSS is used as the snapshot provider, it is sometimes useful to isolate if the problem is within or outside of TSM. This will perform a snapshot of the disk.

You can start diskshadow and logging all outputs to a file by starting a Command Prompt and launching this command:
diskshadow /l c:\diskshadowsnap.out

From the diskshadow prompt, issue the following commands:

reset
set verbose on
set option differential
set context volatile nowriters
add volume c: (replace c: with the drive letter the snapshot is having problems.)
create
exit

The output of all the above commands will be found in c:\diskshadowsnap.out. Review this file for errors. Any failure during the create phase indicate a problem either with VSS or possibly the disk.