Relax-and-Recover - Linux bare metal disaster recovery and system migration solution (cfr. mksysb, ignite)
Aye, it was set up, and formatted. Showed as REAR-000. i manually made backups with mkrescue and mkbackups.
I often booted from the USB disk, to check that i could boot into it, and loaded the ReaR recovery menu. All worked. :) That was on the original PC on which i made it.
But, now that i need it, it wont work :( Original PC stolen.
I often booted from the USB disk, to check that i could boot into it, and loaded the ReaR recovery menu. All worked. :) That was on the original PC on which i made it.
But, now that i need it, it wont work :( Original PC stolen.
I wonder if disk itself did not damage?
As stated, i used Testdisk, which recovered some files. But, cannot open any of them. Tried to extract them too. I think ReaR maybe encrypts it?
As stated, i used Testdisk, which recovered some files. But, cannot open any of them. Tried to extract them too. I think ReaR maybe encrypts it?
maybe you had default encryption directly by disc controller. think pads do offer AES encryption directly from the controller and I'm quite sure, that those are not the only one. But the backup itself should not be encrypted. If everything is on your drive, why don't you have a look at the created .iso (extract it and see if you can read the files and if they are encrypted). If you succeed, than you can at least manually revover your files. Another sad option would be a bad usb drives filesystem. It would not be the first time we hear from data loss after a broken flash device.
Mine was a ThinkPad P50. I often wondered if it was not something my laptop did to the drive, that it worked there, but, wont work anywhere else.
Using Testdisk and Photorec, i managed to recover files. Type unknown. It is not ISO files, or compressed (i think?). Just files, that are there, which i cannot open. I also thought that i was onto something at last.
I thought that somehow maybe ReaR itself could open them, since they are obviously there, but, unknown.
That USB drive used to have NTFS on it, and i actually used a deep formatting which took hours to format it, twice. I wanted it to be clean. I know about the MDT keeping stuff, even if we delete and format the drive.
The problem is, it is a 1TB drive, and the "recoveries" i have with Testdisk are like approx 600-700GB. My data that I am trying to recover was not over 200GB, Giving me the impressiomn that the recovery is from the NTFS drive, before i formatted it. I know, that by using tools like Spotmau, I can extract info, even if it has been formatted more than 7 times, Formatted and wiped.
Will see if i can find a way to open these unknown files :)
Normally when i recover files, it is not unknown types.
Thanks a mil for advice so far :)
Using Testdisk and Photorec, i managed to recover files. Type unknown. It is not ISO files, or compressed (i think?). Just files, that are there, which i cannot open. I also thought that i was onto something at last.
I thought that somehow maybe ReaR itself could open them, since they are obviously there, but, unknown.
That USB drive used to have NTFS on it, and i actually used a deep formatting which took hours to format it, twice. I wanted it to be clean. I know about the MDT keeping stuff, even if we delete and format the drive.
The problem is, it is a 1TB drive, and the "recoveries" i have with Testdisk are like approx 600-700GB. My data that I am trying to recover was not over 200GB, Giving me the impressiomn that the recovery is from the NTFS drive, before i formatted it. I know, that by using tools like Spotmau, I can extract info, even if it has been formatted more than 7 times, Formatted and wiped.
Will see if i can find a way to open these unknown files :)
Normally when i recover files, it is not unknown types.
Thanks a mil for advice so far :)
Hi, I'm trying to create a PBA image but it's too large: "ERROR: TCG Opal 2 PBA image file "/var/lib/rear/TCG-Opal-PBA/localhost-live/TCG-Opal-PBA-localhost-live.raw" is 175.00 MiB in size, allowed maximum is 128.00 MiB." Any ideas how to shrink the image / override the limit?
Has anyone used ReaR to assist in migrating a RHEL machine to LUKS-encrypted disks? It would seem like it should be possible by editing the disklayout.conf file perhaps but it's fairly complicated. I've compared a non-LUKS VM and a LUKS'd version (the disklayout.conf) file and seems like this could be possible. I have 6 RHEL 7.8 physical boxes that need to have LUKS encryption and re-installing and re-configuring them from scratch will be a gigantic PITA so would love to be able to leverage ReaR to do this. Thanks!
Hello, I've run into an interesting issue, trying to create a full system backup on iso, but the system is not actually backing up to the iso, it's just a standard 64MB iso, and there is at least 300MB of stuff in /opt. Additionally, I attempted to provide the iso:/// backup_url, but nothing I do seems to affect it. Am I missing something/some kind of configuration?
@chupacabraz_gitlab Supposedly it can be done, you can actually copy the luks vm's /var/lib/rear/layout/disklayout.conf (just run a backup of a blank machine that matches where you're migrating to) to the non-luks one and place it in /etc/rear/ and run the backup... again, supposedly
it should then restore in a similar manner
untested, but maybe worth a shot
hi @daebenji , i have tried to do what you advised but it still failed, below are my config for both ~/.ssh/config and local.conf
$ cat .ssh/config
Host 172.16.10.17
HostName 172.16.10.17
User sftpuser
IdentityFile ~/.ssh/id_rsa$ sudo cat /etc/rear/local.conf
OUTPUT=ISO
BACKUP=NETFS
OUTPUT_URL=sftp://172.16.10.17/home/sftpuser/
BACKUP_URL=iso:///backup/
BACKUP_PROG_EXCLUDE=("${BACKUP_PROG_EXCLUDE[@]}" '/media' '/var/tmp' '/var/crash')
@wellysunardy Did you exchange your public SSH key with the remote system (add it to ~/.ssh/authorized_keys file)?
that fails with "chroot: failed to run command '/bin/bash': no such file or directory"
despite file /mnt/local/bin/bash shows it to be an ELF Executable
Hello everyone! I seem to be unable to create a Recovery USB-thumbdrive that ist secure-boot compatible. The System I want to backup is Ubuntu 20.04 but the little HP ProDesk thing ist telling me the thumbdrive is not authenticated to boot. I tried several SECURE_BOOT_BOOTLOADER- paths, none works. Anyone here who can maybe help me out of my misery?
it dispaly as UEFI SanDisk in the F9-Boot Menu
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?
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?
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
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
thanks to @jsmeix
more details on rear/rear#2530
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!
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.