#375 Issue closed: Non-destructively recreate filesystem during recover?¶
andyeff opened issue at 2014-03-06 15:15:¶
Hi there,
I have a usage case for Relax and Recover that might be a little out of the ordinary, but I wondered if it's supported?
I have a virtual RHEL 6 server with 6 disks. The first disk contains the OS + boot partitions, the second and third disks contain data that is backed up by a Symantec Netbackup system.
However the fourth, fifth and six drives are not backed up. They are LVM disks, used to provide a single large volume group + logical volume.
I am looking at configuring local.conf with:
OUTPUT=ISO
BACKUP=NBU
BACKUP_URL=file:///root/backup
And then saving the resulting ISO out to a network share afterwards, and then for recovery, mounting that ISO in vmware and booting from it.
If I do this, and run the restore, is there a way to recreate the LVM layout for disks 4-6 without trashing them, so that they will be accessible after the OS is restored with all their existing data on them? My impression is that during the restore, the layouts are recreated and 'new' physical volume / volume groups are applied to the disks which would effectively 'destroy' existing data on the disks.
Apologies for not having quite the right technical terminology to hand, I'm not 100% familiar with LVM and how disks are labelled / identified properly yet.
andyeff commented at 2014-03-06 17:05:¶
I think I might have answered my own question!
I've been looking through the documentation, and it seems having an
EXCLUDE_MOUNTPOINTS section in the local.conf will generate me a
bootable ISO with the disklayout file preconfigured to exclude doing
anything to the filesystems associated with that mountpoint.
gdha commented at 2014-03-07 07:35:¶
Also, do not forget the EXCLUDE_VG variable if those mount points are
mounted via their own VGs.
On Thu, Mar 6, 2014 at 7:11 PM, Andy Eff notifications@github.com wrote:
Closed #375 https://github.com/rear/rear/issues/375.
Reply to this email directly or view it on GitHubhttps://github.com/rear/rear/issues/375
.
[Export of Github issue for rear/rear.]