1DB_REPLICATE(1) BerkeleyDB Utilities DB_REPLICATE(1)
2
3
4
6 db_replicate - Provide replication services
7
9 db_replicate [-MVv] [-h home] [-L file] [-P password] [-T num-threads]
10 [-t secs]
11
13 The db_replicate utility is a daemon process that provides replica‐
14 tion/HA services on a transactional environment. This utility enables
15 you to upgrade an existing Transactional Data Store application to an
16 HA application with minor modifications.
17
19 -h home
20 Specify a home directory for the database environment; by
21 default, the current working directory is used.
22
23 -L file
24 Log the execution of the db_replicate utility to the specified
25 file in the following format, where ### is the process ID, and
26 the date is the time the utility was started.
27
28 db_replicate: ### Wed Jun 15 01:23:45 EDT 1995
29
30 Additionally, events such as site role changes will be noted in
31 the log file. This file will be removed if the db_replicate
32 utility exits gracefully.
33
34 -M Start the db_replicate utility to be the master site of the
35 replication group. Otherwise, the site will be started as a
36 client replica.
37
38 -P password
39 Specify an environment password. Although Berkeley DB utilities
40 overwrite password strings as soon as possible, be aware there
41 may be a window of vulnerability on systems where unprivileged
42 users can see command-line arguments or where utilities are not
43 able to overwrite the memory containing the command-line argu‐
44 ments.
45
46 -T num-threads
47 Specify the number of replication message processing threads.
48
49 -t secs
50 Specify how often (in seconds) the utility will check for pro‐
51 gram interruption and resend the last log record.
52
53 -V Write the library version number to the standard output, and
54 exit.
55
56 -v Turn on replication verbose messages. These messages will be
57 written to the standard output and will be quite voluminous.
58
59 The db_replicate utility does not attempt to create the Berkeley DB
60 shared memory regions if they do not already exist. The application
61 that creates the region should be started first, and once the region is
62 created, the db_replicate utility should be started. The application
63 must use the DB_INIT_REP and DB_THREAD flags when creating the environ‐
64 ment.
65
66 The db_replicate utility uses a Berkeley DB environment (as described
67 for the -h option, the environment variable DB_HOME, or because the
68 utility was run in a directory containing a Berkeley DB environment).
69 In order to avoid environment corruption when using a Berkeley DB envi‐
70 ronment, db_replicate should always be given the chance to detach from
71 the environment and exit gracefully. To cause db_replicate to release
72 all environment resources and exit cleanly, send it an interrupt signal
73 (SIGINT).
74
76 The db_replicate utility exits 0 on success, and >0 if an error occurs.
77
79 DB_HOME
80 If the -h option is not specified and the environment variable
81 DB_HOME is set, it is used as the path of the database home, as
82 described in DB_ENV->open.
83
85 This utility is not supported for use with the DB SQL APIs.
86
88 db_archive(1) db_checkpoint(1) db_deadlock(1) db_dump(1) db_hot‐
89 backup(1) db_log_verify(1) db_load(1) db_printlog(1) db_recover(1)
90 db_stat(1) db_tuner(1) db_upgrade(1) db_verify(1)
91
92
93
94BerkeleyDB 5.3.28 06 December 2016 DB_REPLICATE(1)