-
Notifications
You must be signed in to change notification settings - Fork 246
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
Question: Adequate REAR Validation Measures ? #2782
Comments
@paulra1 Hi - thanks for using ReaR, however, you cannot expect from us that we validate your hardware setup. The ultimate test has to be done by you. Don't be afraid to test it out as thousands of other end-users already did it before you. |
Hi gdah Best Regards, |
I assume your System76 machine is the one that actually matters for you If my assumption is right, then yes, do that! Try out how ReaR behaves on your Dell machine because Regarding your question if a successful recovery on your Dell machine The only possible answer is of couse NO. The reason is that things are different on different hardware. See the section Those areas are in particular firmware (BIOS type / UEFI) Different firmware can behave differently https://tech-docs.system76.com/models/gaze16/README.html
while in contrast
but it tells nothing about BIOS type or UEFI but I assume You wrote that the one has a ReaR is known to work with SATA and NVMe disks. I only tell that there is no proof when ReaR works on one particular hardware In general regarding different hardware: When you do not have fully compatible replacement hardware Migrating a system onto somewhat different hardware Regarding migration to a system with a bit smaller or a bit bigger disk I reccommend to not use AUTORESIZE_PARTITIONS="yes" In general regarding system migration with ReaR In general migrating a system onto different hardware In sufficiently simple cases it may "just work" but in general In general ReaR is first and foremost meant to recreate |
Hi Johannes: Thank you for your lucid explanation. I don't believe my question could be addressed better, You are right that the Dell machine is just being used as a playground and your comments make While both machines are UEFI machines, their BIOS are significantly different. Best Regards, Paul R. |
@paulra1 Only as a side note FYI: |
Relax-and-Recover (ReaR) Issue Template
Fill in the following items before submitting a new issue
(quick response is not guaranteed with free support):
ReaR version ("/usr/sbin/rear -V"): Relax-and-Recover 2.6-git.0.0.master.changed / 2022-03-11
OS version ("cat /etc/os-release" or "lsb_release -a" or "cat /etc/rear/os.conf"): Ubuntu 20.04.3
ReaR configuration files ("cat /etc/rear/site.conf" and/or "cat /etc/rear/local.conf"): local.conf
Hardware vendor/product (PC or PowerNV BareMetal or ARM) or VM (KVM guest or PowerVM LPAR): N/A
System architecture (x86 compatible or PPC64/PPC64LE or what exact ARM device): AMD64
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): SSD
Storage layout ("lsblk -ipo NAME,KNAME,PKNAME,TRAN,TYPE,FSTYPE,LABEL,SIZE,MOUNTPOINT"): Approximate
Dear Staff:
I would like to prove that the bare-metal rear backup procedures I developed for the System76
machine, described below, are valid. However, I don't have a spare System76 machine. I think,
but don't know, if the procedures work on the Dell machine, described below, configured with
the same Linux OS version as the System76 machine, the same backup procedures will also
work for the System76 machine.
In your opinion, is performing rear validation on the Dell machine sufficient to prove the same
set of procedures used for the Dell machine will also work for the System76 machine?
(Assume they have machines have same release of the Ubuntu 20.04.3 LTS OS installed on them.)
The System76 machine is described by the following link.
It has an 11th Gen Intel® Core™ i7-11800H @ 2.30GHz × 16 processor, 16GB RAM, and a 1TB SSD.
The Dell Latitude machine is described by the following links.
It has a i5-2520M @ 2.5Ghz processor, 8GB RAM and a 128GB SSD.
Both of the above machines have AMD64 architecture and satisfy the Ubuntu requirements described by
the following link.
The sequence of validation procedures is as follows.
Install Linux Ubuntu 20.04.3 LTS on the machine.
Use "rear mkbackup" on an external USB disk to create a rescue disk with both boot and data sectors.
Erase the internal disk on the machine.
Use the rear image on thee external USB disk to restore the machine.
Best Regards,
Paul R.
*
Workaround, if any:
Attachments, as applicable ("rear -D mkrescue/mkbackup/recover" debug log files):
The text was updated successfully, but these errors were encountered: