by

Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    msatheesh84
    @msatheesh84
    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....
    Julian Einwag
    @jeinwag
    Hi, I'm currently trying to get rear working and I'm having some trouble during restore. I'm backing up a Debian 10 box to a CIFS share with tar. When I try to restore the machine from the rear rescue system, at some point during the restore of the files, tar gets killed because the system runs out of memory. Running 'free' afterwards shows that almost all of the memory (tesing on a VM with 8 GB of RAM) is used by buffers/cache and only very little memory (about 120 MB) is available. I don't understand what's happening here, any hints are appreciated.
    orioldelos
    @orioldelos
    Hi.. I have been experimenting with REAR and Rsync backup on a Synology server.... I finally seem to have gotten it to work with the permissions being kept on the Synology NAS, but I can only do it using rsync access (not ssh) and it keeps asking for password (it asks for it 3 different times) Is ther a way I can input the rsync user password in the configuration so that it does not require me to type it each time so that I can automate it on a daily basis?
    ismetsener
    @ismetsener
    hello
    relax-and-recover can you make a backup of a running linux system
    complete disk backup
    ?
    SaymonDzen
    @SaymonDzen
    Hello!
    Please share the current manual on tincture rear for bareos.
    ismetsener
    @ismetsener

    Hi,

    I have a installed centos 7 on a usb-stick (32gb)
    On this production environment I have mounted 2 disk as software raid1 -> /dev/md0 mounted to /raid1

    Now I make a rear backup of the centos system (excluding /raid1 and /mnt etc) The location of the backup is /raid1

    But when I recover, the system cannot find the backup location to recover (cannot find backup.tar.gz)

    What steps I have to take?

    my conf file looks like


    OUTPUT=ISO
    OUTPUT_URL=file:///raid1/rear-backup/
    BACKUP=NETFS
    BACKUP_URL=file:///raid1/rear-backup/
    EXCLUDE_BACKUP=('/media' '/raid1' '/mnt' '/var/tmp' '/var/crash')
    NETFS_KEEP_OLD_BACKUP_COPY=yes


    With kind regards,
    Ismet

    pdv-systeme-sachsen
    @pdv-systeme-sachsen
    Hi,
    after some searching in manpages I cannot find an option or possibility to include a mounted Storage LUN in the backup. It is a 3PAR LUN.
    Kidn regards, Thomas
    ronsawyer777
    @ronsawyer777
    Relax-and-Recover 2.4 / 2018-06-21
    Using log file: /var/log/rear/rear-rsawyer-fedora.log
    Using backup archive '/backup/rsawyer-fedora/backup.tar.gz'
    Creating disk layout
    Excluding component fs:/backup
    Using guessed bootloader 'GRUB' (found in first bytes on /dev/nvme0n1)
    Creating root filesystem layout
    Handling network interface 'enp0s31f6'
    enp0s31f6 is a physical device
    Handled network interface 'enp0s31f6'
    Skipping 'tun0': not bound to any physical interface.
    Skipping 'virbr0': not bound to any physical interface.
    Skipping 'virbr1': not bound to any physical interface.
    Skipping 'virbr10': not bound to any physical interface.
    Skipping 'virbr13': not bound to any physical interface.
    Skipping 'virbr14': not bound to any physical interface.
    Skipping 'virbr15': not bound to any physical interface.
    Skipping 'virbr16': not bound to any physical interface.
    Skipping 'virbr17': not bound to any physical interface.
    Skipping 'virbr4': not bound to any physical interface.
    Skipping 'virbr5': not bound to any physical interface.
    Skipping 'virbr9': not bound to any physical interface.
    Handling network interface 'wlp4s0'
    wlp4s0 is a physical device
    Handled network interface 'wlp4s0'
    Copying logfile /var/log/rear/rear-rsawyer-fedora.log into initramfs as '/tmp/rear-rsawyer-fedora-partial-2020-05-07T15:22:21-04:00.log'
    Copying files and directories
    Copying binaries and libraries
    Copying kernel modules
    ERROR: nls_cp437 exists but no module file?
    Aborting due to an error, check /var/log/rear/rear-rsawyer-fedora.log for details
    Exiting rear mkbackup (PID 97614) and its descendant processes
    Running exit tasks
    You should also rm -Rf /tmp/rear.hKGigvLPVESRPkW
    Terminated
    Any suggestions? Thanks in advance!
    trippinnik
    @trippinnik
    I'm testing restore and it dies unable to find the backup file. Seems it's not mounting the nfs path that the backup is run to but I can tell why
    Albert Szostkiewicz
    @tmdag
    Hi!, just came across PDF presentation about rear from @gdha from 2010. And You have mentioned about future plans for rear-server. Did that project ever started ? (I'm looking currently for any solution that would help me tracking backups of all machines and ideas mentioned in your PDF sound like what i was looking for). Thanks!
    Micky Barzilay
    @mikibarzilay
    Hello, is there any way to complete backup my server (with multiple disks) into one image (iso) file?
    I executed rear -v mkrescue and the image is only 300MB (I have about 250GB data on the server)
    asmkaiser
    @asmkaiser
    Hello everyone , need urgent support
    I have created a whole back up .. of disk /dev/nvme{01,02,03,etc}
    Now i want to recover the system into another disk /dev/sda
    is it possible ??
    asmkaiser
    @asmkaiser
    No problem ... just figured it now ...
    Noua Toukourou
    @baba-tunde

    Hi guys. Hope you're doing good ?
    Could you please tell me if the following errors are critical or not ? and What does that mean for REAR ?

    #

    Skip copying broken symlink '/etc/resolv.conf' target '/run/resolvconf/resolv.conf' on /proc/ /sys/ /dev/ or /run/
    Failed to copy target of symlink '/etc/mtab' -> '/etc/mtab'
    Symlink '/etc/pki/nssdb' -> '/var/lib/nssdb' refers to a non-existing directory on the recovery system.
    It will not be copied by default. You can include '/var/lib/nssdb' via the 'COPY_AS_IS' configuration variable.
    Symlink '/usr/share/misc/magic' -> '/usr/share/file/magic' refers to a non-existing directory on the recovery system.
    It will not be copied by default. You can include '/usr/share/file/magic' via the 'COPY_AS_IS' configuration variable.
    Symlink '/lib/modules/4.4.0-62-generic/build' -> '/usr/src/linux-headers-4.4.0-62-generic' refers to a non-existing directory on the recovery system.
    It will not be copied by default. You can include '/usr/src/linux-headers-4.4.0-62-generic' via the 'COPY_AS_IS' configuration variable.

    #

    Thanks in advance

    Vladimir Gozora
    @gozora
    Not critical, it just says that some links are missing their targets in ReaR recovery system (ISO you use for booting broken system).
    from plain looking at the list, ReaR is not using any of those files during recovery
    Noua Toukourou
    @baba-tunde
    Thanks @Vladimir for your answer. Currently my backup archive is about 3GB but the machine has 2 disks with 1.5TB of data. Is it normal ?
    Vladimir Gozora
    @gozora
    since i dont know your setup, I cant tell what us normal. ReaR is by default setup to backup only internal disks. multipath, raids are excluded afik..
    Vladimir Gozora
    @gozora
    you should not mix OS files and user data in ReaR. ReaR is intended mostly for OS backup/recovery, your data should be backed up somewhere else
    Noua Toukourou
    @baba-tunde
    Hi @gozora , I made a test and rear only took in account my OS disk. What is strange. Because on Centos7 it took all the volumes attached.
    How to have the same behavior on Ubuntu 14.04LTS ? Thanks
    Andrea G.
    @Rigido71
    Maybe someone could found it useful...
    On our RHEL lpars we use TSM for everyday backup of both system and application data and we were searching for a quick way to recover from OS crash. Using ReaR we found the way to recover just disk and filesystem structures and restore OS filesystems, we will use TSM to restore application data.
    As we will use just multipath devices, it is important to put:
    AUTOEXCLUDE_MULTIPATH=n
    into a conf file. Then we set BACKUP program to backup just included filesystems:
    BACKUP_ONLY_INCLUDE=YES
    BACKUP_PROG_INCLUDE=( '/boot' '/' )
    That's all...
    Andrea G.
    @Rigido71
    Hi, can someone help me to configure a SLES15 with btrfs?