Changeset 1236 in MondoRescue for branches/2.2.2/mondo-doc/mondorescue-howto.sgml
- Timestamp:
- Mar 12, 2007, 12:23:16 AM (17 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
branches/2.2.2/mondo-doc/mondorescue-howto.sgml
r978 r1236 75 75 </link>.</para> 76 76 <para> 77 or any later version published by the Free Software Foundation; with no Invarian 78 t Sections, Front-Cover Texts or Back-Cover Texts. This document is distributed 79 hoping it will be useful, but <emphasis>without any guaranty</emphasis>; you're 80 completely responsible of its use, and coulnd't complain in case it doesn't work 81 , or even if it breaks the hardware. All the software included in it, if not alr 82 eady copyrighted is released under the GPL. 77 or any later version published by the Free Software Foundation; with no Invariant Sections, Front-Cover Texts or Back-Cover Texts. This document is distributed hoping it will be useful, but <emphasis>without any guaranty</emphasis>; you're completely responsible of its use, and coulnd't complain in case it doesn't work, or even if it breaks the hardware. All the software included in it, if not already copyrighted is released under the GPL. 83 78 </para> 84 79 </legalnotice> … … 173 168 e-mail! Thank you. Without it we can't offer 174 169 any tangible help because you aren't either. That's what the log 175 file is for. It is located at <filename>/var/log/mondo-archive.log</filename>; and <filename>/var/log/mi indi.log</filename> or at <filename>/var/log/mondo-restore.log</filename>176 </para> 177 <para> 178 This document was originaly written by native english speakers, but is maintained by a non-native english speaker so help me correct mistaques instead of rumbling that I've done one :-)170 file is for. It is located at <filename>/var/log/mondo-archive.log</filename>; and <filename>/var/log/mindi.log</filename> or at <filename>/var/log/mondo-restore.log</filename> 171 </para> 172 <para> 173 This document was originaly written by native english speakers, but is maintained by a non-native english speaker so help me correct mistaques (sic) instead of rumbling that I've done one :-) 179 174 </para> 180 175 <para> … … 711 706 boot-time. Mondo uses fdisk, mkfs, cat, less, more, afio, gzip, 712 707 bzip2, your keyboard configuration, your glibc libraries, your 713 other libraries, your kernel, your modules, ... a lot! Mindi takes714 care of all that, so that Mondo can get on with the job of backing708 other libraries, your kernel, your modules, ... which is a lot of tools! 709 Mindi takes care of all that, so that Mondo can get on with the job of backing 715 710 up or restoring your data. 716 711 </para> … … 738 733 drives. That works for most drives but some drives just don't like 739 734 that.</para> 740 <para>Mondo Rescue has tested thousands of times on various computers.741 It worked for them.735 <para>Mondo Rescue has been tested thousands of times on various computers. 736 It has worked for them. 742 737 Thousands of users testify to Mondo's stability and its ease of 743 738 use. However, please test it on your own system before you rely on … … 858 853 Since November 2005, Hugo Rabson has tranfered the maintenance 859 854 of the Mondo Rescue suite to Andree Leidenfrost and Bruno Cornec, 860 both previous develop pers and packagers of the tool since nearly855 both previous developers and packagers of the tool since nearly 861 856 the begining. 862 857 </para> … … 948 943 <para>See Mondo's <ulink url="http://www.mondorescue.org/downloads.shtml">Download 949 944 page</ulink> for details.</para> 950 <para>Mondo requires afio, bzip2, cdrtools/cdrecord/growisofs , ncurses, newt,945 <para>Mondo requires afio, bzip2, cdrtools/cdrecord/growisofs (may be part of the dvd+rw-tools package), ncurses, newt, 951 946 isolinux/syslinux, lzo (optional), lzop (optional), mkisofs, slang, 952 947 and a few other packages.</para> … … 1029 1024 </sect1> 1030 1025 1026 <sect1 id="installation-mindi-busybox"> 1027 <title>Mindi Busybox Installation</title> 1028 <para>If you are installing from a tarball then copy it to wherever 1029 you have enough space, for example /tmp and type:</para> 1030 <para></para> 1031 <informaltable><tgroup cols="1"><tbody> 1032 <row> 1033 <entry> 1034 1035 bash# cd /tmp 1036 </entry> 1037 </row> 1038 <row> 1039 <entry> 1040 bash# tar -zxvf mindi-busybox-1.x.tgz 1041 </entry> 1042 </row> 1043 <row> 1044 <entry> 1045 bash# cd mindi-busybox-1.x 1046 </entry> 1047 </row> 1048 <row> 1049 <entry> 1050 bash# make oldconfig 1051 </entry> 1052 </row> 1053 <row> 1054 <entry> 1055 bash# make busybox 1056 </entry> 1057 </row> 1058 <row> 1059 <entry> 1060 bash# make install 1061 </entry> 1062 </row> 1063 </tbody></tgroup></informaltable> 1064 <para>This installs busybox files and symlinks into /usr/local/lib/mindi/rootfs 1065 </para> 1066 <para>Or, if you are installing from an RPM/deb then copy it to 1067 wherever you have enough space, for example /tmp and type:</para> 1068 <para></para> 1069 <informaltable><tgroup cols="1"><tbody> 1070 <row> 1071 <entry> 1072 1073 bash# rpm -Uvh /tmp/mindi-busybox-1.x-x.i386.rpm 1074 </entry> 1075 </row> 1076 <row> 1077 <entry> 1078 1079 or 1080 </entry> 1081 </row> 1082 <row> 1083 <entry> 1084 1085 bash# dpkg -i /tmp/mindi-busybox-1.x-x.deb 1086 1087 </entry> 1088 </row> 1089 </tbody></tgroup></informaltable> 1090 1091 <para>This installs busybix files and symlinks into /usr/lib/mindi/rootfs 1092 </para> 1093 </sect1> 1094 1031 1095 <sect1 id="installation-mondo"> 1032 1096 <title>Mondo Installation</title> … … 1094 1158 <para>This installs mondo into /usr/lib/mondo and installs 1095 1159 the programs into /usr/sbin</para> 1160 </sect1> 1161 1162 <sect1 id=rpm-verif> 1163 <title>RPM verifications</title> 1164 <para>For RPM based distributions (Fedora, OpenSuSE, Mandriva, ...), you may want to do this post-install in order to check the validity of your installation:</para> 1165 <informaltable><tgroup cols="1"><tbody> 1166 <row> 1167 <entry> 1168 bash# rpm -Va mindi mondo mindi-busybox 1169 </entry> 1170 </row> 1171 </tbody></tgroup></informaltable> 1172 <para> 1173 This gives some truly obtuse output. Basically it will list all files that do NOT pass the verify tests (done on size, MD5 signature, etc). Please read rpm man page to discover the meaning of the output. 1174 </para> 1096 1175 </sect1> 1097 1176 </chapter> … … 1269 1348 1270 1349 <sect1 id="backup-recommandations"> 1271 <title>Recomm andations</title>1350 <title>Recommendations</title> 1272 1351 <itemizedlist> 1273 1352 <listitem> … … 1275 1354 compare differences following the backup). Especially shutdown 1276 1355 properly any running database on your system, as the recovery 1277 may lead to corrupted data. </para>1356 may lead to corrupted data. Or if applicable, boot to single user mode.</para> 1278 1357 </listitem> 1279 1358 <listitem> … … 1488 1567 has been done. The problem lies in the fact that cron does not allow 1489 1568 user interaction with a job. If you schedule a mondoarchive job via 1490 cron, you better be sure it needs only one media. in practical terms,1569 cron, you better be sure it needs only one media. In practical terms, 1491 1570 this means using tapes or ISOs (if CD-R(W) is your backup medium). 1492 1571 However, for tape users, there's always the possibility that the … … 1515 1594 If your backup already occupies two media, this method will allow 1516 1595 as much of the backup as possible to proceed during quiet periods. 1517 Time the backup to start wi ch enough time to complete the first media1596 Time the backup to start with enough time to complete the first media 1518 1597 shortly before the operator arrives for work. The next media can 1519 1598 be mounted and the backup completed asap and minimises the time for … … 1540 1619 of interacting via a FIFO or some such) except termination via its 1541 1620 pid. The only program that I know of that allows such interaction 1542 and serves as a wrapper for other pr rocesses is 'screen'1621 and serves as a wrapper for other processes is 'screen' 1543 1622 </para> 1544 1623 </sect2> … … 1548 1627 attach to a terminal when it first starts. This won't happen under 1549 1628 cron so screen will fail. Fortunately, screen comes with a "start 1550 detached" option.1629 detached" (-d) option. 1551 1630 </para> 1552 1631 </sect2> … … 1845 1924 <listitem><para>Wipe your drives and restore everything, 1846 1925 automatically and unattended. Warning: This does exactly what is 1847 says, so be careful lusing it.</para>1926 says, so be careful using it.</para> 1848 1927 </listitem></varlistentry> 1849 1928 <varlistentry><term>Expert</term> … … 2375 2454 </tbody></tgroup></informaltable> 2376 2455 2377 <para>I hope this manual is proving to be useful toyou.</para>2456 <para>I hope this manual was useful for you.</para> 2378 2457 </sect2> 2379 2458 </sect1> … … 2396 2475 <itemizedlist> 2397 2476 <listitem> 2398 <para>Your kernel version </para>2399 </listitem> 2400 <listitem> 2401 <para>Your Linux distro's name and version</para>2402 </listitem> 2403 <listitem> 2404 <para>Whether your kernel supports initrd and loopfs; it should!</para>2405 </listitem> 2406 <listitem> 2407 <para>What sort of PC you are using, including hard disk configurations </para>2477 <para>Your kernel version (uname -a)</para> 2478 </listitem> 2479 <listitem> 2480 <para>Your Linux distro's name and version (/etc/distro-release)</para> 2481 </listitem> 2482 <listitem> 2483 <para>Whether your kernel supports initrd and loopfs; it should! (grep -E '^CONFIG_BLK_DEV_LOOP|^CONFIG_BLK_DEV_INITRD' /usr/src/linux/.config </para> 2484 </listitem> 2485 <listitem> 2486 <para>What sort of PC you are using, including hard disk configurations (results of dmidecode, lshw, fdisk -l are useful here)</para> 2408 2487 </listitem> 2409 2488 </itemizedlist> … … 2430 2509 'mondo'. Hugo Rabson wasn't sure what to call this project. 'Faust' was one 2431 2510 idea he had, partly as a dig at his former boss who practically owned 2432 him because of his legal status at the time. In the end, He chose2511 him because of his legal status at the time. In the end, he chose 2433 2512 something short and distinctive.</para> 2434 2513 </answer> … … 2438 2517 keels over and dies. What's wrong?</para></question> 2439 2518 <answer> 2440 <para>A: It works on Red Hat 7.x/8/9, RHEL 2.1/3/4, Mandrakelinux 8.x/9.x/10.x , Debian 3.0, most flavors2519 <para>A: It works on Red Hat 7.x/8/9, RHEL 2.1/3/4, Mandrakelinux 8.x/9.x/10.x/200x, Fedora 4/5/6, Debian 3.x, most flavors 2441 2520 of SuSE/SLES, some flavors of Slackware, etc. 2442 2521 The more distributions we support, the more moving targets we have to … … 2457 2536 <para>A: Please send a copy of <filename>/var/log/mindi.log</filename> to the &ML; 2458 2537 along with a description of your distro, your kernel, etc. 2459 Oh, and before sending it, please read it as it's much easier to understand it.</para>2538 Oh, and before sending it, please read it as it is much easier to understand it.</para> 2460 2539 </answer> 2461 2540 </qandaentry> … … 2498 2577 please?</para></question> 2499 2578 <answer> 2500 <para>A: please enter the suggestion in our feature system at &WWW;2579 <para>A: Please enter the suggestion in our feature system at &WWW; 2501 2580 </para> 2502 2581 </answer> … … 2635 2714 <para>A: Recompile your kernel (or use '-k FAILSAFE'). Take a look 2636 2715 at <link linkend="overview-sysrq-kernelreq">Linux Kernel support</link> to 2637 see what you 'rekernel must support.</para>2716 see what your kernel must support.</para> 2638 2717 </answer> 2639 2718 </qandaentry> … … 2644 2723 <para>A: Recompile your kernel and add Virtual memory file system 2645 2724 support. Take a look at <link linkend="overview-sysrq-kernelreq">Linux 2646 Kernel support</link> to see what you 'rekernel must support. (Of2725 Kernel support</link> to see what your kernel must support. (Of 2647 2726 course, if your PC has less than 64MB of RAM, you could always... 2648 2727 what's the phrase? I know, upgrade your RAM!)</para> … … 2656 2735 <para>A: Your kernel must support initrd, loopfs, IDE|SCSI|USB CD-ROM's, and 2657 2736 ramdisks. Take a look at <link linkend="overview-sysrq-kernelreq">Linux 2658 Kernel support</link> to see what you 'rekernel must support. If2737 Kernel support</link> to see what your kernel must support. If 2659 2738 your kernel does not support these things, Mondo will not boot from 2660 2739 your CD. However, when running Mindi, you may choose to use _its_ … … 2714 2793 kernel and/or recompile it. Take a look at 2715 2794 <link linkend="overview-sysrq-kernelreq">Linux Kernel support</link> to see 2716 what you 'rekernel must support.</para>2795 what your kernel must support.</para> 2717 2796 </answer> 2718 2797 </qandaentry> … … 2751 2830 <answer> 2752 2831 <para>A: Recompile your kernel and add initrd support. Take a look 2753 at <link linkend="overview-sysrq-kernelreq">Linux Kernel support</link> to2754 see what you 'rekernel must support.</para>2832 at <link linkend="overview-sysrq-kernelreq">Linux Kernel support</link> to 2833 see what your kernel must support.</para> 2755 2834 </answer> 2756 2835 </qandaentry> … … 2808 2887 <question><para id="TAPENICE">Q: My tape drive 2809 2888 doesn't play nicely with Mondo at boot-time. What do I do?</para></question> 2810 <answer><para>A: Play with 'mt'. Use its setblksize and2889 <answer><para>A: Play with the 'mt' command (package mt-st). Use its setblksize and 2811 2890 defblksize switches to reconfigure your tape drive if necessary. 2812 2891 Some tape drives just are painful. If yours is one of … … 2887 2966 drives?</para></question> 2888 2967 <answer> 2889 <para>A: Yes. See above.</para> 2968 <para>A: Yes. See above.</para> 2969 <para>Of course, mondo will relay on the kernel to support your tape drive. So you should first check that your kernel found it correctly. Use for example one of the following commands:</para> 2970 <informaltable><tgroup cols="1"><tbody> 2971 <row> 2972 <entry> 2973 bash# dmesg | grep tape 2974 </entry> 2975 </row> 2976 <row> 2977 <entry> 2978 bash# cat /proc/scsi/scsi 2979 </entry> 2980 </row> 2981 <row> 2982 <entry> 2983 bash# mt -f /dev/st0 status 2984 </entry> 2985 </row> 2986 </tbody></tgroup></informaltable> 2987 2988 2890 2989 </answer> 2891 2990 </qandaentry> … … 2960 3059 partitions and their settings. Mondo will do the partitioning and 2961 3060 formatting for you.</para> 2962 <para>Tested Raid controllers includes all those showin donly classical devices3061 <para>Tested Raid controllers includes all those showing only classical devices 2963 3062 such as /dev/sdx, and SmartArray cciss controllers.</para> 2964 3063 </answer> … … 2971 3070 <informaltable><tgroup cols="1"><tbody> 2972 3071 <row> 2973 <entry> 2974 2975 bash# cdrecord -scanbus 2976 2977 </entry> 2978 </row> 2979 </tbody></tgroup></informaltable> 3072 <entry> 3073 bash# cdrecord -scanbus 3074 </entry> 3075 </row> 3076 </tbody></tgroup></informaltable> 3077 <para>or for ATAPI type of devices:</para> 3078 <para></para> 3079 <informaltable><tgroup cols="1"><tbody> 3080 <row> 3081 <entry> 3082 bash# cdrecord -scanbus dev=ATAPI 3083 </entry> 3084 </row> 3085 </tbody></tgroup></informaltable> 3086 <para>you may replace ATAPI by ATA in the previous line with certain cdrecord versions and hadrware configurations</para> 3087 2980 3088 2981 3089 <para>Find your CD burner's device# (e.g. '0,0,0'). Call Mondo with … … 3209 3317 <qandaentry> 3210 3318 <question> 3211 <para id="LVM" />Q: I can't nuke-restore my LVM or RAID or3319 <para id="LVM">Q: I can't nuke-restore my LVM or RAID or 3212 3320 LVM-on-RAID setup. I have to do it manually. What now?</para></question> 3213 3321 <answer>
Note:
See TracChangeset
for help on using the changeset viewer.