Re: Best practice preparing for disk restoring system

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]



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/deleteme; rm /path/deleteme) or use 'fstrim' for SSD's, you could use dd to image with fast & light compression (lzop or my current favorite, pzstd) and get maximum benefit of a bit-by-bit archival copy.


On 11/16/20 11:02 PM, H wrote:
> 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
> - grub
> - fstab
>
> Hoping that this would supply me with /all/ information to restore a system - with the exception of installed operating system, apps and data.
>
> I would appreciate any and all thoughts on the above!
> _______________________________________________
> CentOS mailing list
> CentOS@xxxxxxxxxx
> https://lists.centos.org/mailman/listinfo/centos

_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
https://lists.centos.org/mailman/listinfo/centos




[Index of Archives]     [CentOS]     [CentOS Announce]     [CentOS Development]     [CentOS ARM Devel]     [CentOS Docs]     [CentOS Virtualization]     [Carrier Grade Linux]     [Linux Media]     [Asterisk]     [DCCP]     [Netdev]     [Xorg]     [Linux USB]


  Powered by Linux