Skip to content

On Dell machines with "biosdevname" there is no support for that in "rear recover" #951

@grendelson

Description

@grendelson

Relax-and-Recover (rear) Issue Template

Please fill in the following items before submitting a new issue:

  • rear version (/usr/sbin/rear -V): Relax-and-Recover 1.17.2 / Git
  • OS version (cat /etc/rear/os.conf or lsb_release -a):
    OS_VENDOR=OracleServer
    OS_VERSION=6
  • rear configuration files (cat /etc/rear/site.conf or cat /etc/rear/local.conf):
  OUTPUT=ISO
  OUTPUT_URL=nfs:///home/nfsexport
  BACKUP=NETFS
  BACKUP_URL=nfs:///home/nfsexport
  TMPDIR=/data/backup/tmp
  BACKUP_PROG_EXCLUDE=( '/tmp/_' '/dev/shm/_' '/data/backup/_' $VAR_DIR/output/\_ )
  • Brief description of the issue
    When a rescue disk is used to start a restore OR a clone, the devices in our servers ( Dell R720's) under RHEL 6 ( Oracle 6) were captured as card slot and card port - so a card in slot 4 on the MB and port 2 will appear as ifcfg-p4p2. This p4p2 is not present or created when the Live CD is booted. the underlying eth devices are found but the backed up OS network devices nor any advanced settings ( bond0, vlans etc) are working since the expected devices aren't "present". During the backed up OS boot process dmesg shows that "eth3 was renamed p4p3" for example - this is NOT present in the live CD OS.
    I've tried both NETFS and local backups, restores from NBU and from local full backups - the issue appears to be the ability to load and rename the ethernet devices to match what is expected when the network is brought up.
  • Work-around, if any
  • I've been able to use 'ip' and the tools in the Live Env to bring up the ethernet devices ( ethtool to find the active devices, enslave the devices to my bond and then add the vlan if bringing up a Clone with a different IP address). Manually running 'ifenslave' to capture ethernet devices or manually adding ip addresses and default gateways has worked so far and once a network is present the restore continues as expected and upon reboot the original OS works as expected.

Metadata

Metadata

Assignees

Labels

enhancementAdaptions and new featuresneeds sponsorshipThis issue will not get solved on a voluntary base by ReaR upstream.special hardware or VMThe issue depends on non common (virtual) hardware.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions