Updating the sm_versions File

The storage manager must have an entry in the sm_versions file. If you are using ISM, put ism in the sm_name field of sm_versions. To find out which code name to use in sm_versions for third-party storage managers, see the storage-manager documentation.

XBSA_ver is the release version of the XBSA shared library for the storage manager. sm_name is the name of the storage manager. sm_ver is the storage-manager version. The maximum field length is 128 characters.

Before ON–Bar starts a backup or restore process, it calls the currently installed version of the storage-manager-specific XBSA shared library to get its version number. If this version is compatible with the current version of ON–Bar and is defined in the sm_versions file, ON–Bar begins the requested operation.

To update the storage-manager definition in sm_versions

Copy the sm_versions.std template to a new file, sm_versions in the $INFORMIXDIR/etc directory on UNIX or the %INFORMIXDIR%\etc directory on Windows.
If you are using ISM, issue the ism_startup -init command to automatically update sm_versions with the correct version number and storage-manager name or manually edit sm_versions.
If you are installing an ISM patch, you must manually edit sm_versions.

Warning:

The ism_startup -init command erases records of previous backups.
If you are using a third-party storage manager, the vendor supplies the definition for the sm_versions file. Create your own sm_versions file with the correct data for the storage manager using the format in sm_versions.std as a template.

If all coservers share the sm_versions file in the etc subdirectory, the sm_versions file should have an entry for each storage-manager brand.
If the etc subdirectory is not shared between coserver nodes, specify one line in the sm_versions file for the storage manager in use on that coserver node.
Stop any ON–Bar processes (onbar_d, onbar_w, or onbar_m) that are currently running and restart them for the changes to take effect.