search for: __much__

...e commands are there then its trivial to restore data. What I've done in the past is before the nightly backup write a small file to the root of each filesystem giving disk geometries. You can then use any recovery DVD to partition and reload the OS. If rear can do this for me it would be __much__ neater! On 18/11/2020 08:24, John Pierce wrote: > I'm old school, but I always liked using dump/restore on unix file > systems. e2dump or whatever for linux, zfs send/recieve for zfs, ufsdump > on freebsd ufs, etc etc. > > then I just need to know what file systems they are, a...

> What I've done in the past is before the nightly backup write a small > file to the root of each filesystem giving disk geometries.? You can > then use any recovery DVD to partition and reload the OS.? If rear can > do this for me it would be __much__ neater! According to rear webpage: https://relax-and-recover.org/about/ Extensive disk layout implementation, incl. * HWRAID (HP SmartArray) * SWRAID * LVM * multipathing * DRBD * iSCSI * LUKS (encrypted partitions and filesystems) I personally used rear to restore lvm volume group...

On 18/11/2020 03:35, H wrote: > On November 17, 2020 4:07:52 PM EST, "Felix K?lzow" <felix.koelzow at gmx.de> wrote: >> Maybe "rear" is an appropriate solution for you? >> >> https://relax-and-recover.org/ >> >> On 17/11/2020 18:23, Chris Schanzle via CentOS wrote: >>> I would include LVM and mdadm info as well, since I use those

On 04/11/2017 07:50 AM, Andrew Holway wrote: >> I'd much rather have a bash script to look at-- and manually step through. > > Is that a joke? Bash is an almighty impenetrable nightmare. I've been doing > *nix for nearly 10 years and *still* am unable to read anything vaguely > complicated in bash whereas I can write fairly decent python after 6 > months. From my