HP-UX: Running multiple server instances on a single system

You can create more than one server instance on your system. Each server instance has its own instance directory, and database and log directories.

Multiply the memory and other system requirements for one server by the number of instances planned for the system.

The set of files for one instance of the server is stored separately from the files used by another server instance on the same system. Use the steps in HP-UX: Creating the server instance for each new instance, including creation of the new instance user.

To manage the system memory that is used by each server, use the DBMEMPERCENT server option to limit the percentage of system memory. If all servers are equally important, use the same value for each server. If one server is a production server and other servers are test servers, set the value for the production server to a higher value than the test servers.

When you upgrade from Tivoli Storage Manager V6.1, you must upgrade to V6.3 first, and then to V7.1.4. You can upgrade directly from either V6.2 or V6.3 to V7.1. See the upgrade section (Upgrading to Tivoli Storage Manager Version 7.1.4) for more details. When you upgrade and have multiple servers on your system, you must run the installation wizard only once. The installation wizard collects the database and variables information for all of your original server instances.

If you upgrade from Tivoli Storage Manager V6.2 or V6.3 to V7.1.4 and have multiple servers on your system, all instances that exist in DB2® V9.7 are dropped and recreated in DB2 V10.5. The wizard issues the db2 upgrade db dbname command for each database. The database environment variables for each instance on your system are also reconfigured during the upgrade process.