beautypg.com

Configuring an alternate sysdb, N procedures, see, Migrating the nonstop – HP Integrity NonStop J-Series User Manual

Page 181: Migrating the nonstop autotmf software, Migrating the nonstop autotmf, System. see

background image

System Management

HP NonStop AutoTMF Software User’s Guide429952-016

A-7

Configuring an Alternate SysDB

Issue the OPEN command after executing the CI:

Configuring an Alternate SysDB

The SysDB has been engineered to be version-tolerant; multiple versions of AutoTMF
can use the same SysDB concurrently. If however, you must completely segregate
operating environments, you can also configure a separate SysDB and MapDB.

To configure an alternate system database, the following steps are required:

1. Use the

=_ESCORT_SYSDB

DEFINE to specify an alternate SysDB subvolume.

Do not use the ESCSYSDB subvolume name.

2. In the CI, issue the

CREATE SYSDB

command to create the new SysDB.

3. Enter your license.

4. Issue the

CREATE MAPDB

command to create an alternate MapDB. You must

specify an alternate monitor process name.

5. Use the

=_ESCORT_SYSDB

DEFINE whenever using the CI. This is especially

important when issuing the START MONITOR command. The alternate SysDB
DEFINE is not required to run application programs, since the application
programs do not access SysDB, except through the monitor process.

6. Associate the new MapDB and monitor with programs by using one of the methods

described above in

Associate the alternate MapDB and monitor with programs

.

Migrating the NonStop AutoTMF Software
Configuration to a New System

Three commands can assist you in migrating the AutoTMF configuration to a new
system:

To migrate global parameters:

To migrate Monitor and MapDB configuration:

To migrate Program and File Attributes:

AutoTMF 2? open $ztst;

MODIFY GLOBALS

REPLACE SYSTEMNUMBER n [, LISTALL ];

MODIFY MAPDBS

REPLACE NODENAME node [, LISTALL ];

MODIFY AUTOTMF

REPLACE NODENAME node [, LISTALL ];

This manual is related to the following products: