Here's the full steps for another method, works for moving from one hard drive to another, and even cloning a machine if the hardware is similar.įirst, create an image of a good working system. Rpm -qa -qf "%\n" | sort -k2,2 > /./info_rpms_archĪs well as mounting any "optional" user-mounted filesystems. (Occasionally its nice to see what permissions or links you had set up before.)Īlso, you might want to dump fdisk & rpm info before backing up. Though you probably won't use the backed up /dev during a restore. gnu-tar will handle devices properly ( mknod). (I usually back up to an external drive mounted under /mnt. You should probably exclude /proc, /sys, and perhaps /var/log/lastlog or /mnt. (Something to do with very long pathnames and multiple volumes.) No big deal. (I should mention: I did run into a bug a few years back that required me to download and install a newer version of GNU-tar. But when going from a 500Meg to a 1500Meg drive, I get concerned.īesides, when my drive fails, I like to be able to use it as an excuse to upgrade to a newer OS.Īll that said, good old tar does a nice job! GNU-tar includes diff-tar-against-files, only-update-files-that-have-changed, and only-archive-files-newer-than-date options. Especially USB drives or windows partitions. Or had different numbers of heads/sectors/tracks/etc.ĭd is very useful when snapshotting and reflashing the same drive. I always worried about using dd when the drives were differently sized.
0 kommentar(er)
