![]() This is nice if you are restoring on an identical computer or at least an identical hard drive, but that is often not the case. The scripts here restore the partition data exactly as found on the source hard drive. You still have some research, script editing, and testing to do. This HOWTO does not deal with your regular backups at all.Įven within that narrow brief, this HOWTO is not exhaustive. This HOWTO is restricted to making a minimal backup such that, having then restored that backup to new hardware ( "bare metal"), you can then use your regular backups to restore a completely working system. ![]() After you have done that last stage, you should be able to boot to a fully restored and operational system. The last stage is a total restoration from tape or other media. If you use tar, gzip, cpio, mt or dd for your backup and recovery tools, they will be saved to and restored from our ZIP disk as part of the stage one process describe below. You will have to find out the directories and files it needs to run. Of course, if you are using some other backup program, you may have some detective work to do to. Instead, why not tar and gzip the whole arkeia directory (at /usr/knox), and save that to another computer over nfs or ssh? Stage one, as we have defined it below, does not include X, so you will have some experimenting to do if you wish to back up X as well as your backup program. You can recover the database from the tapes, if you want. Arkeia keeps a huge database on the server's hard drives. For example, suppose you use Arkeia and you are building a bare metal recovery ZIP disk for your backup server. The second stage, if it is necessary, consists of restoring backup software and any relevant databases. The goal of stage one is to be able to boot to a running computer with a network connection, tape drives, restoration software, or whatever we need for stage two. and restore a minimum of files from the ZIP disk. In stage one, we build partitions, file systems, etc. So only back up networking in your regular backups. For example, if you are restoring a tape server, you may not need networking during the restoration process. Exactly what you back up and in which stage you back it up is determined by your restoration process. To get there, you need at least two stages of backup, and possibly three. A modern Linux installation with several kernels installed may run to over 100 MB.Ī minimal Linux system that will allow you to run the restoration software, which we will call the restoration Linux. At the moment, there is no provision for using a different hard drive.Ī parallel port Iomega® ZIP® drive or equivalent. The BIOS should be correctly configured, including time and date, and hard drive parameters. Your hardware up and running again, with replacement components as needed. It provides a basis for comparison after a bare metal restoration. ![]() The following is in one of the scripts in this HOWTO: bash# rpm -Va | sort +2 -t ' ' | uniq > /etc/rpmVa.txt Users of Red Hat Package Manager (RPM) based Linux distributions should also save RPM metadata as part of their normal backups. The question, then, is how to get from toasted hardware to the point where you can run the restoration tool that will restore your data. ![]() For example, exactly which files do you back up? What metadata should you preserve, and how? This document explores those questions.īefore beginning the process set forth in this HOWTO you will need to back up your system with a typical backup tool such as Amanda, BRU™, tar, Arkeia® or cpio. However, the book is a bit thin on specific, real-time questions. Curtis Preston, Unix Backup & Recovery, O'Reilly & Associates, 1999, which I have favorably reviewed in Linux Journal. It is up to you to be sure you duplicate your setup, and not the test computer's setup. You may have to use similar commands, but with different parameters. The sample commands will show, in most cases, what I had to type to recover the target system. How to use this License for your documents We now use bz2 compression in the first stage, have the run time option to check for bad blocks, and have a script that runs the entire first stage. New code to handle ext3 partitions in make.fdisk, and a note on initrd. ![]() Substituted new email address and URL for old.Īdded Red Hat 8.0 notes, support for FAT32, split the first stage restore scripts, and other minor changes. Some notes on burning CD-ROMs, and more on files to exclude. Changed some scripts so that long lines don't fall off the right side of printed pages (oops).Īdded Knoppix notes, Syslinux, PPART, QtParted, some other rescue CDs, and made some fixes. Also, changes in the writeup and scripts to reflect using Knoppix instead of tomsrtbt. Removed notes for older versions of FC and Red Hat. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |