728x90

You must not install ISM on a computer in which a NetWorker server or a NetWorker client is already installed. If you attempt such an installation, it fails with the following message: The ISM setup script detected that another storage manager is installed in /nsr, which conflicts with ISM. If you want to setup ISM, you need to de-install the other storage manager and then run $INFORMIXDIR/bin/ism_startup -init.


For ISM to be installed on a computer that has a NetWorker server or client on it, the NetWorker server or client has to be completely uninstalled first.


To uninstall your currently running ISM on UNIX:

1. Log in as user informix.

2. Change to the ISM binaries directory: 

cd $INFORMIXDIR/bin

3. Become user root.

4. Shut down the ISM daemons: 

./ism_shutdown -q

5. Verify that the daemons are shut down: 

ps -ef | grep nsr

6. Move the ISM executables to a temporary directory: 

mkdir ./ism.tmp 

mv ism* ism.tmp 

mv nsr* ism.tmp 

mv mm* ism.tmp 

mv save* ism.tmp 

mv scanner ism.tmp 

mv usam ism.tmp 

mv recover ism.tmp 

7. Move the ISM catalogs to a temporary directory:

cd $INFORMIXDIR 

mv ism ism.bak 

8. Remove the symbolic link to the ISM catalogs: 

rm /nsr 

9. Remove the call to ism_catalog from the $INFORMIXDIR/onbar script.


Now you are ready to install your new storage manager on UNIX. 


Tip: The ism_shutdown command shuts down the ISM daemons nsrd, nsrexecd, nsrmmdbd, and nsrindexd. It does not uninstall ISM, that is, it does not remove the ISM executables in $INFORMIXDIR/bin, the symbolic link /nsr, or the various ISM files in $INFORMIXDIR/ism.

728x90
728x90

To start ISM on UNIX for the first time, issue the ism_startup -init command. The following shell script is an example of a simple setup for making on–Bar storage-space and logical-log backups to disk files:


#!/usr/bin/ksh

# setup for ISM storage manager

INFORMIXDIR=/data/informix

export INFORMIXDIR


echo "ISM setup begins"


# the user must edit these two lines to select

# appropriate disk locations for storage manager use.

SM_DISKDEV1=/backups/dbspaces

SM_DISKDEV2=/backups/logfiles

export SM_DISKDEV1

export SM_DISKDEV2


# start ISM server

echo "initalize ISM server, must be done as root"

$INFORMIXDIR/bin/ism_startup -init


$INFORMIXDIR/bin/ism_add -admin informix@server (server=hostname)


Important: To make informix the ISM user and thereby ensure informix has access to conduct ISM operations during daily routines, you must run the following command after any ism_startup -init or ISM installation:


# create some devices and media

# the ISM user, defined in ism_add -admin, can do these tasks

echo "create and mount ISM devices and pools"

ism_add -device $SM_DISKDEV1 -type file

ism_add -device $SM_DISKDEV2 -type file

ism_op -label $SM_DISKDEV1 -pool ISMDiskData -volume ISMData

ism_op -label $SM_DISKDEV2 -pool ISMDiskLogs -volume ISMLogs

ism_op -mount $SM_DISKDEV1

ism_op -mount $SM_DISKDEV2

echo "end of ISM setup"



Set ISM environment variables and onCONFIG parameters

If you use ISM, you can specify the volume pool names for storage spaces and logical logs in the ISM_DATA_POOL and ISM_LOG_POOL parameters in the onconfig file. The ISM_DATA_POOL configuration parameter specifies the volumepool that you use for backing up storage spaces. The ISM_LOG_POOL configuration parameter specifies the volume pool that you use for backing up
logical logs.

e.g.
ISM_DATA_POOL ISMDiskData
ISM_LOG_POOL ISMDiskLogs

If you do not set these configuration parameters, they default to the volume pool names ISMData and then ISMLogs.


LTAPEDEV parameter
If you specify a tape device in the LTAPEDEV configuration parameter, ON-Bar ignores the value. on-Bar also ignores the value of the LTAPEBLK, LTAPESIZE, TAPEDEV, TAPEBLK, and TAPESIZE parameters. Consider leaving these parameter values blank when you use on-Bar because the storage manager sets these values.

Important: Set LTAPEDEV to /dev/null or leave it blank on UNIX or NUL on Windows only if you do not want to back up the logical logs. The on-Bar activity log shows a warning and return code 152. Because the database server marks the logical logs as backed up when they are no longer current, on-Bar cannot find logical logs to back up. All transactions in those logs are lost, and you are not able to restore them.

728x90

+ Recent posts