A operations and management, Autosync configuration database, Sysdb – HP NonStop G-Series User Manual
Page 223: A. operations and management, Autosync, Configuration database, Appendix a, operations and, Management, For det, Appendix a, operations and management
HP AutoSYNC User’s Guide—522580-020
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
AutoSYNC prevents synchronizations into the current active SysDB and MapDB
destination subvolumes.
The current active destination SYSDB and MapDB subvolumes are also automatically
excluded from being purged through the use of the PURGE and SUBVOLPURGE
options.
These exclusions protect the integrity of the destination SysDB and MapDB
subvolumes. The destination MapDB subvolume is used for recovery processing, and
purging files in the MapDB subvolume can cause file recovery to fail.
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.