Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

combining volumes #2413

Closed
Hardcore-fs opened this issue May 30, 2020 · 3 comments
Closed

combining volumes #2413

Hardcore-fs opened this issue May 30, 2020 · 3 comments

Comments

@Hardcore-fs
Copy link

Sometimes in case of emergency. we have to do a fast restore to a different system, with less drives

if Original system has:
/dev/sda1
/dev/sdb1
both of say 16 GB

is there an easy way on restore to bring sdb1 into say /dev/sda3
if the new system drive is 146gb

@gozora
Copy link
Member

gozora commented May 30, 2020

Hi @Hardcore-fs,

"Easy" is relative, because what is easy basically depends on personal skills ...
But in general, yes ReaR can move content from one partition to another during rear recover workflow.

V.

@Hardcore-fs
Copy link
Author

yep i did it manually....
but it took two attempts to find the right menu to get out and the right stage in the process.
I would be real nice if there was a 'squash' function,
In the end I think i only had to change a few numbers & change sdb1-> sda3

@jsmeix
Copy link
Member

jsmeix commented Jun 2, 2020

@Hardcore-fs
a side note FYI:

In general regarding system migration with ReaR see
#2339 (comment)
and follow the links therein in particular see
http://lists.relax-and-recover.org/pipermail/rear-users/2018-November/003626.html
and also follow the links therein.

Migrating an original system that was on /dev/sda1 and /dev/sdb1
both of 16 GB onto replacement hardware with a single /dev/sda3
that has 146 GB could be more or less straightforward by adapting
the matching entries in var/lib/rear/layout/disklayout.conf
as long as only filesystems on plain partitions are used.

But things get tricky when filesystems on higher level strorage objects
like LVM logical volumes are used because there is no automatism
in ReaR that adapts (size) vaules of higher level strorage objects
so you need to do all that manually.

What could help here - provided you know your replacement hardware
in advance - is to prepare a disklayout.conf in advance that fits the
replacement hardware and copy that into the ReaR recovery system
before you launch "rear recover".
You could automate the "copy that into the ReaR recovery system" part
by using RECOVERY_UPDATE_URL see its description in default.conf
and for a special case issue you may have a look at
#943 (comment)

@jsmeix jsmeix closed this as completed Jun 2, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants