New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Backup Archive not readable #2329
Comments
Hi,
Did you mean Either way, I'd appreciate if you could provide us with debug output from problematic sessions ( V. |
No, the When I'm booting off the ISO, and I get to the menu, login as root and run I just tried with 2.5, same issue. Backup archive is not readable. |
@dveleztx
which makes it needlessly hard for us to find out I am a bit confused by your description about what kind of hardware First and foremost ReaR is meant to So if you try to recreate on incompatible replacement "hardware" Furthermore Finally see
see also "Debugging issues with Relax-and-Recover" in |
@dveleztx
in particular how "your browser" is related there.
See also "Recovery medium compatibility" |
@jsmeix One of the few I saw is seen here: https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/system_administrators_guide/ch-relax-and-recover_rear So, the process is this:
I will try performing a To elaborate on the oVirt piece: My VMs that I'm backing up are on oVirt, and I run my My assumption is that it's the Viewer app, the application that allows you to "console" into your VM. But, I discovered that wasn't the case, I tried several and they all show the console to be frozen. I thought maybe it was a browser issue as well, that is also not the case. That part I'll have to investigate. I'll update soon, thanks! |
I was able to rescue on my test. I did the rescue on my Synology NAS. Instead of doing Thank you @jsmeix ! |
@dveleztx I cannot find a All I can find are things like
so as far as I can see our sources look good. Also in the third-party documentation of Red Hat |
Spelling fix 'REAR' => 'ReaR' cf. rear/rear#2329 (comment)
I just realized that I meant |
Thank you for your frank feedback! |
ReaR version ("/usr/sbin/rear -V"):
ReaR 2.3
OS version ("cat /etc/rear/os.conf" or "lsb_release -a" or "cat /etc/os-release"):
Ubuntu 18.04.3 LTS (Bionic)
ReaR configuration files ("cat /etc/rear/site.conf" and/or "cat /etc/rear/local.conf"):
Hardware (PC or PowerNV BareMetal or ARM) or virtual machine (KVM guest or PoverVM LPAR):
oVirt Virtual Machine, although having issues with it freezing when booting from ISO, so for the moment being I'm using a Synology NAS to create the VM and do the rescue (then export it to see if that works for oVirt).
To elaborate, I get my ISO. I use the ISO on oVirt to boot to it, and when it starts booting up after selecting "Rescue " it freezes after a few moments. No idea why. So, I have a Synology NAS can can spin up machines, I create a VM there, boot to the ISO, works fine. But, then I run
rear rescue
, and it tells me that the tar.gz is not readable. It's pointing to some/tmp
path. I don't get it.System architecture (x86 compatible or PPC64/PPC64LE or what exact ARM device):
x86_64 architecture on both VM and Synology
Firmware (BIOS or UEFI or Open Firmware) and bootloader (GRUB or ELILO or Petitboot):
UEFI
Storage (local disk or SSD) and/or SAN (FC or iSCSI or FCoE) and/or multipath (DM or NVMe):
Virtual Disk, technically an SSD on both the oVirt Host and Synology
Description of the issue (ideally so that others can reproduce it):
I'm trying to make backups for my VMs on oVirt. As described above, I've had no luck with ISOs on oVirt. It comes up to the menu, select Rescue , and it starts loading, and freezes up. Thought it was maybe my browser or ovirt viewer, even tried looking at it from another OS, no dice.
At this point, all I really care about is if these backups actually do work. So far, I can't prove that my backups are even working because I can't rescue them. My alternative solution was to spin up a VM on my Synology NAS, and do the rescue there, and then export that VM to an OVA and see if the oVirt can take that image. It's a pain, but there aren't a lot of good options for backup solutions for oVirt that I've found.
Anyway, I go through the menu on the Synology, I get to the prompt and run
rear rescue
and it stops a moment later saying the tar.gz file is not readable.Attachments, as applicable ("rear -D mkrescue/mkbackup/recover" debug log files):
Here's the full error after running
rear recover
The text was updated successfully, but these errors were encountered: