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
ReaR 2.00 not working for SLES 12 SP3 on PowerVM LPAR with MPIO SAN device #1973
Comments
See On a first glance Backup archive size is 40K ... does not look promising... |
@schabrolles |
@gsasidharan Try out if a more current version works better for you, cf. See I would also recommend to try out our current Basically "git clone" our current ReaR upstream GitHub master code # git clone https://github.com/rear/rear.git # mv rear rear.github.master # cd rear.github.master # vi etc/rear/local.conf # usr/sbin/rear -D mkbackup Note the relative paths "etc/rear/" and "usr/sbin/". I recommend to try out our current ReaR upstream GitHub master code If the issue also happens with current ReaR upstream GitHub master code If it works with the current ReaR 2.4 or our current ReaR upstream GitHub For SUSE Linux Enterprise there should be official "rear23a" RPM packages |
Thanks for your quick response...
already tried version 2.4 and got failures for SUSE.
RHEL worked perfectly fine.
will retry with below steps and confirm the status.
thanksSasi.G
Sent from my Samsung Galaxy smartphone.
|
When things fail for SLES but work for RHEL my blind guess is When you use SLES with its default btrfs structure |
@jsmeix looking at those examples I wonder why we don't include the snapper and other tools by default? Wouldn't that make ReaR work on all SLES versions without "special" configuration? |
@schlomo Of course in theory with unreasonable effort it might be even possible I think in practice it is more reasonable to leave it as it is now SLE12-SP2-btrfs-example.conf also works on SLE12-SP3 and SLE12-SP4 |
AFAIKT the only really relevant parts of that example configuration are the As it took me 3 times going over that example before I noticed those relevant variables I can imagine that our users also will struggle with that. Therefore I suggest to merge the Wrong? Why? I'd like to know specifically. @gsasidharan sorry for highjacking your issue with this general discussion. |
Team..
pls share if you have the SLES12-SP3-PPC64.CONF file...
able to use rear 2.4 now and beleive the conf file is my issue now.
i use the default partitioning for filesystems .
my os version is SLES 12-SP3 for Power platform.
ThanksSasi.G
Sent from my Samsung Galaxy smartphone.
|
@gsasidharan There is no SLES12-SP3-PPC64.CONF file in our ReaR upstream files, # git clone https://github.com/rear/rear.git # mv rear rear.github.master # cd /root/rear.github.master # find . | grep -i SLE ./usr/share/rear/conf/examples/SLE11-SLE12-SAP-HANA-UEFI-example.conf ./usr/share/rear/conf/examples/SLE12-SP2-btrfs-example.conf ./usr/share/rear/conf/examples/SLE11-ext3-example.conf ./usr/share/rear/conf/examples/SLE12-btrfs-example.conf ./usr/share/rear/conf/examples/SLE12-SP1-btrfs-example.conf but I do not run SLES 12-SP3 on POWER platform. |
Hi John,
for Sap Hana purposes we are using SLES V12SP3 in power platform.
this is not available below samples given.
Will try below suitable one and revert back.
thanksSasi.G
Sent from my Samsung Galaxy smartphone.
|
@gsasidharan |
I installed rear 2.4 on my Power E880, running SLES 12.3, and it allmost restored flawless. During recover I had to edit /var/lib/rear/layout/disklayout.conf, exchanging all 'p1' with '-part1' and so on:
here's my rear dump:
|
@hejharald
reminds me of things like For a detailed analysis we need
See also Perhaps in your case there is also something unexpected |
Stale issue message |
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"): [root@rheltest ~]# rear -V
Relax-and-Recover 2.00 / Git
OS version ("cat /etc/rear/os.conf" or "lsb_release -a" or "cat /etc/os-release"): SUSE 12 SP3
ReaR configuration files ("cat /etc/rear/site.conf" and/or "cat /etc/rear/local.conf"):
Hardware (PC or PowerNV BareMetal or ARM) or virtual machine (KVM guest or PoverVM LPAR): PowerVM LPAR
System architecture (x86 compatible or PPC64/PPC64LE or what exact ARM device):ppc64
Firmware (BIOS or UEFI or Open Firmware) and bootloader (GRUB or ELILO or Petitboot):
Storage (lokal disk or SSD) and/or SAN (FC or iSCSI or FCoE) and/or multipath (DM or NVMe):MPIO SAN device
Description of the issue (ideally so that others can reproduce it):
when rear recovery is initiated exiting either with NFS issue or GRUB issues..
No code has been generated to recreate swap:/dev/mapper/20017380035360016-part2 (swap).
To recreate it manually add code to /var/lib/rear/layout/diskrestore.sh or abort.
Manually add code that recreates swap:/dev/mapper/20017380035360016-part2 (swap)
Workaround, if any: NO,failed multiple times
Attachments, as applicable ("rear -D mkrescue/mkbackup/recover" debug log files):
The text was updated successfully, but these errors were encountered: