New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SUSE 12 (ppc64le) Patch level 4 OS Backup & restore through rear utility on IBM Power system #2294
Comments
@Ajju1 In your ...hmciecchdb02s-target.log
but I cannot imagine what the actual root cause behind is. Could it be that you did something in the running ReaR recovery system For example after a previous (possibly failed) run of "rear recover" In your ...hmciecchdb02s-target.log I see lots of lines So when you use SLES12 with its default btrfs structure
Provided your etc/rear/local.conf is right for your SLES12 system Furthermore (also see that section) we would like to get Additionally to get an easier overview about your storage layout
|
Hi Johannes Please find the attached |
Follow what I had written in When you use SLES12 with its default btrfs structure Provided your etc/rear/local.conf is right for your SLES12 system Furthermore ... we would like to get Additionally to get an easier overview about your storage layout
(that command as is - not split up into pieces). |
Hi Johannes Please find the attached logs |
@Ajju1
which is still insufficient for SLE12 with btrfs. For SLE12 SP2 and later with btrfs start with the template in If you had initially installed your system as SLE12 SP1 with btrfs If you had initially installed your system as SLE12 GA (SP0) with btrfs For the reason behind why different SLE12 service packs need Regarding
the reason could be that you use perhaps an already used disk
For some more details and background information see |
I know I had seen such an parted/partprobe |
Because "no news is good news" I assume this issue can be closed. |
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"):
Relax-and-Recover 2.4 / Git
OS version ("cat /etc/rear/os.conf" or "lsb_release -a" or "cat /etc/os-release"):
SUSE Linux Enterprise Server 12 (ppc64le)
cat /etc/rear/local.conf
Hardware (PC or PowerNV BareMetal or ARM) or virtual machine (KVM guest or PoverVM LPAR):
PowerVM Lpar on IBM Power 9 Server
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):
bootloader: Grub
Storage (local disk or SSD) and/or SAN (FC or iSCSI or FCoE) and/or multipath (DM or NVMe):
San bootable and multipathing
Description of the issue (ideally so that others can reproduce it):
We are taking only system/rootvg backup from source and trying to restore on another lpar for restoration testing. During the restoration we are changing IP of the target system after booting from ISO file created by rear backup of source through HMC and then map the disk only for system vg.
Since, we have to just restore the system vg/rootvg only, so we have assigned the same size disk to destination VG and rest disks required for datavg are not assigned.
To achieve this we have done some configuration in the source system /etc/rear/local.conf file for excluding the mapping of disk other than system VG.
While restoring the disk mapping is getting failed and thus results in restoration failure.
Few more things regarding the environment.
The systems are same hardware but different lpar on IBM Power server
Nfs is used for taking backup and restoration of data
Booting lpar in SMS mode through iso file created by the rear backup of source system and then assigning different IP
After assigning new IP, we are using rear -d D restore command
PFA are files of source configuration, rear local.conf file and rear backup log; along with the destination steps followed and logs.
Workaround, if any:
Attachments, as applicable ("rear -D mkrescue/mkbackup/recover" debug log files):
rear backup.zip
To paste verbatim text like command output or file content,
include it between a leading and a closing line of three backticks like
The text was updated successfully, but these errors were encountered: