You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
OS version ("cat /etc/rear/os.conf" or "lsb_release -a" or "cat /etc/os-release"):
esashxigo171:/dev # cat /etc/rear/os.conf
OS_VENDOR=SUSE_LINUX
OS_VERSION=12
Hardware (PC or PowerNV BareMetal or ARM) or virtual machine (KVM guest or PoverVM LPAR):
Power Lpar
System architecture (x86 compatible or PPC64/PPC64LE or what exact ARM device):
PPC64LE
Firmware (BIOS or UEFI or Open Firmware) and bootloader (GRUB or ELILO or Petitboot):
GRUB
Storage (lokal disk or SSD) and/or SAN (FC or iSCSI or FCoE) and/or multipath (DM or NVMe):
SAN FC multipath
Description of the issue (ideally so that others can reproduce it):
Built a new SLES 12 SP3 SAP system and created a rear backup. Trying to clone to another lpar fails.
Your eniesdbs101_RearRecoverDebug.txt excerpts above show
that you use the old mount_url before #1894
so that you need to update your ReaR to one where that issue is fixed.
If it is not fixed with a current ReaR you should of course reopen this issue.
Relax-and-Recover (ReaR) Issue Template
Fill in the following items before submitting a new issue
(quick response is not guaranteed with free support):
ReaR version ("/usr/sbin/rear -V"):
esashxigo171:/dev # /usr/sbin/rear -V
Relax-and-Recover 2.4 / Git
OS version ("cat /etc/rear/os.conf" or "lsb_release -a" or "cat /etc/os-release"):
esashxigo171:/dev # cat /etc/rear/os.conf
OS_VENDOR=SUSE_LINUX
OS_VERSION=12
ReaR configuration files ("cat /etc/rear/site.conf" and/or "cat /etc/rear/local.conf"):
esashxigo171:/dev # cat /etc/rear/local.conf
AUTOEXCLUDE_MULTIPATH=n
BOOT_OVER_SAN=y
REAR_INITRD_COMPRESSION=lzma
OUTPUT=ISO
ISO_MAX_SIZE=4000
BACKUP=NETFS
BACKUP_URL=iso:///iso_fs/REAR_BACKUP
ISO_DIR=/iso_fs/REAR_ISO
TMPDIR=/iso_fs/REAR_TEMP
OUTPUT_URL=null
BOOT_FROM_SAN=y
EXCLUDE_MOUNTPOINTS=( /iso_fs )
EXCLUDE_COMPONENTS=( /dev/mapper/36005076400810051380000000000006d /dev/mapper/36005076400810051380000000000007b /dev/mapper/36005076400810051380000000000007c /dev/mapper/36005076400810051380000000000007d /dev/mapper/36005076400810051380000000000007e /dev/mapper/36005076400810051380000000000007f /dev/mapper/360050764008100513800000000000080 /dev/mapper/360050764008100513800000000000088 )
Hardware (PC or PowerNV BareMetal or ARM) or virtual machine (KVM guest or PoverVM LPAR):
Power Lpar
System architecture (x86 compatible or PPC64/PPC64LE or what exact ARM device):
PPC64LE
Firmware (BIOS or UEFI or Open Firmware) and bootloader (GRUB or ELILO or Petitboot):
GRUB
Storage (lokal disk or SSD) and/or SAN (FC or iSCSI or FCoE) and/or multipath (DM or NVMe):
SAN FC multipath
Description of the issue (ideally so that others can reproduce it):
Built a new SLES 12 SP3 SAP system and created a rear backup. Trying to clone to another lpar fails.
Workaround, if any:
None
Attachments, as applicable ("rear -D mkrescue/mkbackup/recover" debug log files):
eniesdbs101_RearRecoverDebug.txt
The text was updated successfully, but these errors were encountered: