HP Integrity NonStop J-Series - Manual (Page 220)

Operations and Management
HP AutoSYNC User’s Guide—522580-017
A-2
MapDB
MapDB
MapDB stores configuration parameters for scheduled synchronizations. The tables in
the MapDB subvolume are:
•
A REGISTRY table to store local parameters. Local parameters are analogous to
global parameters stores in the SysDB REGISTRY table, but they apply only to a
specific MapDB/monitor pair.
•
a SYNCUSER table containing one row per syncuser
•
SFggguuu tables, one for each syncuser, to store parameters pertaining to the
syncfilesets managed by this syncuser
•
SLggguuu files, one for each syncuser to log the output of synchronizations for file
sets managed by this syncuser
Security and ownership of the MapDB tables determines synchronization privileges of
syncusers. For details see
Authorization and Administration on page 4-1.
The SYNCUSER table is created by using the CREATE MAPDB command. The
SFggguuu and SLggguuu are created when syncuser ggguuu is configured by using
the
ADD SYNCUSER command.
Managing the SLggguuu Log File
SLggguuu file is an entry-sequenced file. It is created with primary and secondary
extent sizes of 32 and 64 pages respectively, and with a maximum of 500 extents. The
log file stores a maximum of 15900 records.
AutoSYNC does not delete records from the log until the file fills up, at which point
Autosync deletes the records for oldest day in the log file. If the volume of
synchronization for a given user is such that the AutoSYNC log file fills up in less than
a day, you can create a larger log file. There are two options:
1. Create a new larger log file
•
In AutoSYNC CI, suspend the activity for the syncuser:
SUSPEND SYNCUSER userID;