Open topic with navigation
lkbackup - LifeKeeper configuration backup utility
lkbackup [ -c | -d | -l | -x ] [-n] [-v] [-f archive] [--cluster] [--help][--rsh] [--ssh]
Performs backup and restore of LifeKeeper configuration files.
Create archive. If no archive is specified, then create one in the default location with a file name using the current date YYMMDDHHMM.
Find differences between an archive and current LifeKeeper configuration files. If no archive is specified, then uses the latest archive found in the default location.
List the archives found in the default location.
Extract (restore) files from an archive, overwriting the current LifeKeeper configuration. This will restore a previous LifeKeeper configuration from an archive. The existing LifeKeeper configuration will be lost. The command checks that LifeKeeper is stopped before extracting files. If no archive is specified, then uses the latest one found in the default location.
List names of files to be processed, but do not process them. This is a dry run or test option to see what files would be affected by a backup or restore. With -c option, list files that would go into created archive, without creating an archive. With -x option, list the files in the archive, without extracting them.
Verbosely list files processed.
Specifies archive file. Optional. If this option is not specified, then the latest archive found in the default location will be used.
Run lkbackup on each system in the cluster. For remote execution, if ssh is found in the path, then use ssh, else use rsh. The rsh/ssh default choice can be overridden with the --rsh and --ssh options. By using ssh or rsh instead of lcdremexec, lkbackup does not require LifeKeeper to be running. For confirmation prompts, lkbackup uses stdin over ssh or rsh.
Display help message.
Use rsh for remote execution when using cluster option.
Use ssh for remote execution when using cluster option.
Default archive with date in the name. The archive is a tar file in gzip format.
Optional file to contain custom list of additional files to be backed up. By adding file names to this list, the user customizes the list of files to be backed up. This file is not modified by lkbackup.
In lkbackup.files, specify files relative to the root directory (/). In lkbackup.files, environment variables are evaluated and wildcards are expanded. For example, to specify files relative to the LifeKeeper installed location, at the beginning of the pathname use environment variable $LKROOT, which is defined in /etc/default/LifeKeeper.
Optional files to contain custom list of additional files to be backed up which are specific to the recovery kits. These files are created by the author of the recovery kit, and users should not modify them.
The standard list of backup files includes:
To create a backup of LifeKeeper configuration files, putting the backup into a specified archive file:
lkbackup -c -f archive
Create backups of the LifeKeeper configuration for each server in the cluster, using the default archive file, which is created on each server in the cluster:
lkbackup -c --cluster
Specifying the backup archive file, which is created on each server in the cluster:
lkbackup -c -f archive --cluster
To list archive files found in the standard location, $LKROOT/config, for each server in the cluster:
lkbackup -l --cluster
To restore a system from scratch, given a fresh LifeKeeper install and an archive file:
make sure LifeKeeper is stopped (lkstop)
set up LKROOT and PATH in the /etc/default/LifeKeeper file
extract files from lkbackup archive (lkbackup -x -f archive)
© 2012 SIOS Technology Corp., the industry's leading provider of business continuity solutions, data replication for continuous data protection.
Open topic with navigation