db_hotbackup [-cDEguVv] [-d data_dir ...] [-h home]
[-l log_dir] [-P password] -b backup_dir
The db_hotbackup utility creates "hot backup" or "hot failover" snapshots of Berkeley DB database environments. Hot backups can also be performed using the DbEnv::backup() or DbEnv::dbbackup() methods.
The db_hotbackup utility performs the following steps:
Sets the
DB_HOTBACKUP_IN_PROGRESS
flag in the home database environment.
If the -c option is specified, checkpoint the source home database environment, and remove any unnecessary log files.
If the target directory for the backup does not exist, it is created with mode read-write-execute for the owner.
If the target directory for the backup does exist and the -u option was specified, all log files in the target directory are removed; if the -u option was not specified, all files in the target directory are removed.
If the -u option was not specified, copy application-specific files found in the database environment home directory, and any directories specified using the -d option, into the target directory for the backup.
Copy all log files found in the directory specified by the -l option (or in the database environment home directory, if no -l option was specified), into the target directory for the backup.
Perform catastrophic recovery in the target directory for the backup.
Remove any unnecessary log files from the target directory for the backup.
Reset the
DB_HOTBACKUP_IN_PROGRESS
flag in the environment.
The db_hotbackup utility does not resolve pending transactions that are in the prepared state. Applications that use DbTxn::prepare() must specify DB_RECOVER_FATAL when opening the environment, and run DbEnv::txn_recover() to resolve any pending transactions, when failing over to the backup.
The options are as follows:
-b
Specify the target directory for the backup.
-c
Before performing the backup, checkpoint the source database environment and remove any log files that are no longer required in that environment. To avoid making catastrophic recovery impossible, log file removal must be integrated with log file archival.
-D
Use the data and log directories listed in a DB_CONFIG configuration file in the source directory. This option has four effects:
The specified data and log directories will be created relative to the target directory, with mode read-write-execute owner, if they do not already exist.
In step #3 above, all files in any source data directories specified in the DB_CONFIG file will be copied to the target data directories.
In step #4 above, log files will be copied from any log directory specified in the DB_CONFIG file, instead of from the default locations.
The DB_CONFIG configuration file will be copied from the source directory to the target directory, and subsequently used for configuration if recovery is run in the target directory.
Care should be taken with the -D option where data and log directories are named relative to the source directory but are not subdirectories (that is, the name includes the element "..") Specifically, the constructed target directory names must be meaningful and distinct from the source directory names, otherwise running recovery in the target directory might corrupt the source data files.
It is an error to use absolute pathnames for data or log directories in this mode, as the DB_CONFIG configuration file copied into the target directory would then point at the source directories and running recovery would corrupt the source data files.
-d
Specify one or more directories that contain data files to be copied to the target directory.
As all database files are copied into a single target directory, files named the same, stored in different source directories, would overwrite each other when copied to the target directory.
Please note the database environment recovery log references database files as they are named by the application program. If the application uses absolute or relative pathnames to name database files, (rather than filenames and the DbEnv::add_data_dir() method or the DB_CONFIG configuration file to specify filenames), running recovery in the target directory may not properly find the copies of the files or might even find the source files, potentially resulting in corruption.
-F
Directly copy from the filesystem. This option can CORRUPT the backup if used while the environment is active and the operating system does not support atomic file system reads. This option is known to be safe only on UNIX systems, not Linux or Windows systems.
-g
Turn on debugging options. In particular this will leave the log files in the backup directory after running recovery.
-h
Specify the source directory for the backup. That is, the database environment home directory.
-l
Specify a source directory that contains log files; if none is specified, the database environment home directory will be searched for log files. If a relative path is specified, the path is evaluated relative to the home directory.
-P
Specify an environment password. Although Berkeley DB utilities overwrite password strings as soon as possible, be aware there may be a window of vulnerability on systems where unprivileged users can see command-line arguments or where utilities are not able to overwrite the memory containing the command-line arguments.
-u
Update a pre-existing hot backup snapshot by copying in new log files. If the -u option is specified, no databases will be copied into the target directory. If applications that update the environment are using the transactional bulk insert optimization, this option must be used with special care. For more information, see the section on Hot Backup in the Getting Started With Transaction Processing Guide.
-V
Write the library version number to the standard output, and exit.
-v
Run in verbose mode, listing operations as they are done.
The db_hotbackup utility uses a Berkeley DB environment (as described for the -h option, the environment variable DB_HOME, or because the utility was run in a directory containing a Berkeley DB environment). In order to avoid environment corruption when using a Berkeley DB environment, db_hotbackup should always be given the chance to detach from the environment and exit gracefully. To cause db_hotbackup to release all environment resources and exit cleanly, send it an interrupt signal (SIGINT).
The db_hotbackup utility exits 0 on success, and >0 if an error occurs.
If the -h option is not specified and the environment variable DB_HOME is set, it is used as the path of the database home, as described in the DbEnv::open() method.