Performance Tuning for Content Manager

Chapter 14. Maintenance 425

14.8 Replacing or repartitioning a hard disk

If a volume or file system that is used by your Resource Manager becomes full,

you can replace or repartition the physical disk on which it is located to make

more space available.

Replacing or repartitioning the disk invalidates the information stored in the

volumes table (RMVOLUMES) for that volume or file system. When updating the

Resource Manager volumes, do not run the destager at any point of this process.

Otherwise, the volumes will not be the same. Use the following procedures to

update the information in the volumes table.

14.8.1 Replacing the staging volume for UNIX

The directory for the staging volume is in the Resource Manager database table,

RMSTAGING. Follow these steps to replace the staging volume:

1. Change the permissions on the new staging directory to match those of your

Resource Manager ID or what is currently in place for the existing staging

directory.

2. If all files in the existing staging directory are currently read-writeable, you can

skip this step because these files have been destaged already; otherwise,

copy all existing files to the new staging volume:

cp -rp current_staging_directory new_staging_directory

3. Update the location of your staging volume in the Resource Manager

database. Open a DB2 command prompt and enter the following commands,

each on a new line:

db2 "connect to <RM db> user <user ID> using <password>"

db2 "update rmstaging set sta_path=staging_path"

– <RM db> is the Resource Manager database (in our scenario, it is rmdb).

– <user ID> is the user ID (in our scenario, icmadmin) used to connect to the

Resource Manager database.

– <password> is the password for the user ID.

– <staging path> is the location of the staging directory, as an absolute path

with the trailing slash.

14.8.2 Replacing the storage volume for UNIX

The Resource Manager uses the vol_path + the string_table value of lbosdata +

collection + num_bucket_value to develop the path. The logical_volume and

426 Performance Tuning for Content Manager

mount_point are used in various calls to get file system information. Follow these

steps to update the Resource Manager storage volume:

1. Stop the Resource Manager.

2. Change the permissions on the new staging directory to match those of your

Resource Manager ID or what is currently in place for the existing staging

directory.

3. Copy all existing files to the new storage volume:

cp -rp current_storage_directory new_storage_directory

4. Update the location of your storage volume in the Resource Manager

database. Use df -k to determine the FILESYSTEM and MOUNTED ON

location for the new storage directory. To update the storage volume, enter the

following commands, each on a new line:

db2 "connect to <RM db> user <user ID> using <password>"

db2 "select vol_volumeid,vol_logicalname,vol_mountpoint from

rmvolumes"

– <RM db> is the Resource Manager database (in our scenario, it is rmdb).

– <user ID> is the user ID (in our scenario, icmadmin) used to connect to the

Resource Manager database.

– <password> is the password for the user ID.

5. Determine which VOLUMEID is the one you need to change. For example, to

change VOLUMEID=1, the new logical volume is /dev/data1, and mount point

is /rm/data1. Enter:

db2 "update rmvolumes set vol_logicalname='/dev/data1 'where

vol_volumeid=1"

db2 "update rmvolumes set vol_mountpoint='/rm/data1 'where

vol_volumeid=1"

db2 "update rmvolumes set vol_size=0 where vol_volumeid=1"

db2 "update rmvolumes set vol_path='/rm/data1 'where vol_volumeid=1"

db2 "update rmvolumes set vol_freespace=0 where vol_volumeid=1"

6. Start the Resource Manager.

Notice that the latter two steps force the Resource Manager to recalculate the

volume space and capacity during any new stores. These values are reflected in

the RMVOLUMES tables when the Resource Manager shuts down.