Performance Tuning for Content Manager

428 Performance Tuning for Content Manager

5. The next time the Resource Manager writes or deletes an object, the

information is read from the new disk or partition and placed in the volume’s

table.

6. If your volume is on a different partition, manually edit the RMVOLUMES table

to update the VOL_LOGICALNAME and VOL_MOUNTPOINT.

For example, assume that the volume that you wish to replace is defined in

the RMVOLUMES table entry with VOL_VOLUMEID=1. If your new partition

is F and this partition is labeled FDRIVE, enter:

UPDATE RMVOLUMES set VOL_LOGICALNAME='FDRIVE' where vol_volumeid=1

UPDATE RMVOLUMES set VOL_MOUNTPOINT='f:' where vol_volumeid=1

7. Start the Resource Manager.

14.9 Backup

This section covers backup of the Content Manager system.

14.9.1 Backup for Content Manager Multiplatforms

For Content Manager on Multiplatforms, it is important to back up four key

components:

 The Library Server database: Use your database manager tools to facilitate

this.

 The Resource Manager database: Use your database manager tools to

facilitate this.

 The LBOSDATA directory on every Resource Manager.

 Tivoli Storage Manager (TSM) volumes: It is important to remember to back

up any data that is migrated to TSM via Content Manager migration policies;

otherwise, you will have a single point of failure and data loss within your

system. This can be accomplished by using TSM copy storage pools, which

might be made up of tape volumes that can be stored off site.

It is not necessary to back up objects in the staging area, because all of the

objects in this directory exist elsewhere in the system, so have been backed up

already if you use the guideline above.

With these four key components, you can rebuild your Content Manager system,

even if the original server is completely destroyed.

Chapter 14. Maintenance 429

If you choose to back up only the four components listed above (as opposed to a

full system backup), you need to reinstall the Content Manager code and its

software prerequisites onto another machine, in case the original machine is

destroyed. The time taken to reinstall a system should be considered when

forming a recovery plan, and you must also make sure you have easy access to

the installation media, with the original CDs or a network drive.

If at all possible, perform full backups for each of your Content Manager servers.

A hierarchical storage management product such as TSM is ideal for this. When

choosing the type of media for backing up your system, consider the relative

speed of the media. For example, restoring a DB2 database backup that spans

multiple magnetic tapes takes much more time than restoring the same database

backup from a fiber attached storage area network (SAN).

TSM can also be used to back up database backup images and database logs.

These backups can be stored on any type of media that TSM supports; therefore,

it is possible to back up DB2 archive logs to tape volumes on TSM automatically,

reducing the amount of storage space needed on the server running DB2. DB2

can be integrated with TSM so that DB2 commands can be run as follows:

db2 backup database icmnlsdb use tsm

For information about integrating DB2 and TSM to provide this type of

functionality, refer to Backing Up DB2 Using Tivoli Storage Manager, SG24-6247.

Be sure to you back up all components of the Content Manager system together.

If you need to restore the system later, each component must be from the same

point in time.

1. Identify the LBOSDATA areas. Run the appropriate query for your operating

system: for UNIX, select vol_mountpoint from rmvolumes; for Windows,

select vol_logicalname from rmvolumes.

2. Pause the system.

3. Perform the backups. Back up:

– Library Server database

– Resource Manager database

– LBOSDATA areas

– Data stored in Tivoli Storage Manager

If possible, before backing up the database, perform db2stop/db2start to

ensure that there are no clients or services connecting to the database in

order to perform full backup. Or, for DB2 UDB V8.2 or higher, use the quiesce

command. For more information about this command, refer to IBM DB2

Universal Database Command Reference, SC09-4828.

4. Resume the system.