Bareos and Rear not recovering

[hi-flyer]

I used version 17.2 of Rear (from git) to create a usb backup using bareos. the configuration parameters in local.conf were

OUTPUT=USB
USB_DEVICE=/dev/sdb1
BACKUP=BAREOS
BAREOS_CLIENT=zeus-fd

this created a USB with bootable Rear recovery.
I booted a second dell computer with this usb, after reassigning eth0 (which was not connected in any case) and wlan0 (which is my access to the bareos server), it proceed to a line where if I hit a cr
it asked me for ZEUS login:
I have tried both the user name and root both of which state that they have created the disk layout. then it says is is connecting to the Director (which seems good to me)
Then is says "waiting for job to start" Which it never does anything else.

The real Zeus is on line when I am doing the above restore and I admit that the Bareos backup is only my local user files but it seems that it should actually run the restore from bareos but I do not expect that the operating system will be there as bareos backup is not set to provide that at this time.

So why does the job not start - any suggestions.

PS, your patch on #624 did fix my problem of not having a bootable usb.

[gdha]

@sebastianlederer Hi Sebastian - are you able to have a look at this issue and respond to it?

[sebastianlederer]

To help debugging, you can try manual recovery mode. Include the following in your rear configuration:

BAREOS_RECOVERY_MODE=manual

Then when booting the rear image and starting the recovery command, you will get a bconsole prompt. From there you can start a bareos restore job. Maybe then you can see more easily what is wrong.

You said that the original machine is still running, maybe the director is trying to connect with this machine instead of the new one?

[hi-flyer]

It turns out there are 3 issues. 1&2) the network dhclients are not establishing the IP connections. Because I am on a different machine, it detects that the mac addresses are different and asks me to select for a new idenity for ETH0 and WLAN0 which I did. It attempts to establish dhclient connections but fails for both. When I run ifconfig only local and wlan0 show up but no network IP connections. If I run dhclient -v wlan0 after many attempts it fails. If I run dhclient -v eth2 (and hook up the hardwire), then it gets a client connection. Normally I run these machines only on wlan. these are the first 2 issues. the last issue is with bareos. 3) If I run bconsole, I can start the backup. If I try to run rear recover, it gets to the point where it has selected the files and tries to select the bareos recover definition. I have 9 definitions and it tries something 3 times but then hangs. It will not let me enter the number 9 which is the correct one and not does it seem to do anything else.

As indicated above I can make it work but it is definitely not automatic in my test case.

[gdha]

@hi-flyer Different machine - could it be that the wlan drivers were not loaded and therefore no IP address could be attached? Rear does not always load automatically drivers if the HW changed. Certainly when doing cloning on different HW this might happen. Using dmesg might help to identify what was and what was not loaded...
We are open for improvements (as always)...

[schlomo]

Are you sure that all the WIFI tools are included in the Rescue image? I don't remember seeing WIFI support in ReaR... Consequently I would be surprised if WIFI would work just like this.

[hi-flyer]

I have tried to drop txt messages for dmesg, dhclient, ifconfig on the site to give info as to what am seeing but the system is saying it cannot process any of those files.

[hi-flyer]

as I am not available for next 3 weeks, I will close this issue as I have a work around. thanks

[schlomo]

@hi-flyer maybe it would help if you could open separate issues for your 3 problems?