rear/rear

Relax-and-Recover - Linux bare metal disaster recovery and system migration solution (cfr. mksysb, ignite)

daebenji

@daebenji

how should i know?

mattiscb

@mattiscb

You couldn't know. that's why i told you =) is there somewhere a comprehensive document telling me how i could create a working usb backup/rescue-system with uefi an secure boot from an ubuntu20.04?

Gratien D'haese

@gdha

It turns out they are symlinks on the core system, making them broken on the ISO if backing up to them, has anyone run into this? is there a known solution
@awienecke_gitlab seems serious - please open an issue for this

mattiscb

@mattiscb

thanks daebenji, i got legacy stick working. better than nothing atm

pyfan1

@pyfan1

Is there any way to get NTFS support in the recovery environment? I happily sent the tar file to an NTFS drive. Now when I boot the rescue disk and try to mount that drive, it says the NTFS filesystem type is unknown. If it makes any difference, I'm running CentOS 7. ReAR 2.4

kevanlanister735

@kevanlanister735

I have performed a rear -d -v mkbackup using a local.conf that has BACKUP_URL and OUTPUT_URL as a local file:/// in the home directory of my CentOS7 box (because home was a large partition that had lots of space)

it seems like the .tar file generated does not include my /home/* directories

is this because my backup file location was in /home?

is there any way around this if I need to create the backup local to the box and that is the only partition available?

kevanlanister735

@kevanlanister735

If a rear -d -v mkbackup is interrupted, will rear continue where it left off? do i need to enable rsync backup to make that happen?

SeyyedKhandon

@SeyyedKhandon

in this topic https://askubuntu.com/questions/1295016/how-to-create-full-backup-bootable-iso-file-using-relax-and-recover-app

I'm going to use rear for a full backup with one iso

but everything which i did, was the generating a 250mb iso and a 1.7gb tar.gz

What I want is just 1 bootable ISO which contains the whole backup of my current centos 7 (with its all configs and installed apps) that can be write later in a bootable matter on USB stick and be installed on other machines.

how should i do this?

Gratien D'haese

@gdha

in this topic https://askubuntu.com/questions/1295016/how-to-create-full-backup-bootable-iso-file-using-relax-and-recover-app

Why not make a bootable USB stick and write backup to it as well? See http://relax-and-recover.org/documentation/usecases

SeyyedKhandon

@SeyyedKhandon

The problem with only usb solution is the backup is available as the usb is available, so I cant send it to anyone to use it.

SeyyedKhandon

@SeyyedKhandon

Isn't there any solution ?

SeyyedKhandon

@SeyyedKhandon

After struggling with this need and the problem, I Asked it on the rear/rear#2530, and the answer as in the below:
it will generate 1 bootable iso in /var/lib/rear/output/rear-YOURSYSTEMNAME.iso

OUTPUT=ISO
OUTPUT_URL=null
BACKUP=NETFS
BACKUP_URL="iso:///backup"

And you can install it where ever you want. Please read the issue carefully.
In my experience, if the automatic restore failed, you should manually restore it as the rear video says:

https://relax-and-recover.org/

rear recovery steps:

rear username: root

command to restore: rear recover

SeyyedKhandon

@SeyyedKhandon

update

if you want to generate .iso straight into your usb stick, you can do as below steps:

# mkdir /other
# umount /dev/sdb1
# mount /dev/sdb1 /other

OUTPUT=ISO
ISO_DIR=/other
OUTPUT_URL=null
BACKUP=NETFS
BACKUP_URL="iso:///backup"

thanks to @jsmeix

more details on rear/rear#2530

wbrells

@wbrells

I'm just starting to use Relax-and-Recover with Mint 20.04, so I expect I'm doing something that is obviously wrong. I used the command git clone https://github.com/rear/rear.git to install Relax-and-Recover, and that went fine. However, when I tried to format a USB stick with the commands: cd rear/ and sudo usr/sbin/rear format /dev/subc (subc is the usb stick) the command fails and the log file shows an error message of "Failed to create msdos partition table". I've tried different USB sticks and get the same message. Can someone suggest what I'm doing wrong? Many thanks!

wbrells

@wbrells

Problem solved! The USB stick needed to be UMOUNTed before it could be formatted. The error message could have been more helpful, but I was able to successfully format the USB stick and start the backup process. However, backing up to the USB stick was so slow that I gave up after an hour or so. It would probably have been faster if backing up to a hard disk, but I decided to switch over to a different program. I've settled on using Macrium Reflect's bootable Rescue Media which seems to be working well for me.

sway-vmware

@sway-vmware

Hi, I'd like to use an USB drive to store backup.tar.gz, but when I tried to mount the USB drive for restore, the rescue OS complains that ntfs filesystem unknown. What is the best way to add ntfs modules to the rescue ISO?

Gratien D'haese

@gdha

Hi, I'd like to use an USB drive to store backup.tar.gz, but when I tried to mount the USB drive for restore, the rescue OS complains that ntfs filesystem unknown. What is the best way to add ntfs modules to the rescue ISO?

Add MODULES=( 'all_modules' ) to the /etc/rear/local.conf file

sway-vmware

@sway-vmware

thanks @gdha , is there a trick to get the rescue iso bootable after adding the MODULES line? I have upgraded rear to 2.6 but the rescue would hang after selecting Recover from the menu

cvijayvinoth

@cvijayvinoth

How to add proxy information while restore the data using iso image ( medium us RSYNC)?

Gratien D'haese

@gdha

thanks @gdha , is there a trick to get the rescue iso bootable after adding the MODULES line? I have upgraded rear to 2.6 but the rescue would hang after selecting Recover from the menu

@sway-vmware Try first to get a prompt from the rescue medium after booting. From the command line you can also start a recover easely.

Jonathan Shepherd

@jon_sco_gitlab

Hi All, I'm looking for a bit of advice. I'm currently evaluating this software and want to start using it to move a few old physical Linux servers to our virtual environment. I've run through all the steps and have created an ISO image on a central server. However, when I try to recover the ISO into my virtual environment it always errors with the following: ERROR could not find Directory /boot/grub. So it does sound like it's not recreating the boot partition correctly when restoring from the ISO. Any ideas?

pcmurphy101

@pcmurphy101

I am attempting use REAR 2.4 on a HP DL380 G10 running RHEL 8.3. The problem I am having is that when I boot this UEFI system with the ISO burned on a DVD the system does not recognize the DVD as a bootable. Any suggestions as to what I could be doing wrong?

ikarpov

@ikarpov:matrix.org

[m]

Hi all!

I am pretty new to ReaR backup and ran into a weird issue:
Skipping 'eth0': not yet supported.
Failed to handle network interface 'eth0'.

Both mkrescue and mkbackup produce this error and I got no idea about the reason and how to solve it

It's CentOS Linux release 7.5.1804

ReaR 2.4

ikarpov

@ikarpov:matrix.org

[m]

I believe that this line " # Skip fake interfaces without MAC address
[ "$mac" != "00:00:00:00:00:00" ] || return $rc_error" is to blame. But why? And what is the proper way to handle such errors?

lexzz

@lexzz

Good morning everyone, I'm new to rear and have a question I can't find the answer for. I used rear to make a bootable usb for a baremetal Proxmox VE machine (Debian). After booting rear the USB keyboard doesn't work. I tried to connect with SSH but the machine asks for a password. Can someone give me a tip to make the keyboard work and/or configure the SSH password. Thank you very much!

golgotow

@golgotow

Good day to all.

Can I ask you if you have experience with NBU 8.2 on Linux + ReaR ? For now this not work at all :)

golgotow

@golgotow

Looks like pbx_exchange is not starting, also a lot of nbu directories I tried to add via COPY_AS_IS , rear is 2.4 from centos repositories

Michael L. Metts

@mmetts

Hi. I am running Relax-and-Recover 2.4 on a RHEL 7.7 PPC64le with an NFS target and I'm ending up with a TAR file that just has the REAR log in it and nothing else. Looking through the log nothing really stands out. In other words, I don't see anything all that strange in the way of errors. I have it working successfully on other RHEL PPC64le machines but on those, I'm doing the "giant ISO all in one" approach and that's working fine. Has anyone seen or heard of this oddity with the TAR file? Thanks.

I'll add that it runs pretty fast (too fast) at the end like something's getting skipped over.

But it doesn't generate any significant errors that I can see.

Michael L. Metts

@mmetts

It appears that I have an empty include list. I see closed issues related to that but have not found one that matches my situation or otherwise figured it out yet. If anyone has more clues, I would appreciate it. Thanks.

Michael L. Metts

@mmetts

Figured it out. It's a boot_over_SAN issue. Thanks.

Seth Kushniryk

@sethkush

Hi, I'm wondering if there's a way to run my backups through split during creation. I backup using netfs and tar to a local disk. After the backup I typically run "split -d -b 5G backup.tar.gz backup.tar.gz.". Is there a way to have rear do this during creation?

John Hamilton

@JohnHam21629495_twitter

Hi I am getting errors when trying to install. I managed to get by most but am stuck at ERROR: FindStorageDrivers called but STORAGE_DRIVERS is empty and no builtin storage modules found. Using CentOS Latest Versions or rear 2.6. Any advice?

LiamFry

@LiamFry

Hello! How do I prune one or more backups? There's a HOWOT link in the documentation but it's broken. I'm out of space on my backup device and I really would like to free some up.

Where communities thrive

People

Repo info

Activity

rear recovery steps:

update