#835 Issue closed: Migrating with rear¶

Labels: support / question

John-Leone opened issue at 2016-05-13 00:28:¶

[root@xjlappm1d init.d]# rear -V
Relax-and-Recover 1.17.1 / Git

[root@xjlappm1d init.d]# cat /etc/redhat-release
Red Hat Enterprise Linux Server release 6.7 (Santiago)

We're trying to use rear as a migration tool. The network files on the recovery image need to be modified to work on the new subnet. Is there a command line tool or process that lets you change the network files to support the new network?

I was searching the documentation but could not find anything.

Thanks,
John

gdha commented at 2016-05-13 05:58:¶

See http://relax-and-recover.org/documentation/faq IP migration section.

On Fri, May 13, 2016 at 2:28 AM, John-Leone notifications@github.com
wrote:

[root@xjlappm1d init.d]# rear -V
Relax-and-Recover 1.17.1 / Git

[root@xjlappm1d init.d]# cat /etc/redhat-release
Red Hat Enterprise Linux Server release 6.7 (Santiago)

We're trying to use rear as a migration tool. The network files on the
recovery image need to be modified to work on the new subnet. Is there a
command line tool or process that lets you change the network files to
support the new network?

I was searching the documentation but could not find anything.

Thanks,
John

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/rear/rear/issues/835

John-Leone commented at 2016-05-13 19:17:¶

Thank you that works!
Does rear work with bonded networks?

gdha commented at 2016-06-13 14:40:¶

@John-Leone yes it understands it to recreate these on a new system, however, when booted from the rescue image there is no guarantee it works (it might just be one interface).

---

[Export of Github issue for rear/rear.]