Rearranging things later

For a number of reasons, you may decide to relocate either the Razor database, or the Razor executables.

Moving where the release resides

Although it is possible to move our release to a new directory, we encourage you to simply perform a fresh installation in the new area. The installation process (rz_install) generates a number of files which serve to assist our scripts. Finding and modifying all those files is time consuming and error prone.

1. Make sure that all of the existing Razor programs have been terminated. Refer to "Stopping the database server" on page 42 and "Stopping the license manager" on page 40.

2. Go to where the present release is stored and remove the Razor symbolic link. This prevents people from accidentally invoking and using the tool from its present location.

# cd /home/razoradm
# rm Razor

3. Go to where you'd like the release to now reside and do a fresh installation as described above.

4. Find the rz_prep and rz_prep.sh files for each database you have and edit them. You will need to change the RAZOR_HOME environment variable to point to where the release now exists.

IMPORTANT NOTE: These two files MUST be kept in sync!

5. Review whatever sys-admin files may also be affected by this change. If any of them called out the full path name to the prior release area, they will also need to be modified.

Once the above steps are complete, have each user re-reference their related rz_prep file, and everything should start back up just fine. Once you are sure that everything is proceeding fine, you are free to go back and completely remove the original installation.

Moving a database to new location

A Razor database is stored on a disk as a directory tree and a broad collection of files (refer to "$RAZOR_UNIVERSE_DIR How a database lays out" on page 253.) Moving the database to a new disk or parent directory can be down with whatever mechanisms you would use to move any other directory, i.e. UNIX command "mv". Prior to moving any Razor database, make sure that no client applications are connected and that the database server is not running. Remember to move the directory structure, RAZOR_UNIVERSE, as well as the files rz_prep and rz_prep.sh. Once the move is completed, edit the files, rz_prep and rz_prep.sh, correcting the setting of RAZOR_UNIVERSE_DIR to refer to the new location of the database. Reset the Razor environment variables by sourcing (or dotting), refer to "Starting Razor" on page 38, the modified rz_prep (or rz_prep.sh) file.

If the database has been moved to a different operating system, the owner of the database must do the following:

# cp $RAZOR_HOME/bin/rz_exec \
$RAZOR_UNIVERSE_DIR/bin/<OS>/rz_db_exec 1
# chmod a+x $RAZOR_UNIVERSE_DIR/bin/<OS>/rz_db_exec
# chmod ug+s $RAZOR_UNIVERSE_DIR/bin/<OS>/rz_db_exec

remember to change all references to the file rz_prep.sh in files that exist in the scripts directory ($RAZOR_UNIVERSE_DIR/Scripts) to reference the new location of this file.

You will also have to hunt down and modify all references to the original rz_prep files. A common trick is to leave a "placebo" rz_prep file in the original location. The placebo file can simply echo out some statements as to where the present rz_prep files now reside.

NOTE: If you are changing operating systems, you need the appropriate distribution for that new system.

¹ Razor releases prior to v4.1d did not create bin/<OS> in $RAZOR_UNIVERSE_DIR. Refer to "$RAZOR_UNIVERSE_DIR How a database lays out" on page 253 for the operating system nomenclature.