You are here: Administration > Man Pages > lk_chg_value(8)

lk_chg_value(8)

NAME

lk_chg_value(8) - changes specified values in the LifeKeeper local configuration database (LCD).

SYNOPSIS

LKROOT/bin/lk_chg_value -o old_value -n new_value -f filename [-vFIMT]

DESCRIPTION

This command should be used to modify arbitrary values in LifeKeeper's local configuration database (LCD).  You can modify such values as the LifeKeeper uname, comm path addresses, resource tag names, etc. This command should be run locally on each machine in your cluster configuration. Ensure that you are logged on as the root user and that LifeKeeper is not running before executing lk_chg_value.  This command does not modify the system's uname or network interfaces.  If you wish to modify the LifeKeeper uname or comm path address, first you must modify the system's uname and network interfaces (using system utilities) before executing lk_chg_value.  In order to properly update LifeKeeper, you must run lk_chg_value on every system in your cluster.

The values you wish to modify may be specified on the command line using the the -o and -n options or in a file using the -f option.  The syntax for a file containing LCD value substitutions is:

old_value=new_value

with one substitution per line.  Substitutions that are not presented in this format will be ignored.  

To view changes that lk_chg_value will make without modifying any LifeKeeper files, use the -M option.  To identify the files that lk_chg_value is examining, use the -v option.  If you do not wish to modify tag names, use the -T option.  If you do not wish to modify resource ids, use the -I option.

EXAMPLES

Systems A, B, and C have been configured in a LifeKeeper configuration. Systems A and B manage a database resource and system A also manages a communication resource with system C.  To modify the uname and comm path address of system A with comm path old_address perform the following:

  1. Stop LifeKeeper by executing the lkstop command on each affected system. However, if the resources being managed are to stay available to the user community, execute lkstop -f.

  2. Change System A's uname to X and change the network address to new_address.  Create the  substitution file, /tmp/lksubs, containing the following substitution pairs:

A=X

old_address=new_address

  1. As root, login to system A and execute the following:

$LKROOT/bin/lk_chg_value -vf /tmp/lksubs

  1. This replaces all local occurrences of A with X and old_address with new_address found within the LifeKeeper core and recovery kits on system A, which is now identified as system X.
  2. Copy the substitutions file from system A to systems B and C.  Login as root to systems B and C and execute the following:

$LKROOT/bin/lk_chg_value -vf /tmp/lksubs

  1. This replaces all occurrences of A with X and old_address with new_address within the LifeKeeper configuration database on systems B and C.

EXIT CODES

The following exit codes could be returned by this command:

0

Execution of command completed successfully.

1

Interrupt occurred...files restored.

2

Invalid arguments passed to command.

3

LifeKeeper processes are still running.

4

Command needs to be executed by root login.

NOTES

The location of the utility, LKROOT, is defined in the default file /etc/default/LifeKeeper.

FILES

/etc/default/LifeKeeper

© 2012 SIOS Technology Corp., the industry's leading provider of business continuity solutions, data replication for continuous data protection.