Migrating ISM 1.0 to ISM 2.2

You can either upgrade ISM 1.0 to ISM 2.2 alone or upgrade ISM with the database server version.

Migration reinstalls the ISM binaries but maintains the ISM data (the catalogs and tape volumes that contain the save sets).

The following section explains how to migrate ISM 1.0 to ISM 2.2. ISM 2.2 includes changes to the format of data in the ISM catalogs and volumes. Begin the following procedure with ISM 1.0 running on your old database server version.

To migrate ISM

Complete a full backup of your system with one of the following commands:
```
onbar -b -w 
onbar -b -L 0
```
Create a bootstrap of your ISM 1.0 server with the following command:
```
ism_catalog -create_bootstrap -pool ISMData
```
The bootstrap is a copy of the files and directories in $INFORMIXDIR/ism/mm, index, and res (UNIX) or %ISMDIR%\mm, index, and res (Windows). These directories are backed up into a single save set, called the bootstrap.
Shut down the ISM 1.0 server.
UNIX Only
On UNIX:
```
ism_shutdown 
```
End of UNIX Only

Windows Only
On Windows:
```
ism_shutdown -deinstall 
```
End of Windows Only
Remove the ISM 1.0 catalogs.
Warning:

Do not remove the res directory.

UNIX Only
On UNIX:
```
rm -rf $INFORMIXDIR/ism/index 
rm -rf $INFORMIXDIR/ism/mm
```
End of UNIX Only

Windows Only
On Windows:
```
del %ISMDIR%/index
del %ISMDIR%/mm
```
End of Windows Only

If you have file-type devices configured in ISM, you cannot move, copy, or rename the directories that contain those devices.
Remove ISM 1.0. (This step is optional.)
Follow the instructions on how to remove ISM 1.0 in Uninstalling ISM. Use regedt32 to check the registry keys.
On Windows, you must rename or remove the ISM 1.0 bin directory because the ISM 2.2 installer installs the ISM files in a different directory. Then move the ISM 2.2 bin directory to the ISM 1.0 bin directory location.
Install the new ISM 2.2 files, either separately or with the new database server version.
Warning:

You must install the new ISM 2.2 files in the same directory as the ISM 1.0 files.
If you are upgrading ISM on Windows, follow these steps to ensure that ISM is properly configured.
1. The installer might have made a Windows command window script for the Informix environment. The filename of this script is servername.CMD.
2. Edit this file to be sure that ISMDIR and PATH are correct for the location of the ISM 2.2 directory.
3. Change the %INFORMIXDIR%\bin\onbar.bat file for any user-customized references to the ISM directory.
4. If necessary, edit the %INFORMIXDIR%\bin\SETISM.BAT file to ensure that it refers to the ISM 2.2 directory.
5. Check your database server configuration file (usually %INFORMIXDIR%\etc\ONCONFIG.servername). Be sure that the BAR_BSALIB_PATH parameter points to the libbsa.dll in the bin subdirectory of the ISM 2.2 directory.
6. Check Windows system environment variable settings that affect the PATH environment variable or that set the ISMDIR environment variable.
7. Copy the sm_versions.std file to create a new sm_versions file.
8. If you changed the configuration files, you might need to reboot Windows.
Warning:

An error message that an entry point cannot be found in libnsr.dll means part of the Windows configuration still references the old ISM installation.
Start the ISM server with the following command. Do not initialize the server.
```
ism_startup
```
Place the tape that contains the bootstrap in a device and mount it, if it is not already mounted.
Create an index for your host with the following command:
```
nsrck -c
```
Locate the bootstrap on the tape and note the save-set ID: ism_catalog -find_bootstrap device_name.
Recover your bootstrap with the following command:
```
ism_catalog -recover
```
Important:

Do not replace the res directory with the res.R directory. Wait for the preceding command to issue a message that the index was fully recovered.
Remove all the defined devices with the following command. You must unmount each device individually.
```
ism_op -unmount device_name
```
Segregate all ISM 1.0 volumes. Make backups of file-type devices.
Important:

For future use, you must store the tape with the bootstrap that you created in step 2. Without the bootstrap, you cannot revert to ISM 1.0 if you need to.
Label new volumes.
ISM 2.2 must not write to any ISM 1.0 volumes because they would be unreadable by ISM 1.0 if you chose to revert.
```
ism_op -label device_name -volume volume_name -pool
ISMData
```
Mount the new volumes with the following command for each device:
```
ism_op -mount device_name
```
Create a new bootstrap to back up the converted indexes.
```
ism_catalog -create_bootstrap -pool ISMData
```
Upgrade the database server to the new version if necessary, and then start the database server.
Immediately perform a level-0 backup.
```
onbar -b -L 0
```