2008-10-08 16:50:13 +04:00
.TH VGCFGBACKUP 8 "LVM TOOLS #VERSION#" "Sistina Software UK" \" -*- nroff -*-
2002-01-04 23:35:19 +03:00
.SH NAME
2014-06-11 13:06:30 +04:00
vgcfgbackup \(em backup volume group descriptor area
2002-01-04 23:35:19 +03:00
.SH SYNOPSIS
.B vgcfgbackup
2014-05-21 16:53:56 +04:00
.RB [ \- \- commandprofile
.IR ProfileName ]
2002-01-04 23:35:19 +03:00
.RB [ \- d | \- \- debug ]
2012-04-11 16:42:10 +04:00
.RB [ \- f | \- \- file
2016-03-03 01:51:59 +03:00
.IR Filename ]
2002-01-04 23:35:19 +03:00
.RB [ \- h | \- \- help ]
2002-11-18 17:04:08 +03:00
.RB [ \- \- ignorelockingfailure ]
.RB [ \- P | \- \- partial ]
2016-06-24 15:51:20 +03:00
.RB [ \- \- reportformat
.RB { basic | json }]
2002-01-04 23:35:19 +03:00
.RB [ \- v | \- \- verbose ]
.RI [ VolumeGroupName ...]
.SH DESCRIPTION
2012-04-11 16:42:10 +04:00
vgcfgbackup allows you to backup the metadata of your volume groups.
If you don't name any volume groups on the command line, all of them
2004-06-19 22:55:29 +04:00
will be backed up.
.sp
In a default installation, each volume group gets backed up into a separate
2016-03-03 01:51:59 +03:00
file bearing the name of the volume group in the directory
\fI #DEFAULT_BACKUP_DIR#\fP .
2014-06-11 13:06:30 +04:00
You can write the backup to an alternative file using \fB \- f\fP . In this case
2004-06-19 22:55:29 +04:00
if you are backing up more than one volume group the filename is
treated as a template, and %s gets replaced by the volume group name.
.sp
NB. This DOESN'T backup user/system data in logical
2016-03-03 01:51:59 +03:00
volume(s)! Backup \fI #DEFAULT_SYS_DIR#\fP regularly too.
2002-01-04 23:35:19 +03:00
.SH OPTIONS
2012-04-11 16:42:10 +04:00
See \fB lvm\fP (8) for common options.
2002-01-04 23:35:19 +03:00
.SH SEE ALSO
.BR lvm (8),
2004-06-19 22:55:29 +04:00
.BR vgcfgrestore (8)