Installing old FreeBSD (7.2, amd64) from DUMP Files

Hello everyone,
I'm a little stuck - I have an old important PC which doesn't run anymore.
I have dump Backups of the following:
/
/var
/usr

The System running was:
7.2-STABLE FreeBSD

I have listings of bsdlabel, dmesg, fstab and gpart for the boot drive.

I've downloaded the 7.2-RELEASE dvd1 and livefs.iso but I am unsure as how to proceed to restore. I'd like to create a virtual machine in Proxmox where I can restore this old PC to.

Thank you very much for your help.
 
We had to import a very old FreeBSD server at some point a few years back We ended up using a recent FreeBSD release, installing the relevant compat files, and then creating a jail for this with the old binaries.
 
We had to import a very old FreeBSD server at some point a few years back We ended up using a recent FreeBSD release, installing the relevant compat files, and then creating a jail for this with the old binaries.
Is there any howto I could follow to try this? I'm not a real FreeBSD pro :-).
 
What happens if you just do a `restore` from your dump files?

It is what it is intended for.
I'll try that - but I'm not very used to FreeBSD - I just found a howto on cloning. I though I'd do an install of the ISO and then restore the dump files. Is there any HowTo or similar I could follow?
 
I'll try that - but I'm not very used to FreeBSD - I just found a howto on cloning. I though I'd do an install of the ISO and then restore the dump files. Is there any HowTo or similar I could follow?

dump + restore is simple. The manpage will do.

Kind of similar to un-tarring a tarfile.
 
I've just tried with a new disk and a live-cd from an old freebsd.
I can restore the root dump successfully but on all other dumps I'm getting the following error:
Command:
restore -r -f /mnt/cd/usr.dump

Response:
Tape is not a dump tape

Could this be due to the size of the partitions? The root partition was ~1GB the other partitions ~10GB.
I've formatted the partitions with the following command:
newfs -U -O 2 /dev/ad4s1f
 
It seems it was a problem with the ISO I've created to mount it in proxmox, now it's working. But I'm out of temp-space :-).
I'll see if I can get a workaround for this working. Thank you for your help!
 
I'm restoring the dump files and it seems to be working. Can I just edit the new disk names in the fstab file to boot from it afterwards (e.g. /dev/da0s1a to /dev/ad4s1a)?
 
Can I just edit the new disk names in the fstab file to boot from it afterwards (e.g. /dev/da0s1a to /dev/ad4s1a)?
Yes, additionally the first time the bootloader might complain too. Just tell it to boot from correct disk.

What's so important that it requires an 11 year old EoL version?
 
Thank you, I'll try.
It's an old project where I need to take a look on the code while it's running - and what better option as to virtualize it :)
 
It's an old project where I need to take a look on the code while it's running - and what better option as to virtualize it
I'd also like to point out the various COMPAT_FREEBSD? options in the kernel, and misc/compat7x and associated compatNx compatibility libraries. Which will allow you to run binaries compiled for old(er) versions of FreeBSD on up to date systems.
 
Back
Top