Other Inspecting the output of dump(8)

As part of a larger project of reinstalling a server and moving from UFS to ZFS on my VPS, I decided I would back things up - using dump(8). Is there any way I can inspect the blob it outputs? I'd like to verify what's in there and what would be restored at a later time before wiping the current server. Searching the forums, and the greater web, has not been helpful.

Because I know falling victim to the XY-problem (https://xyproblem.info/) is often hard to spot to the user falling victim to it, I'd also take alternative suggestions for getting my current system state onto a new install (installed packages, configurations, created users, etc.), as my main target is moving towards ZFS while minimizing downtime for things I run. I did find a thread about doing this in-place (https://forums.freebsd.org/threads/ufs-to-zfs.92754/post-647819) which offers a solution using a ramdisk, but this isn't feasible considering the existing dump is larger than the available physical memory on the device. As it's a VPS, the approach of using two physical drives is unfortunately also out the window.
 
Huh, am I correctly seeing that the dump isn't storing any info on existing symlinks? Neither dump(8) nor restore(8) even mention them. That might be an issue, depending on how much existing packages depend on them.
Guess I'll have to generate a list of packages and then do an interactive restore. Minimize any potential breakage to my user folders and deal with any problems from there. Thanks for the pointer!
 
Use interactive restore to inspect the content. Dump store everything including symlinks
 
If FreeBSD dump/restore works the same way as Solaris ufsdump/ufsrestore, then

Is there any way I can inspect the blob it outputs? I'd like to verify what's in there and what would be restored at a later time before wiping the current server.

You can browse the dump contents, using restore -if.

Huh, am I correctly seeing that the dump isn't storing any info on existing symlinks? Neither dump(8) nor restore(8) even mention them.

Yes, it should preserve symbolic links.
 
Guess I'll dryrun in a VM or virtual filesystem first, just to see what I'm actually getting. This is interesting stuff, thanks.

Any advice on having
restore unpack in places other than the drive's root? Would a chroot env work for the purposes of testing what it dumps?
 
Back
Top