Veeam Linux Recovery Media

[oli4]

Hello

I'm struggling with the Veeam Recovery Media. I have downloaded the version veeam-recovery-media-4.0.1.2365_x86_64.iso and tried to boot my server (Huawei with standard INTEL NIC's).
It boot from the media but after a while it fails and the screen stays black.

Then I modified the media with the efi switch and booted again, now it works but when I try to configure the network adapters the list is empty. I then modified the media and also added the
nic drivers (added the .ko and .ko.xz version), but still no success.

Is there anything else I can try?

Regards
oli4

[PTide]

Hi,

Did you add drivers as files using --copy <additional_path>, or you just patched the recovery?

If you just import drivers into the recovery media then the drivers has to be:

1. compiled for the same kernel version as recovery media kernel
2. loaded once the recovery media is booted (using 'modprobe')

Without that drivers won't work properly.

If you patch the recovery media, then VAL will inject all drivers into the media and patch the kernel. That should be enough for the hardware to work:

Code: Select all

veeamconfig patchiso --efi --input <input_path> --output <output_path>

Another option would be to take any LiveCD of your choice that is guaranteed to work with your hardware, install Veeam Agent inside it, and then start recovery UI from there. More details here

Thank you

[oli4]

Hello

Thanks for your answer. I tried now with an older ISO from Veeam: veeam-recovery-media-3.0.1.iso

With that it recognises the nics but when I try to restore it gives me error:

linux agent version 4 is not supported maximum of support is 3

Is this because the recovery media is version 3 and not version 4?


Regards
oli4

[PTide]

Right. You can restore v3 backups using v4 ISO, but not the other way around.

Have you tried any of the steps that I proposed (liveISO or patching the ISO)?

Thanks!

[Meisterzunge]

Hi,

I have exactly the same problem.
I'm wondering why veeam 3.x is able get my devices (nics and disks) but v4.x not!?
It would be great to use my rescue medium v4.x like I did with veeam v3.x - just as designed. Don't want to use a workarounds.

What I have done so far:
I used a patched iso with no additional paths.

Thanks,
Marco

[Meisterzunge]

When booting, the following output is visible for a split second:

Code: Select all

cryptd loading...
ip6_tables loading...
ip_tables loading...
nf_conntrack loading...
[Warn] Setting up network: network-up.sh lo eth0
Warning:
Unable to drop input artable: (modprobe: ERROR: could not insert ’arp_tables’: Exec format error
arptables v0.0.3.4: can’t initialize arptables table ‘filter’: arptables who? (do you need to insmod?)
Perhaps arptables or your kernel needs to be upgraded.].
Unable to drop output artable: [modprobe: ERROR: could not insert ’arp_tables’:
Exec format error
arptables v0.0.3.4: can’t initialize arptables table ‘filter’: arptables who? (do you need to insmod?)
Perhaps arptables or your kernel needs to be upgraded.].
modprobe: ERROR: could not insert ’arp_tables’: Exec format error
arptables v0.0.3.4: can’t initialize arptables table ‘filter’: arptables who? (do you need to insmod?)
Perhaps arptables or your kernel needs to be upgraded.
Unable to set up interface [eth0]: Cip: SIOCGIFFLAGS: No such device].
Unable to obtain settings by DHCP for interface eth0: Cudhcpc: option -h NAME is
deprecated, use -x hostname: NAME
udhcpc: SIOCGIFINDEX: No such device].

I'm not a linux expert, but it seams like some drivers could not get loaded!?

[PTide]

Hi @Meisterzunge,

What is the distro (and kernel version) where you patched you ISO at? Does the distro fail to see disks as well?

Thanks!

[Meisterzunge]

I patched the ISO on a CentOS distro. Kernel version is 3.10.0-1127.18.2.el7.x86_64.
With a booted system I'm able to see everything - no problems there.

Thanks.

[PTide]

@Meisterzunge,

Sorry, I meant to ask "Does the patched ISO fail to see disks too?"

[Meisterzunge]

Yes of course:
the booted ISO can't see anything.
And the log above (See my post Oct 28, 2020 9:37 pm) shows the output while booting the patched v4.x ISO.

And as mentioned:
The patched v3.x ISO had no problems....

[PTide]

Hi,

I contacted our support team and they said that they have already seen similar issues. So the best option for now would be to open a case with our support team and let them find something.
Via forums we don't resolve complex technical issues, so please open the case and post your case ID.

Thanks!

[Meisterzunge]

Hi PRide,

I've opened a support case #04487245.

Thank you,
Marco

[arossolimo]

I have a case open about this (Case #04362290), but I want to let everybody know that customized recovery ISO on RHEL based distros is useless. When we boot from customized recovery iso we can't see any NIC's and not able to perform a recovery.

Note from Veeam support:
-------------
I'm finding that Debian based distros are fine (ie. Debian/Ubuntu). Seems to be an issue with RHEL based distros.
-------------

Workaround that worked for me that I received from Veeam support:
-------------
I have another update, I do believe we have a workaround for now, can you do the following for me:
Run these commands
# mkdir -p /test/bin
# mkdir -p /test/lib/x86_64-linux-gnu
# cp /bin/kmod /test/bin/
# cp /lib64/libcrypto.so.10 /test/lib/x86_64-linux-gnu/
# veeamconfig patchiso --input veeam-recovery-media-4.0.0.iso --output veeam-recovery-media-4.0.0_patched.iso --efi --copy /test


Then try the new ISO and see if that works.
-------------

Another note from Veeam support:
-------------
Okay, I have an update, the issue is with the current patching, it will result in a huge intramfs and results in the ISO either not booting or modules failing to be copied properly.
We are looking to resolve the issue in the future, but we do not have any ETA for future releases.
-------------

[Meisterzunge]

I wanted to play with the "veeamconfig ... --copy /test" approach.
But I dont have any "/bin/kmod" directory...

---

I was thinking about SE-Linux issues. But I have disabled SE-Linux! This cannot be the cause of my problem - just for your info.

[PTide]

@arossolimo,

Thank you for the update. Indeed, this seems to be a known issue which has to be fixed in one of the next updates. I heard that the support engineer provided a workaround, did that work for you?

@Meisterzunge

If support engineer hasn't answered you anything meaningful yet or provided a workaround, then I advise you to escalate the case.

Thank you!

[Meisterzunge]

My support case has already been closed
But it sounds good if a fix is coming up with an update!

[Meisterzunge]

Hi @PTide,
do you have some news for us here? Thank you.

[Meisterzunge]

So long without a feedback

[PTide]

@Meisterzunge,

I apologize, my bad - somehow I've overlooked your message (thrice...).

We've recently (3 days ago) released a new version of Agent, so the Recovery ISO has been updated too. On the repository you can find two v5 ISO versions - the liveCD-based one (kernel 4.19) and the legacy (older kernel). Please try the 4.19 first as it should work with the majority of hardware. If it does not work, then try the other one. If neither works, then you need to open another case and mention and post your case ID in this thread again so that I can make sure that there is an item opened in out internal systems for that particular issue.

Thank you for your patience

[Meisterzunge]

Hi PTide,

I have patched and used the live cd image and it worked: My actual hardware configuration could be used when booting into recovery mode.
Thank you.

But now I have another problem that prevents me from recovering a backup
See this topic: veeam-agents-for-linux-mac-aix-solaris- ... 72505.html.

I am kind of frustrated because for now a half year I am unable to recover backups! This is operating a server with defacto no backups

[PTide]

But now I have another problem that prevents me from recovering a backup
See this topic: veeam-agents-for-linux-mac-aix-solaris- ... 72505.html.

I cannot comment on the issue right now, let's see what the support engineer will find.
Should you feel that they could do better please feel free to use "talk to a manager button".

Thanks!