Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Jason Hurd
    @jasonhurd
    Hello All, I have three installations of Ubuntu 16.04.5 LTS and only one of them shows rear available for installation in APT. And the one installation that it does show, only has version 2.00 available. Any ideas?
    nadloga
    @Pintar_gitlab
    Hi guys, one stupid question but, i am able to recover my system to /mnt/local but what next. Documentation states that after reboot VM will be fine. But FileSystem mounted from /mnt/local isnt copied to /. How can i achieve this? Thnx
    Dorothea Muecke-Herzberg
    @domuhe
    Hello All, I have trouble recovering an Ubuntu 18.04 backup to a smaller disk on a different hardware. The original system is on a RAID (3TB) and the restore system is just a single drive 2(TB). The Backup is just 70GB. But recover complains that the last partition has to be shrunk more than 2%. How can I address that?
    chumunga
    @chumunga
    Hi All, been testing ReaR for about a week now, I notice incremental backups doesn't work when BACKUP_URL=file:/// (in my case to an FSTAB mount), but when BACKUP_URL=CIFS:// works just fine, is this a known limitation?
    chumunga
    @chumunga
    In case someone else has the same question rear/rear#1146 I guess BACKUP_URL=file:/// is the same as USB
    Dan
    @Dan75060179_twitter
    Does anyone know if Relax-And-Recover will work under LinuxMint 17.1 ?
    chumunga
    @chumunga
    would anyone know if possible or how to backup mount point? like a mounted nas
    Eason Family
    @tomlauri_twitter
    Have a couple suggestions for the next REAR release: would like to see if the "lsblk" command could be added to the rear recovery; also can we get UDF, NFS, and USB_STORAGE modules loaded automatically? Currently I have to make sure I modprobe them before making a backup as well as having to add lsblk to /usr/bin in order to see if my USB device mountable, and in order to add the file, I have to mount a cdrom using modprobe udf. One last request is to see if ntfs-3g can be added as well, this would help to read a DVD that was created in Windows.
    Eason Family
    @tomlauri_twitter
    An additional request; I would also like the ISO image to be created during a backup using OUTPUT=USB... (just incase I would need to create a bootable CD to do a recovery). Right now I can either have the ISO created as part of the backup, or have a bootable USB device, but not both.
    Eason Family
    @tomlauri_twitter
    I would like to add /usr/bin/ntfs-3g to my mkrescue image... how do I add that to the local.conf file so I can ntfs-3g mount my external hard drive?
    Eason Family
    @tomlauri_twitter
    Never mind all my questions above; I have figured it out on my own. I now can make a USB device, with ISO included in the backup, and can mount my "windows" external hard drive using ntfs-3g during rear recovery.
    rudraach
    @rudraach
    Hi I'm facing one issue while restoring the backup
    chroot : failed to run command '/bin/bash' : no such file directory
    any idea how to fix it?
    basically backup include VG and LV
    rudraach
    @rudraach
    iso image size is 32Gb
    cvijayvinoth
    @cvijayvinoth
    Is there any options to backup external harddisk ( /media ) data using ReaR-rsync methodology ?
    daebenji
    @daebenji
    Hello Folks, is there any recommandation how to handle an old debian lenny, which has to be migrated by p2v? I stuck, after creating a all- in-one iso, which can not be recovered into a virtualbox virtual machine. I read, that rear was made for this tasks (kind of), but it feels like it's getting mad at me when it comes to udev. what is your experience?
    Clovis
    @Tristan3860_twitter
    Hello,
    I have created a backup of my system (disk 960GB).
    I need to restore on a 400GB and 480GB disk
    I have read that adding AUTORESIZE_PARTITIONS=true and creating a /etc/rear/disklayout.conf file would solve

    here is my disklayout.conf:

    lvmdev <volume_group> <device> [<uuid>] [<size(bytes)>]

    lvmdev /dev/rhel /dev/sda3 lea2mY-Uisa-TaBm-mCUR-Mr8Q-FV56-5eZL15

    Format for LVM VGs

    lvmgrp <volume_group> <extentsize> [<size(extents)>] [<size(bytes)>]

    lvmgrp /dev/rhel 4096

    lvmvol <volume_group> <name> <size(bytes)> <layout> [key:value ...]

    lvmvol /dev/rhel home 53687091200b linear
    lvmvol /dev/rhel root 317083927552b linear
    lvmvol /dev/rhel swap 4294967296b linear

    Filesystems (only ext2,ext3,ext4,vfat,xfs,reiserfs,btrfs are supported).

    Format: fs <device> <mountpoint> <fstype> [uuid=<uuid>] [label=<label>] [<attributes>]

    fs /dev/mapper/rhel-home /home xfs uuid=a7f43e71-b3fd-4d6c-9c4a-18d3ba3e0d78 label= options=rw,relatime,attr2,inode64,noquota
    fs /dev/mapper/rhel-root / xfs uuid=43ce6f3e-9f55-4b7a-bb9b-5a95d4271caf label= options=rw,relatime,attr2,inode64,noquota
    fs /dev/sda1 /boot/efi vfat uuid=D447-C421 label= options=rw,relatime,fmask=0077,dmask=0077,codepage=437,iocharset=ascii,shortname=winnt,errors=remount-ro
    fs /dev/sda2 /boot xfs uuid=4e2d2106-6365-417d-9587-61afc9800f53 label= options=rw,relatime,attr2,inode64,noquota

    Swap partitions or swap files

    Format: swap <filename> uuid=<uuid> label=<label>

    swap /dev/mapper/rhel-swap uuid=67329c6e-c824-4e3b-8fdf-c12c7b148461 label=

    restore fails with error on lmvgrp
    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:
    https://stackoverflow.com/questions/4341442/gzip-with-all-cores
    «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.