Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Clovis
    @Tristan3860_twitter
    Please, any idea. I would need to restore almost automatically
    Anthony
    @Anth0nyME
    hello
    Anthony
    @Anth0nyME
    i can't find answer or sollution for my problem. please help me, if possible... i have a strange thing: powerfull hardware (2 x xeon silver), many RAM and 1Gb network link, but ReaR make backup too slowly. No more than 5000KiB/sec. "top" show me what gzip eat 98% of CPU but mpstat show absolutely different: ALL cores (20 in summ) stay at 96-99% idle state... How can i speedup backup process? Thank you for advice.
    Laurent G
    @xenlo
    I assume that the gzip is mono threat, so it take 100% of one core and the rest of your cores stay in idle
    Anthony
    @Anth0nyME
    I make backup to NFS share. If i simple transfer any data at this shared NFS folder, speed dramatically increased.
    @xenlo Thank you. Can you advice how can i change this situation...?
    It's possible to change gzip to another app to make process more faster..?
    Laurent G
    @xenlo
    few clues here:
    «an implementation of gzip that is multithreaded, pigz»
    «use GNU's xargs to launch as many processes as you have cores»
    Anthony
    @Anth0nyME
    thank you mate =)
    Laurent G
    @xenlo
    you're welcome
    PetersPlace
    @PetersPlace
    Hello anyone here ?
    Laurent G
    @xenlo
    @PetersPlace, Hi someone there!
    msatheesh84
    @msatheesh84
    hi
    anyone there to help me out for REAR Backup recovery
    Backup completed for SUSE Enterprise OS with NFS, but failed to restore stating that Start system layout restoration.
    Skipping /dev/mapper/360050764008282e62000000000000166 (multipath) as it has already been created.
    Skipping /dev/mapper/360050764008282e62000000000000166-part1 (part) as it has already been created.
    Skipping /dev/mapper/360050764008282e62000000000000166-part2 (part) as it has already been created.
    Skipping pv:/dev/mapper/360050764008282e62000000000000166-part2 (lvmdev) as it has already been created.
    Skipping /dev/system (lvmgrp) as it has already been created.
    Skipping /dev/mapper/system-root (lvmvol) as it has already been created.
    Skipping /dev/mapper/system-swap (lvmvol) as it has already been created.
    Creating filesystem of type btrfs with mount point / on /dev/mapper/system-root.
    Mounting filesystem /
    UserInput -I LAYOUT_CODE_RUN needed in /usr/share/rear/layout/recreate/default/200_run_layout_code.sh line 127
    The disk layout recreation script failed
    1) Rerun disk recreation script (/var/lib/rear/layout/diskrestore.sh)
    2) View 'rear recover' log file (/var/log/rear/rear-dchsbdev.log)
    3) Edit disk recreation script (/var/lib/rear/layout/diskrestore.sh)
    4) View original disk space usage (/var/lib/rear/layout/config/df.txt)
    5) Use Relax-and-Recover shell and return back to here
    6) Abort 'rear recover'
    (default '1' timeout 300 seconds)
    celikozl
    @celikozl
    hello Could someone help me with these error logs?
    ERROR: Could not find file 'mbr.bin'. Syslinux version 3.08 or newer is required, 4.x prefered!
    ===== Stack trace =====
    Trace 0: usr/sbin/rear:541 main
    Trace 1: /root/rear/usr/share/rear/lib/mkrescue-workflow.sh:12 WORKFLOW_mkrescue
    Trace 2: /root/rear/usr/share/rear/lib/framework-functions.sh:116 SourceStage
    Trace 3: /root/rear/usr/share/rear/lib/framework-functions.sh:56 Source
    Trace 4: /root/rear/usr/share/rear/prep/USB/Linux-i386/340_find_mbr_bin.sh:22 source
    Trace 5: /root/rear/usr/share/rear/lib/_input-output-functions.sh:693 StopIfError
    === End stack trace ===
    2020-01-03 16:34:04.318704079 Exiting rear mkrescue (PID 638) and its descendant processes ...
    2020-01-03 16:34:07.394024221 rear,638 usr/sbin/rear -v mkrescue
    -rear,1349 usr/sbin/rear -v mkrescue-pstree,1350 -Aplau 638
    /root/rear/usr/share/rear/lib/_input-output-functions.sh: line 151: kill: (1373) - No such process
    2020-01-03 16:34:07.423860450 Running exit tasks
    this command gave the output I posted. sudo usr/sbin/rear -v mkrescue
    "sudo usr/sbin/rear -v mkrescue
    "
    daebenji
    @daebenji
    @celikozl which distro and which version of it are you running? what version is syslinux (in debian it may comes with the extlinux package)?
    Is someone of you in Chemnitz at Cheminitzer Linux Tage 2020 #CLT2020?
    Stefan
    @21Stefan21_twitter
    Hi, I am not entirely sure if this right place, but it seems that the repo gpg key at http://download.opensuse.org/repositories/Archiving:/Backup:/Rear/Debian_9.0 has been expired. (InRelease: The following signatures were invalid: EXPKEYSIG A39566C0A4AB7D54).
    Is this the right place or am i just wasting your time :) ?
    daebenji
    @daebenji
    Maybe you should open an issue at https://github.com/rear/rear/issues
    ChiefMedicalOfficer
    @ChiefMedicalOfficer
    Hi guys. Really new to Rear and I'm just wondering if it's possible to recover to a drive that is smaller than the partition that was backed up? I found some forum posts from a few years ago suggesting it wouldn't work. Thanks.
    John Borkowski
    @uzyx-john

    Hello all, I just discovered rear and have a quick question. I have done a quick look through the docs and dont see what I am looking for obviously, but it may be there once I learn more.

    I would like to be able to save backups to a local hard drive that is not part of the operating system. Is that possible? yes or no works then I will do my homework.

    kitatek
    @kitatek
    Well if you can mount it for rear, it should work. I usually do it on nfs, but I mount the nfs targets.
    @ChiefMedicalOfficer I think the recovery includes the partition table, so if you fully partitioned the disk, then it should require a disk size that is bigger or equal to the backup disk.
    kitatek
    @kitatek
    @uzyx-john @ChiefMedicalOfficer Please note that I used rear very seldom ( but it beautifully saved my arch when I used it :) ), so I just speak from memory, you definitely need to double-check .
    John Borkowski
    @uzyx-john
    Awesome, thanks guys... playing with it now. I will use SSHFS if need be, but local would be better.
    Mark Jones
    @kingpoop

    Hello Everyone, I installed rear on the following linux server:

    Distributor ID: Ubuntu
    Description: Ubuntu 14.04.5 LTS
    Release: 14.04
    Codename: trusty

    I DOWNLOADED THE BITS FROM THE FOLLOWING LOCATION:
    sudo wget http://download.opensuse.org/repositories/Archiving:/Backup:/Rear/xUbuntu_14.04/rear_2.2.orig.tar.gz

    UNTAR:
    sudo tar xzvf rear_2.2.orig.tar.gz

    LASTLY BUILT AND INSTALLED IT:
    sudo make install
    == Validating scripts and configuration ==
    find etc/ usr/share/rear/conf/ -name '.conf' | xargs -n 1 bash -n
    bash -n usr/sbin/rear
    find . -name '
    .sh' | xargs -n 1 bash -n
    find usr/share/rear -name '.sh' | grep -v -E '(lib|skel|conf)' | while read FILE ; do \
    num=$(echo ${FILE##
    /} | cut -c1-3); \
    if [[ "$num" = "000" || "$num" = "999" ]] ; then \
    echo "ERROR: script $FILE may not start with $num"; \
    exit 1; \
    else \
    if $( grep '[_[:alpha:]]' <<< $num >/dev/null 2>&1 ) ; then \
    echo "ERROR: script $FILE must start with 3 digits"; \
    exit 1; \
    fi; \
    fi; \
    done
    == Prepare manual ==
    make -C doc man
    make[1]: Entering directory /home/rear/rear-2.2/doc' make[1]: Nothing to be done forman'.
    make[1]: Leaving directory /home/rear/rear-2.2/doc' == Installing configuration == install -d -m0700 /etc/rear/ install -d -m0700 /etc/rear/cert/ [[ ! -e /etc/rear/local.conf ]] && \ install -Dp -m0600 etc/rear/local.conf /etc/rear/local.conf make: [install-config] Error 1 (ignored) [[ ! -e /etc/rear/os.conf && -e etc/rear/os.conf ]] && \ install -Dp -m0600 etc/rear/os.conf /etc/rear/os.conf make: [install-config] Error 1 (ignored) find /etc/rear/ -name '.gitignore' -exec rm -rf {} \; &>/dev/null == Installing binary == install -Dp -m0755 usr/sbin/rear /usr/sbin/rear sed -i -e 's,^CONFIG_DIR=.*,CONFIG_DIR="/etc/rear",' \ -e 's,^SHARE_DIR=.*,SHARE_DIR="/usr/share/rear",' \ -e 's,^VAR_DIR=.*,VAR_DIR="/var/lib/rear",' \ /usr/sbin/rear == Installing scripts == install -d -m0755 /usr/share/rear/ cp -a usr/share/rear/. /usr/share/rear/ find /usr/share/rear/ -name '.gitignore' -exec rm -rf {} \; &>/dev/null == Installing working directory == install -d -m0755 /var/lib/rear/ install -d -m0755 /var/log/rear/ == Installing documentation == make -C doc install make[1]: Entering directory/home/rear/rear-2.2/doc'
    install -Dp -m0644 rear.8 /usr/share/man/man8/rear.8
    make[1]: Leaving directory `/home/rear/rear-2.2/doc'
    sed -i -e 's,/etc,/etc,' \
    -e 's,/usr/sbin,/usr/sbin,' \
    -e 's,/usr/share,/usr/share,' \
    -e 's,/usr/share/doc/packages,/usr/share/doc,' \
    /usr/share/man/man8/rear.8

    VERIFIED THE VERSION:
    rear --version
    Relax-and-Recover 2.2 / 2017-07-20

    MY ISSUE IS THAT WHEN I EXECUTE A rear dump command i get the following error:
    sudo rear dump
    Relax-and-Recover 2.2 / 2017-07-20
    Using log file: /var/log/rear/rear-gitlab.log.lockless
    ERROR: EFI_STUB="" is incorrect option value pair.
    Aborting due to an error, check /var/log/rear/rear-gitlab.log.lockless for details

    AND THE LOG FILE DOESN'T SHOW MUCH AS YOU CAN SEE:
    sudo cat /var/log/rear/rear-gitlab.log.lockless

    2020-02-06 13:32:02.681536255 Relax-and-Recover 2.2 / 2017-07-20
    2020-02-06 13:32:02.683035461 Command line options: /usr/sbin/rear dump
    2020-02-06 13:32:02.684207239 Using log file: /var/log/rear/rear-gitlab.log.lockless
    2020-02-06 13:32:02.685783554 Including /etc/rear/os.conf
    2020-02-06 13:32:02.687440260 Including conf/Linux-i386.conf
    2020-02-06 13:32:02.689014550 Including conf/GNU/Linux.conf
    2020-02-06 13:32:02.698201718 Including conf/Ubuntu.conf
    2020-02-06 13:32:02.700722677 Including /etc/rear/local.conf
    2020-02-06 13:32:02.704175285 ======================
    2020-02-06 13:32:02.705457415 Running 'init' stage
    2020-02-06 13:32:02.706756517 ======================
    2020-02-06 13:32:02.712420956 Includin

    AND THE LOG FILE DOESN'T SHOW MUCH AS YOU CAN SEE:
    sudo cat /var/log/rear/rear-gitlab.log.lockless

    2020-02-06 13:32:02.681536255 Relax-and-Recover 2.2 / 2017-07-20
    2020-02-06 13:32:02.683035461 Command line options: /usr/sbin/rear dump
    2020-02-06 13:32:02.684207239 Using log file: /var/log/rear/rear-gitlab.log.lockless
    2020-02-06 13:32:02.685783554 Including /etc/rear/os.conf
    2020-02-06 13:32:02.687440260 Including conf/Linux-i386.conf
    2020-02-06 13:32:02.689014550 Including conf/GNU/Linux.conf
    2020-02-06 13:32:02.698201718 Including conf/Ubuntu.conf
    2020-02-06 13:32:02.700722677 Including /etc/rear/local.conf
    2020-02-06 13:32:02.704175285 ======================
    2020-02-06 13:32:02.705457415 Running 'init' stage
    2020-02-06 13:32:02.706756517 ======================
    2020-02-06 13:32:02.712420956 Including init/default/005_verify_os_conf.sh
    2020-02-06 13:32:02.714087720 Including init/default/010_EFISTUB_check.sh
    2020-02-06 13:32:02.716085961 ERROR: EFI_STUB="" is incorrect option value pair.
    ==== Stack trace ====
    Trace 0: /usr/sbin/rear:496 main
    Trace 1: /usr/share/rear/lib/framework-functions.sh:95 SourceStage
    Trace 2: /usr/share/rear/lib/framework-functions.sh:49 Source
    Trace 3: /usr/share/rear/init/default/010_EFISTUB_check.sh:6 source
    Message: EFI_STUB="" is incorrect option value pair.
    == End stack trace ==
    2020-02-06 13:32:02.722219122 Running exit tasks.

    IF ANYONE CAN SHED SOME LIGHT ON HELPING ME RESOLVE I WOULD GREATLY APPRECIATE YOUR HELP.
    THANKS,

    Mark Jones
    @kingpoop
    Never Mind I figured it out.
    natur3kid
    @natur3kid
    Hi Everyone, can I install rear on RPI4 running kali and then make a USB Stick?
    for recovry of the current state
    Dennis Appelon Jensen
    @AppelonD
    Hi all, any idea why rear, when making backup on SLES 12 SP4 on Power gets stuck doing the creation of the tar archive ? it always only reaches 334 MiB and then nothing happens....