A operations and management, Autosync configuration database, Sysdb – HP Integrity NonStop J-Series User Manual
Page 219: A. operations and management, Ables are created. see, Appendix a, operations and management, For a list of va, Operations and management
HP AutoSYNC User’s Guide—522580-017
A-1
A
Operations and Management
This appendix describes the management of AutoSYNC.
The topics covered are the following:
AutoSYNC Configuration Database
Configuring and Using an Alternate AutoSYNC Environment
Migrating the Configuration Database
AutoSYNC Configuration Database
The configuration information is stored in two subvolumes:
1. SysDB: global parameters and licensing information
2. MapDB: syncuser and syncfileset information and synchronization output
SysDB
The System Database (SysDB) consists of two SQL tables:
•
MAPDBS to store the description of map databases and associated monitor
processes.
•
REGISTRY to register a product license and other system-wide (global)
configuration parameters.
Each system has a single SysDB in the $SYSTEM.ESCSYSDB subvolume, but
SYSDB may also reside on another volume. There should be only one SysDB
subvolume named ESCSYSDB.
You need write access to the SysDB to create or alter MapDB, to specify the product
license, or alter global configuration parameters. You need read access to execute
some commands, especially to start the monitor process.
When AutoSYNC needs to access the SysDB, it looks first for SysDB tables in
$SYSTEM.ESCSYSDB. If the tables do not exist, it then searches all disks for a
SysDB in the ESCSYSDB subvolume. If there is more than one SysDB, the command
interpreter terminates with an error.