[rear-users] Help with recover on IBM cloud bare metal servers

[Cary Lewis]

Thank you very much for the information.

I have a couple of follow up questions:

1. The system I am dealing with has 4 nic cards, and two bonded networks,
bond0 and bond1. bond0 is for the private network and is assigned a static
IP, bond1 is for the public network and is also assigned a static ip.

When the recovery ISO boots and starts to run, it does prompt for replacing
the old MAC addresses with new ones, but it does not prompt for replacing
the IP addresses.

Is there a way to do that?

2. On the production system, the /etc/sysconfig/network-scripts folder
contains all of the networking scripts - where are those in the recovery
system?

Should I be editing those, to update the IP addresses?

If I do, how do I restart the network?

On Mon, Nov 4, 2019 at 11:19 AM Johannes Meixner <jsmeix at suse.de> wrote:

>
> Hello,
>
> On Nov 4 09:09 Cary Lewis wrote (excerpt):
> > I am having trouble getting the networking to work
> > when I boot from the rear ISO.
> >
> > I am running centos 7 on the supermicro hardware,
> > and each machine has four NICs configured into
> > two bonded interfaces, one public and one private.
> >
> > I have tried various combinations of replacing the
> > different NICs with ones that the rear software presents,
> > but I can not get the network working.
> >
> > Can someone please provide some instructions on how to use
> > the recover ISO on the ibm cloud bare metal servers.
>
> I have neither your hardware nor IBM things nor do I use CentOS
> so that if your issue is specific on your hardware or software
> there is nothing what I could do to directly help you,
> but perhaps others could able to help you directly.
>
> When you do not yet use our latest ReaR upstream
> GitHub master code, have a look at the section
> "Testing current ReaR upstream GitHub master code" at
> https://en.opensuse.org/SDB:Disaster_Recovery
>
> In general we at ReaR upstream prefer when issues are
> reported to us as GitHub issues via the [New issue] button at
> https://github.com/rear/rear/issues
>
> This leads you automatically to our issue template at
>
> https://raw.githubusercontent.com/rear/rear/master/.github/ISSUE_TEMPLATE.md
> where we list what info we usually like to get.
>
> Usually we need debug logs i.e. made with "rear -d -D mkbackup"
> and/or "rear -d -D recover" plus your disklayout.conf file and
> things like that, see "Debugging issues with Relax-and-Recover" at
> https://en.opensuse.org/SDB:Disaster_Recovery
>
> The main advantage of GitHub issues over plain e-mails
> is the much better GitHub user interface that helps a lot
> when several people need to work together on an issue.
>
> Regarding how to debug issues during startup of the
> ReaR recovery system:
>
> When you boot the ReaR recovery system on "usual hardware"
> you should get the recovery system bootloader menue where
> you can add the kernel command line parameter ' debug'.
>
> This way the recovery system startup scripts are run
> one by one (you need to press Enter to run each one)
> with the bash 'set -x' option set so that you get the
> commands of each script printed on the terminal/console.
>
> This can help to find out in which script things go wrong.
>
> The recovery system setup scripts are in etc/scripts/system-setup.d
>
> The main networking setup script is
> /etc/scripts/system-setup.d/60-network-devices.sh
> that is generated during "rear mkrescue/mkbackup" by
>
> https://github.com/rear/rear/blob/master/usr/share/rear/rescue/GNU/Linux/310_network_devices.sh
>
> See the usr/share/rear/rescue/GNU/Linux/310_network_devices.sh script
> for details how networking setup happens in the recovery system.
>
> Furthermore there is NETWORKING_PREPARATION_COMMANDS that could help
> to set up special networking in the ReaR recovery system, see
>
> https://github.com/rear/rear/blob/master/usr/share/rear/conf/default.conf#L2521
>
> Finally you can use KEEP_BUILD_DIR="yes" see
>
> https://github.com/rear/rear/blob/master/usr/share/rear/conf/default.conf#L128
> to inspect the contents of the ReaR recovery system
> on your original system in /tmp/rear.XXXXXXXXXXXXXXX/rootfs
> after is was made there by "rear -d -D mkrescue/mkbackup"
>
>
> Kind Regards
> Johannes Meixner
> --
> SUSE Software Solutions Germany GmbH
> (HRB 36809, AG Nuernberg) GF: Felix Imendoerffer
>
> _______________________________________________
> rear-users mailing list
> rear-users at lists.relax-and-recover.org
> http://lists.relax-and-recover.org/mailman/listinfo/rear-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.relax-and-recover.org/pipermail/rear-users/attachments/20191105/9abbc74e/attachment.html>