Re: [CentOS] Best practice preparing for disk restoring system

2020-11-18 Thread Valeri Galtsev
> On Nov 18, 2020, at 3:27 AM, J Martin Rushton via CentOS > wrote: > > I'd agree with you John. I'm trying to get away from Amanda's > unpredictability and go back to using scripts to drive dump (for ext2/3/4) > and xfsdump (for xfs). > There is enterprise class open source backup softw

Re: [CentOS] Best practice preparing for disk restoring system

2020-11-18 Thread J Martin Rushton via CentOS
Thanks for that. I only picked up on rear this morning, I suppose if you don't go looking for it you'll never find it. A combination of the paper Site Management Guide and the nightly disk summary have worked for over 20 years on *NIX! VMS before that was totally different, but we still kept

Re: [CentOS] Best practice preparing for disk restoring system

2020-11-18 Thread Felix Kölzow
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-an

Re: [CentOS] Best practice preparing for disk restoring system

2020-11-18 Thread J Martin Rushton via CentOS
I'd agree with you John. I'm trying to get away from Amanda's unpredictability and go back to using scripts to drive dump (for ext2/3/4) and xfsdump (for xfs). Is there any easy way to tell rear to include xfsdump and dump capability? If the commands are there then its trivial to restore dat

Re: [CentOS] Best practice preparing for disk restoring system

2020-11-18 Thread John Pierce
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, and where they should be mounted, and its trivial to set tha tup on new hardwar

Re: [CentOS] Best practice preparing for disk restoring system

2020-11-17 Thread Felix Kölzow
On 18/11/2020 03:35, H wrote: On November 17, 2020 4:07:52 PM EST, "Felix Kölzow" 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 feat

Re: [CentOS] Best practice preparing for disk restoring system

2020-11-17 Thread H
On November 17, 2020 4:07:52 PM EST, "Felix Kölzow" 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 >features.  I encourage you to l

Re: [CentOS] Best practice preparing for disk restoring system

2020-11-17 Thread Felix Kölzow
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 features.  I encourage you to look at what long-lived tools, such as clonezilla, write into their

Re: [CentOS] Best practice preparing for disk restoring system

2020-11-17 Thread Chris Schanzle via CentOS
I would include LVM and mdadm info as well, since I use those features.  I encourage you to look at what long-lived tools, such as clonezilla, write into their archive directories.  It's impressive. If you zero out all free space on all of your HDD partitions (dd bs=1M if=/dev/zero of=/path/del

[CentOS] Best practice preparing for disk restoring system

2020-11-16 Thread H
Short of backing up entire disks using dd, I'd like to collect all required information to make sure I can restore partitions, disk information, UUIDs and anything else required in the event of losing a disk. So far I am collecting information from: - fdisk -l - blkid - lsblk - grub2-efi.cfg - g