Nov 29

Relocating Tivoli Storage Manager Server DB2 database instance directories

Info Comments Off on Relocating Tivoli Storage Manager Server DB2 database instance directories

Problem(Abstract)

Is it possible to change the location of the local Tivoli Storage Manager Server DB2 database directory?

Resolving the problem

DB2 provides an utility called ‘db2relocatedb’ that can be used to move the existing DB2 database instance directories to a new location. By default, the local database directory is created on the C: drive. It may be necessary to move the local DB2 database instance directory to another drive with more available space.

For example, assume that the local DB2 database instance directory was initially created on the C: drive, as seen in the output from the ‘db2 list database directory’ command below:
1: Dos Command Prompt, enter ‘db2cmd’ to get a DB2 Command Prompt. 2: You will be running all DB2 commands from this new Command Prompt. 3: Issue the following command to get the current DB2 database details details. db2 list database directory
System Database Directory Number of entries in the directory = 1
Database 1 entry: Database alias = TSMDB1 Database name = TSMDB1 Local database directory = C: Database release level = d.00 Comment = TSM SERVER DATABASE Directory entry type = Indirect Catalog database partition number = 0 Alternate server hostname = Alternate server port number =
To change the local database directory from C: to X:, the following actions will need to be performed :
1. As a precaution, perform a full backup of the Tivoli Storage Manager database.
2. Halt the Tivoli Storage Manager Server and ensure that DB2 is also stopped.
3. Copy/move the existing DB2 database instance directory structure to the new location. For example : copy c:\server1\* x:\server1\*

 Ensure that the original directory structure was successfully copied/moved to the new location.

4. Create the configuration file required by the db2relocatedb utility. The configuration file is where all of the required parameters are defined (eg. database name, database instance, new and old directory paths, etc.). Assuming that the database name is TSMDB1 and the DB2 instance is named SERVER1, the configuration file would be as follows : Filename( reloc.cfg ):
DB_NAME=TSMDB1 DB_PATH=C:,X: INSTANCE=SERVER1

 5. Once the configuration file has been created, issue the db2relocatedb command to update DB2 as to the new location of the local DB2 database instance directory path: db2relocatedb -f < reloc.cfg > NOTE: Refer to the DB2 documentation for additional considerations prior to using the db2relocatedb utility.

written by Bosse

Nov 15

REPAIR OCCUPANCY (Repair reporting occupancy for storage pool)

Server Command Comments Off on REPAIR OCCUPANCY (Repair reporting occupancy for storage pool)

Problem(Abstract)

In Tivoli Storage Manager server version 6.x, the cluster records that are used to track occupancy values for a given node may become invalidated such that occupancy values being reported are inaccurate. One result of this problem could be seen in the Query OCCupancy command where the Physical and Logical Space Occupied values are incorrect. Also, the Query STGpool F=D could show an incorrect value for Duplicate Data Not Stored.

Cause

This could be caused during data movement of deleted deduplicated chunks. The Tivoli Storage Manager would add the occupancy of the deleted chunks to the nodes occupancy making the total occupancy invalid. Once the chunk has been deleted it should no longer count towards the overall occupancy. This issue would cause the storage pool to grow from a reporting perspective until deduplication would no longer show proper results.

Another cause could be client side deduplication enabled. This would only cause the number of files being reported to be wrong as opposed to the sizing.

Resolving the problem

Resolving the problem requires upgrading to at least 6.1.5.102, 6.2.3.100 or 6.3.0.0 of the Tivoli Storage Manager. These released levels not only contain the fix from APAR IC73005, but also the utility for fixing the reporting occupancy.

The utility added to Tivoli Storage Manager is called REPAIR OCCUPANCY. This command takes 3 parameters:
REPAIR OCCUPANCY--+-storage_pool_name-+--+-node_name--+--+-FIX--=-No/Yes
Parameters
storage_pool_name (Required) Specifies the name of the storage pool to be fixed. This parameter is required for the utility to work.
node_name (Required) Specifies the name of the client node. The use of wildcards is not acceptable for this command.
FIX Specifies how the server is to resolve the inconsistencies with the reporting occupancy for the storage pool in question. This parameter is optional. The default is NO.

FIX=No

      Tivoli Storage Manager will only report the reported occupancy values and the actual values that will replace the reporting values. These values will not be updated at this time though.

FIX=Yes

    The server will fix any inconsistencies found for the reporting logical occupancy.

Example:Show the current reporting values and what the actual reporting values should be for the requested storage pool Using the REPAIR OCCUPANCY with the parameter FIX=No will display the current reporting values and what the values will be updated to once the command is ran with FIX=Yes.

      REPAIR OCCUPANCY filecopypool node1
      Repair Occupancy: Cluster for Node NODE1 and Filespace Id 2 in pool FILECOPYPOOL contains following reported values: Current Number of files – 11 Current Number of chunks – 2 Current Reported Occupancy – 28917 Current Reported Logical Occupancy – 28946 Current Reported Reported Occupancy – 28946
    Repair Occupancy: Cluster for Node NODE1 and Filespace Id 2 in pool FILECOPYPOOL contains actual values: Actual Number of files – 19 Actual Number of chunks – 8 Actual Reported Occupancy – 189174 Actual Reported Logical Occupancy – 189046 Actual Reported Reported Occupancy – 189046

Example:Repair the reporting values for the storage pool Using the REPAIR OCCUPANCY command with FIX=Yes will look similar to FIX=No but the exception will be additional messaging stating the changes were made.

      REPAIR OCCUPANCY filecopypool node1 FIX=Yes
      Repair Occupancy: Cluster for Node NODE1 and Filespace Id 2 in pool FILECOPYPOOL contains following reported values: Current Number of files – 11 Current Number of chunks – 2 Current Reported Occupancy – 28917 Current Reported Logical Occupancy – 28946 Current Reported Reported Occupancy – 28946
      Repair Occupancy: Cluster for Node NODE1 and Filespace Id 2 in pool FILECOPYPOOL contains actual values: Actual Number of files – 19 Actual Number of chunks – 8 Actual Reported Occupancy – 189174 Actual Reported Logical Occupancy – 189046 Actual Reported Reported Occupancy – 189046
      Repair Occupancy: Updating Cluster for Node NODE1 and Filespace Id 2 in pool FILECOPYPOOL with actual occupancy values.
      Repair Occupancy: SuccessFully updated Cluster for Node NODE1 and Filespace Id 2 in pool FILECOPYPOOL.
      Repair Occupancy: Utility process 7 finished for Node NODE1 and Filespace Id 2 in pool FILECOPYPOOL finished with 1 occupancy clusters found and 1 occupancy clusters updated.
    **** FINAL REPAIR OCCUPANCY STATS **** Repair Occupancy: Filespaces analyzed: 1 Repair Occupancy: Total Filespaces updated: 1

Related information

IC73005

IC73592

written by Bosse

Nov 14

Changing the client GUID on Windows

Windows 2003, Windows 2008 Comments Off on Changing the client GUID on Windows

Question

How do I change the GUID on a Tivoli Storage Manager Backup Archive client?

Answer

GUID is an acronym for Globally Unique IDentifier. The GUIDs are intended to help uniquely identify a particular machine (for reporting purposes), regardless of how many different node names are used on the machine, or which network adapter on the machine is used to connect to the Tivoli Storage Manager server.

In Windows this GUID is stored in the registry under the following location.
HKEY_LOCAL_MACHINE\SOFTWARE\Tivoli\Guid
If it is necessary to remove an old GUID and create a new one the following procedure can be followed.
NOTE: This procedure will require you to modify your Windows Registry. Before doing anything, make sure to backup your registry. This is so you can restore your registry should you accidentally remove something you should not have.

  1. Backup your Windows Registry
  2. Close all client GUI windows and stop all client services
  3. Open the registry and browse to HKEY_LOCAL_MACHINE\SOFTWARE\Tivoli\Guid
  4. Delete/rename the entire GUID folder
  5. Start the client again. This should recreate the GUID folder and a new GUID key

 

written by Bosse