<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<HTML
><HEAD
><TITLE
>MondoRescue HOWTO</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><META
HTTP-EQUIV="Content-Type"
CONTENT="text/html; charset=iso-8859-1"><META
NAME="Author"
CONTENT="Bruno Cornec"><META
NAME="KeyWords"
CONTENT="Linux,Disaster Recovery, Mondo, Mindi, MondoRescue"></HEAD
><BODY
CLASS="BOOK"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="BOOK"
><A
NAME="AEN1"
></A
><DIV
CLASS="TITLEPAGE"
><H1
CLASS="TITLE"
><A
NAME="AEN2"
>MondoRescue HOWTO</A
></H1
><H2
CLASS="SUBTITLE"
>Utilisation and Configuration of Mondo and Mindi under Linux (Version 2.2.9.3-r2622)</H2
><IMG
ALIGN="CENTER"
SRC="images/protected-by-mondo.png"
ALT=""><H3
CLASS="AUTHOR"
><A
NAME="AEN9"
></A
>Bruno Cornec</H3
><DIV
CLASS="AFFILIATION"
><SPAN
CLASS="ORGNAME"
>MondoRescue Project<BR></SPAN
><DIV
CLASS="ADDRESS"
><P
CLASS="ADDRESS"
><CODE
CLASS="EMAIL"
><<A
HREF="mailto:bruno@mondorescue.org"
>bruno@mondorescue.org</A
>></CODE
></P
></DIV
></DIV
><H3
CLASS="AUTHOR"
><A
NAME="AEN16"
></A
>Conor Daly</H3
><DIV
CLASS="AFFILIATION"
><SPAN
CLASS="ORGNAME"
>MondoRescue Project<BR></SPAN
><DIV
CLASS="ADDRESS"
><P
CLASS="ADDRESS"
><CODE
CLASS="EMAIL"
><<A
HREF="mailto:conor.daly_at_met.ie"
>conor.daly_at_met.ie</A
>></CODE
></P
></DIV
></DIV
><P
CLASS="COPYRIGHT"
>Copyright © 2000-2006 Bruno Cornec</P
><DIV
><DIV
CLASS="ABSTRACT"
><P
></P
><A
NAME="AEN7"
></A
><P
>This document describes the use of mondo and mindi tools to realize disaster recovery backup of your systems. It provides information on installation, backup and restore modes, hardware and software requirements, and answers to some frequently asked questions.
The goals are to offer a general view of the functions and their best usages.
Mondo Rescue is a Disaster Recovery Solution which allows you
to effortlessly backup and interactively restore Linux, Windows and
other supported filesystem partitions to/from CD/DVD-+R/RW media, tape,
NFS, ... and Mindi Linux provides the bootable emergency restore
media which Mondo uses at boot-time.</P
><P
></P
></DIV
></DIV
><DIV
CLASS="LEGALNOTICE"
><A
NAME="AEN26"
></A
><P
><B
>License</B
></P
><P
></P
><P
>This HOWTO is a free documentation. you may copy, redistribute and/or modify it under the terms of the
<A
HREF="#GFDL"
>GNU Free Documentation License, Version 1.1</A
>.</P
><P
>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 <EM
>without any guaranty</EM
>; 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.</P
></DIV
><HR></DIV
><DIV
CLASS="TOC"
><DL
><DT
><B
>Table of Contents</B
></DT
><DT
>1. <A
HREF="#INTRO"
>About this Guide</A
></DT
><DD
><DL
><DT
>1.1. <A
HREF="#INTRO-PURPOSE"
>Purpose / Scope of this Guide</A
></DT
><DT
>1.2. <A
HREF="#INTRO-NEWVERSION"
>New versions of this document</A
></DT
><DT
>1.3. <A
HREF="#AEN61"
>Suggestions / Feedback</A
></DT
><DT
>1.4. <A
HREF="#INTRO-THANKS"
>Aknowledgements</A
></DT
></DL
></DD
><DT
>2. <A
HREF="#QUICKSTART"
>QuickStart</A
></DT
><DT
>3. <A
HREF="#OVERVIEW"
>Overview</A
></DT
><DD
><DL
><DT
>3.1. <A
HREF="#OVERVIEW-MONDORESCUE"
>Mondo Rescue</A
></DT
><DT
>3.2. <A
HREF="#OVERVIEW-MINDI"
>Mindi</A
></DT
><DT
>3.3. <A
HREF="#OVERVIEW-LINUXBACKUP"
>Linux Backup</A
></DT
><DT
>3.4. <A
HREF="#OVERVIEW-WINBACKUP"
>Windows Backup</A
></DT
><DD
><DL
><DT
>3.4.1. <A
HREF="#OVERVIEW-WINBACKUP-WIN95"
>Windows ME/95/98</A
></DT
><DT
>3.4.2. <A
HREF="#OVERVIEW-WINBACKUP-WINNT"
>Windows NT4/2K/XP</A
></DT
></DL
></DD
><DT
>3.5. <A
HREF="#OVERVIEW-HISTORY"
>Mondo Rescue and Mindi Linux
History</A
></DT
><DT
>3.6. <A
HREF="#OVERVIEW-SYSREQ"
>System Requirements</A
></DT
><DD
><DL
><DT
>3.6.1. <A
HREF="#OVERVIEW-SYSRQ-HWREQ"
>Hardware Requirements</A
></DT
><DT
>3.6.2. <A
HREF="#OVERVIEW-SYSRQ-KERNELREQ"
>Kernel Requirements</A
></DT
><DT
>3.6.3. <A
HREF="#OVERVIEW-SYSRQ-SWREQ"
>Software Requirements</A
></DT
></DL
></DD
></DL
></DD
><DT
>4. <A
HREF="#INSTALLATION"
>Installation</A
></DT
><DD
><DL
><DT
>4.1. <A
HREF="#INSTALLATION-MINDI"
>Mindi Installation</A
></DT
><DT
>4.2. <A
HREF="#INSTALLATION-MINDI-BUSYBOX"
>Mindi Busybox Installation</A
></DT
><DT
>4.3. <A
HREF="#INSTALLATION-MONDO"
>Mondo Installation</A
></DT
><DT
>4.4. <A
HREF="#RPM-VERIF"
>RPM verifications</A
></DT
></DL
></DD
><DT
>5. <A
HREF="#TEST"
>Tests</A
></DT
><DD
><DL
><DT
>5.1. <A
HREF="#TEST-MINDI"
>Testing Mindi</A
></DT
></DL
></DD
><DT
>6. <A
HREF="#BACKUP"
>Backup</A
></DT
><DD
><DL
><DT
>6.1. <A
HREF="#BACKUP-RECOMMANDATIONS"
>Recommendations</A
></DT
><DT
>6.2. <A
HREF="#BACKUP-CMD"
>Backup Commands and Options</A
></DT
><DD
><DL
><DT
>6.2.1. <A
HREF="#BACKUP-CMD-CDR"
>Standard Example With CD-R</A
></DT
><DT
>6.2.2. <A
HREF="#BACKUP-CMD-CDRW"
>Standard Example With CD-RW</A
></DT
><DT
>6.2.3. <A
HREF="#BACKUP-CMD-TAPE"
>Standard Example With Tape</A
></DT
><DT
>6.2.4. <A
HREF="#BACKUP-CMD-FAILSAFE"
>Standard Example With Failsafe kernel</A
></DT
><DT
>6.2.5. <A
HREF="#BACKUP-CMD-NETWORK"
>Standard Example With Network Backup</A
></DT
></DL
></DD
></DL
></DD
><DT
>7. <A
HREF="#BACKUP-CRON"
>HOWTO run mondo interactively using cron</A
></DT
><DD
><DL
><DT
>7.1. <A
HREF="#BACKUP-CRON-OVERVIEW"
>Overview</A
></DT
><DT
>7.2. <A
HREF="#BACKUP-CRON-INTRO"
>Introduction</A
></DT
><DT
>7.3. <A
HREF="#BACKUP-CRON-WHO"
>Who should read this?</A
></DT
><DD
><DL
><DT
>7.3.1. <A
HREF="#AEN683"
>Insurance</A
></DT
><DT
>7.3.2. <A
HREF="#AEN686"
>Efficiency</A
></DT
></DL
></DD
><DT
>7.4. <A
HREF="#BACKUP-CRON-PROBLEM"
>The Problem</A
></DT
><DD
><DL
><DT
>7.4.1. <A
HREF="#AEN691"
>Cron's environment</A
></DT
><DT
>7.4.2. <A
HREF="#AEN694"
>Interactivity</A
></DT
><DT
>7.4.3. <A
HREF="#AEN697"
>Screen</A
></DT
></DL
></DD
><DT
>7.5. <A
HREF="#BACKUP-CRON-SOLUTION"
>The Solution</A
></DT
><DD
><DL
><DT
>7.5.1. <A
HREF="#AEN702"
>Briefly</A
></DT
><DT
>7.5.2. <A
HREF="#AEN718"
>In Detail</A
></DT
></DL
></DD
></DL
></DD
><DT
>8. <A
HREF="#COMPARE"
>Compare</A
></DT
><DT
>9. <A
HREF="#RESTORE"
>Restore</A
></DT
><DD
><DL
><DT
>9.1. <A
HREF="#RESTORE-OVERVIEW"
>Overview</A
></DT
><DT
>9.2. <A
HREF="#RESTORE-TIPS"
>Tips and Tricks</A
></DT
><DD
><DL
><DT
>9.2.1. <A
HREF="#AEN872"
>Barebones (Nuke) Restore</A
></DT
><DT
>9.2.2. <A
HREF="#AEN890"
>Interactive Restore</A
></DT
><DT
>9.2.3. <A
HREF="#AEN928"
>Expert Restore</A
></DT
><DT
>9.2.4. <A
HREF="#AEN951"
>Modified partitions - Restore to a different disk geometry</A
></DT
><DT
>9.2.5. <A
HREF="#AEN1023"
>Advanced</A
></DT
></DL
></DD
></DL
></DD
><DT
>10. <A
HREF="#FAQ"
>FAQ</A
></DT
><DD
><DL
><DT
>10.1. <A
HREF="#FAQ-OVERVIEW"
>Overview</A
></DT
><DT
>10.2. <A
HREF="#FAQ-GENERAL"
>General Questions</A
></DT
><DT
>10.3. <A
HREF="#FAQ-BOOTING"
>Booting and Kernel related Questions</A
></DT
><DT
>10.4. <A
HREF="#FAQ-INSTALL"
>Installation related Questions</A
></DT
><DT
>10.5. <A
HREF="#FAQ-HARDWARE"
>Hardware related Questions</A
></DT
><DT
>10.6. <A
HREF="#FAQ-BACKUP"
>Backup related Questions</A
></DT
><DT
>10.7. <A
HREF="#FAQ-COMPARE"
>Compare related Questions</A
></DT
><DT
>10.8. <A
HREF="#FAQ-RESTORE"
>Restore related Questions</A
></DT
></DL
></DD
><DT
>A. <A
HREF="#GFDL"
>GNU Free Documentation License</A
></DT
><DD
><DL
><DT
>0. <A
HREF="#FDL-PREAMBLE"
>PREAMBLE</A
></DT
><DT
>1. <A
HREF="#FDL-DEF"
>APPLICABILITY AND DEFINITIONS</A
></DT
><DT
>2. <A
HREF="#FDL-VERBATIMCP"
>VERBATIM COPYING</A
></DT
><DT
>3. <A
HREF="#FDL-QUANTITYCP"
>COPYING IN QUANTITY</A
></DT
><DT
>4. <A
HREF="#FDL-MODIF"
>MODIFICATIONS</A
></DT
><DT
>5. <A
HREF="#FDL-COMBINING"
>COMBINING DOCUMENTS</A
></DT
><DT
>6. <A
HREF="#FDL-COLLECTION"
>COLLECTIONS OF DOCUMENTS</A
></DT
><DT
>7. <A
HREF="#FDL-AGGREGATION"
>AGGREGATION WITH INDEPENDENT WORKS</A
></DT
><DT
>8. <A
HREF="#FDL-TRANSLATION"
>TRANSLATION</A
></DT
><DT
>9. <A
HREF="#FDL-TERM"
>TERMINATION</A
></DT
><DT
>10. <A
HREF="#FDL-FUTUREREV"
>FUTURE REVISIONS OF THIS LICENSE</A
></DT
><DT
><A
HREF="#FDL-HOWTO"
>How to use this License for your documents</A
></DT
></DL
></DD
></DL
></DIV
><DIV
CLASS="CHAPTER"
><HR><H1
><A
NAME="INTRO"
></A
>Chapter 1. About this Guide</H1
><DIV
CLASS="SECT1"
><H2
CLASS="SECT1"
><A
NAME="INTRO-PURPOSE"
>1.1. Purpose / Scope of this Guide</A
></H2
><P
>This HOWTO serves to help people get started with using
mondo/mindi as way to backup/restore their system. This is a work
constantly evolving. It was started by Hugo Rabson and has
since been worked upon by a number of people. See the
'<A
HREF="http://www.mondorescue.org/about.shtml#devteam"
TARGET="_top"
>About</A
>' web
page for a list of members of the development team.</P
><P
>There are many ways to contribute to the Linux movement
without actually writing code. One of the most important is writing
documentation, allowing each person to share their knowledge with
thousands of others around the world. This HOWTO is designed to
help you get familiar with how Mondo/Mindi works.</P
><P
>Opinions expressed here are those of the authors.
Informations are provided in the aim to be useful to the readers.
However, there can't be, through this document, any warranty of any kind
on the way it works on your systems, nor the author could be responsible for any problem caused by the use of these informations.
However, software editors don't garantee you a lot either (re-read the contracts).</P
></DIV
><DIV
CLASS="SECT1"
><HR><H2
CLASS="SECT1"
><A
NAME="INTRO-NEWVERSION"
>1.2. New versions of this document</A
></H2
><P
>The newest version of this document can always be found on
MondoRescue's homepage <A
HREF="http://www.mondorescue.org"
TARGET="_top"
>MondoRescue</A
>.</P
><P
>If you make a translation of this document into another language, please let meknow so that I can include a reference to it here.</P
></DIV
><DIV
CLASS="SECT1"
><HR><H2
CLASS="SECT1"
><A
NAME="AEN61"
>1.3. Suggestions / Feedback</A
></H2
><P
>I rely on you, the reader, to make this HOWTO useful. THis HOWTO is probably incomplete even if it tries to be accurate to the best of our knowledge.
If you have any suggestions, corrections, recommandations or congratulations :-) don't hesitate to send them to me
<CODE
CLASS="EMAIL"
><<A
HREF="mailto:bruno@mondorescue.org"
>bruno@mondorescue.org</A
>></CODE
>,
and I will try to incorporate them in a next revision or to the <A
HREF="http://lists.sourceforge.net/lists/listinfo/mondo-devel"
TARGET="_top"
>mondorescue mailing list</A
>;
e-mail the list at
<A
HREF="mailto:mondo-devel@lists.sourceforge.net"
TARGET="_top"
>mondo-devel@lists.sourceforge.net</A
>;
tell us what is wrong and how it should be fixed.
Include the section title and recommended changes. Whenever possible, include
the exact, spell-checked, grammar-checked text that you think would
improve the document.</P
><P
>See Mondo's
<A
HREF="http://www.mondorescue.org/support.shtml"
TARGET="_top"
>Support</A
> page for
more information.</P
><P
>Please note that we do our best to help everyone but it is
difficult for us to help you if you do not attach a log file to
your e-mail. Let me say that again - attach your log file to your
e-mail! Thank you. Without it we can't offer
any tangible help because you aren't either. That's what the log
file is for. It is located at <TT
CLASS="FILENAME"
>/var/log/mondoarchive.log</TT
>; and <TT
CLASS="FILENAME"
>/var/log/mindi.log</TT
> (if called alone) or at <TT
CLASS="FILENAME"
>/var/log/mondorestore.log</TT
></P
><P
>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 :-)</P
><P
>I am also willing to answer general questions on MondoRescue, the best I can.
Before doing so, please read all of the information in this HOWTO, and then send me detailed information about the problem, especially including the logs generated by the tools, or traces obtained (Did I say that already :-].</P
><P
>If you publish this document on a CD-ROM or in hardcopy form, a complimentary copy would be appreciated; mail me for my postal address. Also consider making a donation to the Linux Documentation Project to help support free documentation for Linux. Contact the Linux HOWTO coordinator,
Guylhem AZNAR <CODE
CLASS="EMAIL"
><<A
HREF="mailto:guylhem@rrremovethis.oeil.qc.ca"
>guylhem@rrremovethis.oeil.qc.ca</A
>></CODE
>.</P
></DIV
><DIV
CLASS="SECT1"
><HR><H2
CLASS="SECT1"
><A
NAME="INTRO-THANKS"
>1.4. Aknowledgements</A
></H2
><P
>Thanks goes to these people for helping and adding to this
HOWTO.</P
><P
>Document maintainer:</P
><P
></P
><UL
COMPACT="COMPACT"
><LI
STYLE="list-style-type: disc"
><P
>Bruno Cornec</P
></LI
></UL
><P
>Original Design Assistance by:</P
><P
></P
><UL
><LI
><P
>Xion Network.com</P
></LI
></UL
><P
>Original Document Assistance by:</P
><P
></P
><UL
><LI
><P
>Cafeole</P
></LI
><LI
><P
>Troff</P
></LI
><LI
><P
>Randy Delfs</P
></LI
><LI
><P
>Mikael Hultgren</P
></LI
></UL
><P
>Original LinuxDoc and LaTeX Reformat by:</P
><P
></P
><UL
><LI
><P
>Bryan J. Smith</P
></LI
></UL
><P
>Original DocBook Reformat by:</P
><P
></P
><UL
><LI
><P
>Mikael Hultgren</P
></LI
></UL
><P
>Original author; 1.6x material:</P
><P
></P
><UL
><LI
><P
>Hugo Rabson</P
></LI
></UL
></DIV
></DIV
><DIV
CLASS="CHAPTER"
><HR><H1
><A
NAME="QUICKSTART"
></A
>Chapter 2. QuickStart</H1
><P
></P
><UL
COMPACT="COMPACT"
><LI
STYLE="list-style-type: disc"
><P
>We recommend that you read this complete
HOWTO. However, if you are too busy or impatient, then
please use this QuickStart guide to stay out of trouble.</P
></LI
><LI
STYLE="list-style-type: disc"
><P
>Install the tarball, RPM, or DEB mindi and mondo
packages. (see <A
HREF="#INSTALLATION"
>Installation</A
>
for more details)</P
></LI
><LI
STYLE="list-style-type: disc"
><P
>Execute as root (type 'su -' to become root if you are not
logged in as root)</P
><P
></P
><DIV
CLASS="INFORMALTABLE"
><P
></P
><A
NAME="AEN121"
></A
><TABLE
BORDER="1"
CLASS="CALSTABLE"
><COL><TBODY
><TR
><TD
> bash# mondoarchive </TD
></TR
></TBODY
></TABLE
><P
></P
></DIV
></LI
></UL
><P
></P
><DIV
CLASS="INFORMALTABLE"
><P
></P
><A
NAME="AEN127"
></A
><TABLE
BORDER="1"
CLASS="CALSTABLE"
><COL><COL><TBODY
><TR
><TD
><A
HREF="images/mamain.png"
TARGET="_top"
><SPAN
CLASS="INLINEMEDIAOBJECT"
><IMG
SRC="images/mamain-mini.png"></SPAN
></A
></TD
><TD
>Choose from the list of supported backup media types. The media you
will use most often are CD/DVD-+R, CD/DVD-+RW, tape, NFS and hard disk. If
you want to backup/restore over a network, choose 'NFS'. If you
want to backup/restore to/from a local partition or if you simply
want to store the ISO images in a local directory until you have
time or facilities to burn them to CD's, choose 'hard disk'. If you
choose 'CD/DVD-+R[W]' or 'tape' then in general your hardware will be
detected and configured for you.</TD
></TR
><TR
><TD
><A
HREF="images/maburnproof.png"
TARGET="_top"
><SPAN
CLASS="INLINEMEDIAOBJECT"
><IMG
SRC="images/maburnproof-mini.png"></SPAN
></A
></TD
><TD
> If you are backing up to CD/DVD-+R[W] then Mondo will ask you if your CD
burner has BurnProof technology, is inside a laptop, or is
otherwise eccentric. If you are backing up to a tape streamer then
you will not see this message.</TD
></TR
><TR
><TD
><A
HREF="images/macompression.png"
TARGET="_top"
><SPAN
CLASS="INLINEMEDIAOBJECT"
><IMG
SRC="images/macompression-mini.png"></SPAN
></A
></TD
><TD
>How much compression do you want? None, if your tape streamer has
built-in hardware compression. Maximum, if your CPU is blazingly
fast. Average should do just fine for most situations.</TD
></TR
><TR
><TD
><A
HREF="images/mainclude.png"
TARGET="_top"
><SPAN
CLASS="INLINEMEDIAOBJECT"
><IMG
SRC="images/mainclude-mini.png"></SPAN
></A
></TD
><TD
>If you want to backup the whole computer (excluding /sys and /proc,
naturally) then leave this as / which is the default. Otherwise,
specify subsets, (e.g. /usr/local /home ) being sure to put a space
in between each path.</TD
></TR
><TR
><TD
><A
HREF="images/maexclude.png"
TARGET="_top"
><SPAN
CLASS="INLINEMEDIAOBJECT"
><IMG
SRC="images/maexclude-mini.png"></SPAN
></A
></TD
><TD
>If you are backing up your whole computer then you might want to
exclude certain directories, e.g. /shared/MP3. Please specify them
in the 'exclude directories' dialog box. Please put a space in
between each path, e.g. /shared/private /scratch /nfs /windows</TD
></TR
><TR
><TD
><A
HREF="images/makernel.png"
TARGET="_top"
><SPAN
CLASS="INLINEMEDIAOBJECT"
><IMG
SRC="images/makernel-mini.png"></SPAN
></A
></TD
><TD
>Is your kernel sane? Red Hat, Mandrake, SuSE, Debian and Slackware users
should in general say 'yes' because these vendors are good at
producing reliable kernels. If you are using Gentoo or LFS
then your kernel might be non-standard, in which case say 'no' to
use Mondo's failsafe kernel (provided separately).</TD
></TR
><TR
><TD
><A
HREF="images/maverifyq.png"
TARGET="_top"
><SPAN
CLASS="INLINEMEDIAOBJECT"
><IMG
SRC="images/maverifyq-mini.png"></SPAN
></A
></TD
><TD
>If you want to verify the archives after writing them to media, say
'yes' here. If you have absolute faith in your hardware and your
Linux distribution, say 'no'... and a little prayer.</TD
></TR
><TR
><TD
><A
HREF="images/maproceedq.png"
TARGET="_top"
><SPAN
CLASS="INLINEMEDIAOBJECT"
><IMG
SRC="images/maproceedq-mini.png"></SPAN
></A
></TD
><TD
>If you are sure you want to go ahead, say 'yes' and find something
else to do while Mondo backs up your computer. If you say 'no' then
you will be unceremoniously dumped at the shell prompt. :-)</TD
></TR
><TR
><TD
><A
HREF="images/1.png"
TARGET="_top"
><SPAN
CLASS="INLINEMEDIAOBJECT"
><IMG
SRC="images/1-mini.png"></SPAN
></A
></TD
><TD
>The backup process will now commence. There are some pre-backup
tasks to be carried out first but the backup is essentially
underway. To simplify the backup process, you were asked a series
of questions. Next time, if you like, you could call mondoarchive
with various command-line switches to control its behavior, instead
of answering a series of questions. See the man page for details.</TD
></TR
><TR
><TD
><A
HREF="images/3.png"
TARGET="_top"
><SPAN
CLASS="INLINEMEDIAOBJECT"
><IMG
SRC="images/3-mini.png"></SPAN
></A
></TD
><TD
>Mondo will make a catalog of all files to be backed up. This may
take up to five minutes. The list of files will be divided into
sets, approximately 4 MB (before compression) of files per set.
This typically takes one minute.</TD
></TR
><TR
><TD
><A
HREF="images/4.png"
TARGET="_top"
><SPAN
CLASS="INLINEMEDIAOBJECT"
><IMG
SRC="images/1-mini.png"></SPAN
></A
></TD
><TD
>Mondo calls Mindi. Mindi generates bootable media image and
auxiliary data disk images which are based on your existing Linux
distribution and filesystem. That way, you can be sure Mondo's
tools will be compatible with your existing filesystems and
binaries: Mondo's tools are your tools. Mindi takes up to five
minutes to run.</TD
></TR
><TR
><TD
><A
HREF="images/5tape.png"
TARGET="_top"
><SPAN
CLASS="INLINEMEDIAOBJECT"
><IMG
SRC="images/5tape-mini.png"></SPAN
></A
></TD
><TD
>Finally, Mondo begins backing up your computer. This process may
take a few minutes or a few hours, depending on how much data you
are archiving, how fast your CPU is, how much RAM you have, and so
on. It will backup your regular files and then your large files
(files larger than approximately 32MB). If you have opted to verify
your backups, Mondo will do that too.</TD
></TR
></TBODY
></TABLE
><P
></P
></DIV
><P
></P
><UL
><LI
><P
>Try to boot from the first media of the backup.
Choose 'Compare Mode' by typing compare at the boot screen.</P
></LI
><LI
><P
>If you can boot, fine. If not, make a Mindi "Test" CD to
checkout the compatibility of your system. (see
<A
HREF="#TEST-MINDI"
>Testing Mindi</A
> for more
details). Remove the media; boot your computer as usual;
execute as root</P
><P
></P
><DIV
CLASS="INFORMALTABLE"
><P
></P
><A
NAME="AEN221"
></A
><TABLE
BORDER="1"
CLASS="CALSTABLE"
><COL><TBODY
><TR
><TD
> bash# mindi</TD
></TR
><TR
><TD
> bash# cd /var/cache/mindi </TD
></TR
></TBODY
></TABLE
><P
></P
></DIV
><P
>(for CD-R)</P
><P
></P
><DIV
CLASS="INFORMALTABLE"
><P
></P
><A
NAME="AEN230"
></A
><TABLE
BORDER="1"
CLASS="CALSTABLE"
><COL><TBODY
><TR
><TD
>bash# cdrecord dev=0,0,0 speed=4 -eject -v mindi.iso</TD
></TR
><TR
><TD
>bash# wodim dev=0,0,0 speed=4 -eject -v mindi.iso</TD
></TR
></TBODY
></TABLE
><P
></P
></DIV
><P
>(for CD-RW)</P
><P
></P
><DIV
CLASS="INFORMALTABLE"
><P
></P
><A
NAME="AEN239"
></A
><TABLE
BORDER="1"
CLASS="CALSTABLE"
><COL><TBODY
><TR
><TD
>bash# cdrecord dev=0,0,0 speed=4 blank=fast -eject -v mindi.iso</TD
></TR
><TR
><TD
>bash# wodim dev=0,0,0 speed=4 blank=fast -eject -v mindi.iso</TD
></TR
></TBODY
></TABLE
><P
></P
></DIV
><P
>Reboot your system with the created Mindi CD, with the BIOS
set to boot from CD. If the result is a command line in 'Expert'
mode, your system checks out. Remove the CD and reboot your
system.</P
></LI
><LI
><P
>If you still cannot boot from Mindi's CD then please e-mail
the <A
HREF="http://lists.sourceforge.net/lists/listinfo/mondo-devel"
TARGET="_top"
>mondorescue mailing list</A
> for help.</P
></LI
></UL
><P
>When making a backup on a live system, there will always be
processes running that will write out data on the system after you
have made the backup and before you have made the compare, this
will result in difference showing up when comparing your backup.
For a full explanation and what can be done to avoid this, please
read this section.</P
><P
></P
><UL
><LI
><P
>This QuickStart covers the ideal case. Upon receiving any
system feedback/errors, read each related HOWTO section.</P
><P
>Example 2-1. A test backup of your /home directory to CD-Rs
using the command line</P
><P
></P
><DIV
CLASS="INFORMALTABLE"
><P
></P
><A
NAME="AEN256"
></A
><TABLE
BORDER="1"
CLASS="CALSTABLE"
><COL><TBODY
><TR
><TD
> bash# mondoarchive -OVc 4 -I /home -gF </TD
></TR
></TBODY
></TABLE
><P
></P
></DIV
><P
>The 'c' means you must be writing to CD-Rs, not CD-RWs (the
latter would require 'w' instead of 'c'). The '4' is the speed of
your CD writer. The string after -I is the path to be backed up.
The '-gF' means you are going to see the pretty yellow-on-blue
screen instead of the boring white-on-black screen. :) It also
means Mondo will not offer to create physical boot media for
you. It is assumed that you are able to boot from the CD which
Mondo has generated.</P
><P
>Example 2-2. A backup of your whole filesystem to NFS using
the command line</P
><P
></P
><DIV
CLASS="INFORMALTABLE"
><P
></P
><A
NAME="AEN264"
></A
><TABLE
BORDER="1"
CLASS="CALSTABLE"
><COL><TBODY
><TR
><TD
> bash# mkdir -p /mnt/nfs</TD
></TR
><TR
><TD
> bash# mount nfs://192.168.1.28:/home/nfs /mnt/nfs
</TD
></TR
><TR
><TD
> bash# mondoarchive -OVn nfs://192.168.1.28:/home/nfs -gF[...]
</TD
></TR
><TR
><TD
>bash# umount /mnt/nfs
</TD
></TR
><TR
><TD
> bash# cdrecord dev=0,0,0 speed=4 -eject -v /var/cache/mindi/mindi.iso</TD
></TR
></TBODY
></TABLE
><P
></P
></DIV
><P
>Note that you have to mount the NFS partition, backup to it,
unmount it, and create a boot CD to allow you to restore from
scratch if necessary. To reassure yourself that you will be able to
restore from the NFS share even if your PC is wiped, please boot
from the Mindi CD and type 'compare'. The on-screen instructions
from that point on should be sufficient.</P
><P
>Example 2-3. A backup of your whole
filesystem to tape using the command line</P
><P
></P
><DIV
CLASS="INFORMALTABLE"
><P
></P
><A
NAME="AEN280"
></A
><TABLE
BORDER="1"
CLASS="CALSTABLE"
><COL><TBODY
><TR
><TD
> bash# mondoarchive -OVt -d /dev/st0 -9 -L -g </TD
></TR
></TBODY
></TABLE
><P
></P
></DIV
><P
>In this case, we assume Syslinux is incompatible with your
boot media. For some reason, some BIOSes just don't like Syslinux.
If you find this to be the case for your computer, please use '-L'
to force Mondo to use LILO instead of Syslinux as the boot loader
for its media. (NB: This has nothing to do with which boot
loader your hard drive uses.) Also, it is a good habit to specify
your tape streamer with '-d <device>'. You don't usually need
to but it's good to be on the safe side. Some computers call your
tape streamer /dev/osst0, some call it /dev/ftape, ...
Also, depending on the tape streamer model, a tape should be inserted
in the tape drive before starting mondoarchive, otherwise it may not
recognize the drive.</P
></LI
></UL
></DIV
><DIV
CLASS="CHAPTER"
><HR><H1
><A
NAME="OVERVIEW"
></A
>Chapter 3. Overview</H1
><DIV
CLASS="SECT1"
><H2
CLASS="SECT1"
><A
NAME="OVERVIEW-MONDORESCUE"
>3.1. Mondo Rescue</A
></H2
><P
>Mondo Rescue backs up your file system to CD, tape, NFS
(archives stored remotely) or ISO's (archives stored locally).
Mondo uses afio as the backup engine; afio is a well-respected
replacement for tar. In the event of catastrophic data loss, you
may restore some or all of your system, even if your hard drives
are now blank. Mondo Rescue can do a lot of other cool
things:</P
><P
></P
><UL
><LI
><P
>You can use Mondo to clone an installation of Linux. Just
backup the crucial stuff and exclude /home, /var/log, etc.</P
></LI
><LI
><P
>You can backup a non-RAID file system and restore it as RAID
including the root partition (if your kernel supports that).</P
></LI
><LI
><P
>You can backup a system running on one format and restore as
another format.</P
></LI
><LI
><P
>You can restructure your partitions, e.g. shrink/enlarge,
reassign devices, add hard drives, etc, before you partition and
format your drives. Mondo will restore your data and amend
/etc/lilo.conf and /etc/fstab accordingly.</P
></LI
><LI
><P
>You can backup Linux/Windows systems, including the boot
sectors. Mondo will make everything right at restore-time.
(However, do run "Scandisk" when you first boot into Windows, just
in case.)</P
></LI
><LI
><P
>You can use your Mondo backup CD to verify the integrity of
your computer.</P
></LI
></UL
><P
>Mondo's principal virtue is that it protects you from the
problems that can arise when you reinstall completely from scratch.
If you want to wipe and restore your system every year just as a
matter of 'good practice', Mondo is not for you. However, if you
want to get up and running again in a hurry after someone breaks
into your computer and wipes it (or if you accidentally wipe it
yourself) then Mondo is definitely for you. It will permit you to
roll back to a known-good installation in a very short period of
time, sometimes as little as twenty minutes. Even if you backup
large amounts of data to tape daily and do not want to add yet
another backup regime, please consider backing up the core
filesystem (i.e. everything but the directories containing your
huge database and your prizewinning novel) every month or so, just
in case. You will be glad you did.</P
><P
>What is Mondo not?</P
><P
>Mondo is not an everyday backup program. It is not designed
to replace tar, afio, kbackup, etc. Mondo is designed to make it
possible to recover from scratch if necessary. Tar and afio offer a
quick, convenient way to backup small sets of files, sometimes to
removable media.</P
></DIV
><DIV
CLASS="SECT1"
><HR><H2
CLASS="SECT1"
><A
NAME="OVERVIEW-MINDI"
>3.2. Mindi</A
></H2
><P
>Mindi Linux creates a set of boot/root media images
that will let you perform basic system maintenance on your Linux
distro. The principal virtues of Mindi's boot disks are the fact
that they contain your kernel, modules, tools and libraries. You
can ask for additional binaries (or other files) to be included on
the kit. The libraries will be added for you.</P
><P
>Whichever modules were loaded at backup-time, they are
reloaded at boot-time. So, in theory, you will boot into almost the
same environment as you were in when you backed up. If you want to
add files to your Mindi boot disks, edit '<INSTALLPATH OF
MINDI>/mindi/deplist.txt' and add the files to that list. The
added files and dependencies, will be spread across the data disks
at run-time.</P
><P
>Mindi makes sure that Mondo has all the tools it needs at
boot-time. Mondo uses fdisk, mkfs, cat, less, more, afio, gzip,
bzip2, your keyboard configuration, your glibc libraries, your
other libraries, your kernel, your modules, ... which is a lot of tools!
Mindi takes care of all that, so that Mondo can get on with the job of backing
up or restoring your data.</P
><P
>Mindi is also handy for making boot CDs/disks which stand on
their own. You do not need Mondo. Indeed, if you like, you could
use another backup/restore program with Mindi. Just add it to
Mindi's dependency list (type 'locate deplist.txt' to find it).
Mindi will include your software on its boot CD/disks the next time
you run mindi.</P
></DIV
><DIV
CLASS="SECT1"
><HR><H2
CLASS="SECT1"
><A
NAME="OVERVIEW-LINUXBACKUP"
>3.3. Linux Backup</A
></H2
><P
>Mondo Rescue and Mindi Linux are used primarily as Linux
backup and cloning tools. The fall in prices of CD-RW drives and
writable discs will allow current users to keep good backups and
future users to leverage the cloning capability.</P
><P
>Tape drives are more likely to suit your needs if you run a
larger installation (or have lots of MP3's). Warning! OnStream
drives do not play well with Mondo. I do not know why. It is, in my
opinion, something which OnStream should look into. Mondo uses
fopen(), fread(), fwrite() and fclose() to interact with tape
drives. That works for most drives but some drives just don't like
that.
Also, depending on the tape streamer model, a tape should be inserted
in the tape drive before starting mondoarchive, otherwise it may not
recognize the drive.</P
><P
>Mondo Rescue has been tested thousands of times on various computers.
It has worked for them.
Thousands of users testify to Mondo's stability and its ease of
use. However, please test it on your own system before you rely on
it. In fact, do not rely on any software until you have tested it
to see if it performs as expected.</P
><P
>To establish that Mondo will behave well in an emergency,
please be prepared. Run a test backup as follows:-</P
><P
></P
><UL
><LI
><P
>Run mondoarchive without any command-line options.</P
></LI
><LI
><P
>Backup a subset of files - e.g. /usr/local - to CD or
tape. Say 'yes' when asked if you want to verify them.</P
></LI
><LI
><P
>If you are not backing up to CD, please create boot
media when prompted.</P
></LI
></UL
><P
>Next, restore archives to your live filesystem.</P
><P
></P
><UL
><LI
><P
>When mondoarchive terminates, run mondorestore without any
command-line options.</P
></LI
><LI
><P
>Insert the media when prompted.
Press <Enter>. Wait a moment.</P
></LI
><LI
><P
>Select a subset of files to restore, e.g. /usr/local/man
and /usr/local/bin. Hit OK.</P
></LI
><LI
><P
>Restore files to /tmp or /root/RESTORED or something
similar.</P
></LI
><LI
><P
>When mondorestore terminates, compare the restored files
to the originals using cmp or diff.</P
></LI
></UL
><P
>Finally, simulate an emergency restore.</P
><P
></P
><UL
><LI
><P
>Boot from media.</P
></LI
><LI
><P
>Select 'Interactive Mode' at boot-time. (Type
'interactive' and hit <Enter>.)</P
></LI
><LI
><P
>Hit OK when shown the mountlist. Say 'yes' when asked if
you accept the mountlist.</P
></LI
><LI
><P
>Select files to restore, e.g. /usr/local/man and
/usr/local/bin. Hit OK.</P
></LI
><LI
><P
>Restore files to /tmp or /root/RESTORED or something
similar.</P
></LI
><LI
><P
>When mondorestore terminates, please reboot and compare
the restored files to the originals.</P
></LI
></UL
><P
>FYI, the subroutines to repartition and reformat your drives
are very stable. If you are a RAID or LVM user, you
might encounter some difficulties when wiping and restoring
from scratch because of the sheer range of filesystem layouts and
the impossibility of testing Mondo on every single one. If you have
trouble, just drop to the command-line and partition/format
manually. Then, call mondorestore, select Interactive Mode, and say
'no' when asked if you want Mondo to partition or format your
drives for you.</P
><P
>You see, even if you have trouble, you still have two hands
and most of the tools you need - lvchange, pvcreate, fdisk, mkraid,
etc. - to do it manually. After you have prepped and formatted your
drives manually (if you have to), just run mondorestore again and
say 'no' when asked if you want to prep or format your drives. What
could be easier?</P
></DIV
><DIV
CLASS="SECT1"
><HR><H2
CLASS="SECT1"
><A
NAME="OVERVIEW-WINBACKUP"
>3.4. Windows Backup</A
></H2
><P
>Backing up windows partitions.</P
><DIV
CLASS="SECT2"
><HR><H3
CLASS="SECT2"
><A
NAME="OVERVIEW-WINBACKUP-WIN95"
>3.4.1. Windows ME/95/98</A
></H3
><P
>Verify that the partition is listed in /etc/fstab and is
mounted (e.g. /dev/hda1). Mondo will take care of everything else.
The files will be archived just like all other files in the live
file system. At restore-time, Mondo will take care of the boot
sector of /dev/hda1 prior to the restore.</P
><P
>Note: if Windows ME/95/98 is not located on /dev/hda1 or
/dev/sda1, then Mondo will not take care of the boot sector of
/dev/hda1. The user will have to boot from a DOS floppy and run SYS
C: to correct the Windows boot sector.</P
></DIV
><DIV
CLASS="SECT2"
><HR><H3
CLASS="SECT2"
><A
NAME="OVERVIEW-WINBACKUP-WINNT"
>3.4.2. Windows NT4/2K/XP</A
></H3
><P
>Windows NT4/2K/XP typically use the NTFS file system, not
VFAT.. The user should use '-x /dev/hda1' (or whichever device the
Windows partition resides). Mondo will treat the partition as a
biggiefile. Mondo will also add an entry to the mountlist to
reflect the size and type of the partition. The user may not edit
that partition's size at restore-time (for obvious reasons).</P
><P
>Please bear in mind that Mondo was written for Linux users.
If Mondo does not backup or restore your Windows system well, you
might want to consider reporting it to the <A
HREF="http://lists.sourceforge.net/lists/listinfo/mondo-devel"
TARGET="_top"
>mondorescue mailing list</A
></P
></DIV
></DIV
><DIV
CLASS="SECT1"
><HR><H2
CLASS="SECT1"
><A
NAME="OVERVIEW-HISTORY"
>3.5. Mondo Rescue and Mindi Linux
History</A
></H2
><P
>Mondo Rescue was created in December 1999 by Hugo Rabson as a utility to
clone Linux/Windows installations. Norton Ghost would not do the
job, and his boss wanted to jump on the Linux bandwagon. So, he wrote
a few scripts and shoehorned them into the latest Linux-Mandrake
CD. Since that time, Mondo grew into a disaster recovery suite for
Linux and Windows. Mondo forced him to learn about the kernel, its
initrd initial ramdisk, modules, library dependencies, disk
partitioning, and the myriad differences between the Top 10 Linux
distributions.</P
><P
>The first formal release was made on February 18th, 2000.
Mondo is currently one of the top five Linux backup/restore
programs. Mondo has been compared favorably to ArcServe, Arkeia and
BRU. Although Mondo lacks the more advanced, enterprise-level
features of ArcServe and Arkeia, for workstations and small- to
medium-size servers it is ideal because it is small, fast,
efficient, stable, comes with source code, and is being actively
developed and supported.</P
><P
> Since November 2005, Hugo Rabson has tranfered the maintenance
of the Mondo Rescue suite to Andree Leidenfrost and Bruno Cornec,
both previous developers and packagers of the tool since nearly
the begining.</P
></DIV
><DIV
CLASS="SECT1"
><HR><H2
CLASS="SECT1"
><A
NAME="OVERVIEW-SYSREQ"
>3.6. System Requirements</A
></H2
><DIV
CLASS="SECT2"
><H3
CLASS="SECT2"
><A
NAME="OVERVIEW-SYSRQ-HWREQ"
>3.6.1. Hardware Requirements</A
></H3
><P
>Your computer must have:</P
><P
></P
><UL
><LI
><P
>Intel(R)-compatible CPU (ia32, x86_64/amd64 or ia64)</P
></LI
><LI
><P
>64MB of RAM (128MB recommended)</P
></LI
><LI
><P
>800MB of hard disk space free</P
></LI
><LI
><P
>CD writer, tape streamer, NFS share or some way to backup the
backups :)</P
></LI
></UL
><P
>It is recommended that your computer have very good airflow.
The backup with Mondo Rescue and Mindi Linux will utilize your CPU,
CD drive and fixed disk(s) like very few other applications. With a
few hours of system backup activity, computers without sufficient
airflow may show symptoms such as not burning full CD discs. The
solution is a $20 or less additional fan at your local electronics
discount store.</P
></DIV
><DIV
CLASS="SECT2"
><HR><H3
CLASS="SECT2"
><A
NAME="OVERVIEW-SYSRQ-KERNELREQ"
>3.6.2. Kernel Requirements</A
></H3
><P
>Your kernel must have:</P
><P
></P
><UL
><LI
><P
>stable loopfs support, which means it really needs to be
2.2.19 or 2.4.7 (or later)</P
></LI
><LI
><P
>CD-ROM device support</P
></LI
><LI
><P
>ISO9660 file system support</P
></LI
><LI
><P
>initrd ramdisk support (built-in)</P
></LI
><LI
><P
>Virtual memory file system support (built-in)</P
></LI
><LI
><P
>ext2 file system support (built-in)</P
></LI
><LI
><P
>Support for the backup media (Tape, CD-RW, NFS, Hard
disk)</P
></LI
><LI
><P
>If the backup media is CD-RW then you need SCSI emulation
also</P
><P
>vfat support in the active kernel - mindi needs this when creating
syslinux boot media</P
></LI
></UL
><P
>Please note that the stock kernels of Red Hat/RHEL/Fedora,
Mandrake/Mandriva, SuSE/SLES/OpenSuSE, Debian and Slackware
all meet Mondo's requirements. If your kernel does not meet Mondo's
requirements then there is something wrong with it. Mondo's demands
are not unreasonable.</P
><P
>Mondo (specifically Mindi) does not require any specific
module. It does require that your kernel support the initrd
initial ramdisk facility. Typically this is supported by the Linux
kernel. Modules used are needed to support the CD,
hard disks, etc. If the support is modular, then the modules will
be incorporated in a boot disk by Mindi. If the support is built-in
(static), then it will be available at boot-time by default.</P
></DIV
><DIV
CLASS="SECT2"
><HR><H3
CLASS="SECT2"
><A
NAME="OVERVIEW-SYSRQ-SWREQ"
>3.6.3. Software Requirements</A
></H3
><P
>See Mondo's <A
HREF="http://www.mondorescue.org/downloads.shtml"
TARGET="_top"
>Download
page</A
> for details.</P
><P
>Mondo requires afio, bzip2, cdrtools/cdrecord/growisofs (may be part of the dvd+rw-tools package), ncurses, newt,
isolinux/syslinux, lzo (optional), lzop (optional), mkisofs, slang,
and a few other packages.</P
><P
>Good Linux distributions provide all these packages. If yours
does not then please go to the aforementioned Download page or surf
the Net, preferably the website of the distribution you are
using.</P
><P
>Mondo's expectations are not unreasonable, either of your
Linux distribution or of your kernel. However, if your distribution
fails to meet its expectations and you cannot find out how to
resolve them, please feel free to e-mail the <A
HREF="http://lists.sourceforge.net/lists/listinfo/mondo-devel"
TARGET="_top"
>mondorescue mailing list</A
></P
></DIV
></DIV
></DIV
><DIV
CLASS="CHAPTER"
><HR><H1
><A
NAME="INSTALLATION"
></A
>Chapter 4. Installation</H1
><DIV
CLASS="SECT1"
><H2
CLASS="SECT1"
><A
NAME="INSTALLATION-MINDI"
>4.1. Mindi Installation</A
></H2
><P
>If you are installing from a tarball then copy it to wherever
you have enough space, for example /tmp and type:</P
><P
></P
><DIV
CLASS="INFORMALTABLE"
><P
></P
><A
NAME="AEN423"
></A
><TABLE
BORDER="1"
CLASS="CALSTABLE"
><COL><TBODY
><TR
><TD
> bash# cd /tmp</TD
></TR
><TR
><TD
> bash# tar -zxvf mindi-1.x.tgz
</TD
></TR
><TR
><TD
>bash# cd mindi-1.x</TD
></TR
><TR
><TD
> bash# ./install.sh </TD
></TR
></TBODY
></TABLE
><P
></P
></DIV
><P
>This installs mindi additional files into /usr/local/lib/mindi and
the program into /usr/local/sbin</P
><P
>Or, if you are installing from an RPM/deb then copy it to
wherever you have enough space, for example /tmp and type:</P
><P
></P
><DIV
CLASS="INFORMALTABLE"
><P
></P
><A
NAME="AEN437"
></A
><TABLE
BORDER="1"
CLASS="CALSTABLE"
><COL><TBODY
><TR
><TD
> bash# rpm -Uvh /tmp/mindi-1.x-x.i386.rpm</TD
></TR
><TR
><TD
> or</TD
></TR
><TR
><TD
> bash# dpkg -i /tmp/mindi-1.x-x.deb </TD
></TR
></TBODY
></TABLE
><P
></P
></DIV
><P
>This installs mindi additional files into /usr/lib/mindi and
the program into /usr/sbin.</P
></DIV
><DIV
CLASS="SECT1"
><HR><H2
CLASS="SECT1"
><A
NAME="INSTALLATION-MINDI-BUSYBOX"
>4.2. Mindi Busybox Installation</A
></H2
><P
>If you are installing from a tarball then copy it to wherever
you have enough space, for example /tmp and type:</P
><P
></P
><DIV
CLASS="INFORMALTABLE"
><P
></P
><A
NAME="AEN451"
></A
><TABLE
BORDER="1"
CLASS="CALSTABLE"
><COL><TBODY
><TR
><TD
> bash# cd /tmp</TD
></TR
><TR
><TD
> bash# tar -zxvf mindi-busybox-1.x.tgz
</TD
></TR
><TR
><TD
> bash# cd mindi-busybox-1.x
</TD
></TR
><TR
><TD
> bash# make oldconfig
</TD
></TR
><TR
><TD
> bash# make busybox
</TD
></TR
><TR
><TD
> bash# make install
</TD
></TR
></TBODY
></TABLE
><P
></P
></DIV
><P
>This installs busybox files and symlinks into /usr/local/lib/mindi/rootfs</P
><P
>Or, if you are installing from an RPM/deb then copy it to
wherever you have enough space, for example /tmp and type:</P
><P
></P
><DIV
CLASS="INFORMALTABLE"
><P
></P
><A
NAME="AEN469"
></A
><TABLE
BORDER="1"
CLASS="CALSTABLE"
><COL><TBODY
><TR
><TD
> bash# rpm -Uvh /tmp/mindi-busybox-1.x-x.i386.rpm</TD
></TR
><TR
><TD
> or</TD
></TR
><TR
><TD
> bash# dpkg -i /tmp/mindi-busybox-1.x-x.deb </TD
></TR
></TBODY
></TABLE
><P
></P
></DIV
><P
>This installs busybix files and symlinks into /usr/lib/mindi/rootfs </P
></DIV
><DIV
CLASS="SECT1"
><HR><H2
CLASS="SECT1"
><A
NAME="INSTALLATION-MONDO"
>4.3. Mondo Installation</A
></H2
><P
>If you are installing from a tarball then copy it to wherever
you have enough space, for example /tmp and type:</P
><P
></P
><DIV
CLASS="INFORMALTABLE"
><P
></P
><A
NAME="AEN483"
></A
><TABLE
BORDER="1"
CLASS="CALSTABLE"
><COL><TBODY
><TR
><TD
> bash# cd /tmp</TD
></TR
><TR
><TD
> bash# tar -zxvf mondo-2.xx.tgz
</TD
></TR
><TR
><TD
>bash# cd mondo-2.xx
</TD
></TR
><TR
><TD
> bash# ./configure
</TD
></TR
><TR
><TD
>bash# make && make install </TD
></TR
></TBODY
></TABLE
><P
></P
></DIV
><P
>This installs mondo into /usr/local/lib/mondo and installs
the programs into /usr/local/sbin</P
><P
>Or, if you are installing from an RPM/deb then copy it to copy it
to wherever you have enough space, for example /tmp and
type:</P
><P
></P
><DIV
CLASS="INFORMALTABLE"
><P
></P
><A
NAME="AEN499"
></A
><TABLE
BORDER="1"
CLASS="CALSTABLE"
><COL><TBODY
><TR
><TD
> bash# rpm -Uvh /tmp/mondo-2.x-x.i386.rpm</TD
></TR
><TR
><TD
> or</TD
></TR
><TR
><TD
> bash# dpkg -i /tmp/mondo-2.x-x.deb </TD
></TR
></TBODY
></TABLE
><P
></P
></DIV
><P
>This installs mondo into /usr/lib/mondo and installs
the programs into /usr/sbin</P
></DIV
><DIV
CLASS="SECT1"
><HR><H2
CLASS="SECT1"
><A
NAME="RPM-VERIF"
>4.4. RPM verifications</A
></H2
><P
>For RPM based distributions (Fedora, OpenSuSE, Mandriva, ...), you may want to do this post-install in order to check the validity of your installation:</P
><DIV
CLASS="INFORMALTABLE"
><P
></P
><A
NAME="AEN512"
></A
><TABLE
BORDER="1"
CLASS="CALSTABLE"
><COL><TBODY
><TR
><TD
> bash# rpm -Va mindi mondo mindi-busybox
</TD
></TR
></TBODY
></TABLE
><P
></P
></DIV
><P
> 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.
</P
></DIV
></DIV
><DIV
CLASS="CHAPTER"
><HR><H1
><A
NAME="TEST"
></A
>Chapter 5. Tests</H1
><DIV
CLASS="SECT1"
><H2
CLASS="SECT1"
><A
NAME="TEST-MINDI"
>5.1. Testing Mindi</A
></H2
><P
>Mindi is a vital part of the backup procedure. If you have
used Mondo before or if you are in a hurry, skip steps 6.2 and 6.3;
go straight to QuickStart.</P
><P
>However, if you have time or if you have been having trouble
getting Mondo to work, I would recommend trying out Mindi directly
(rather than via Mondo) to see if it can produce a bootable CD on
your system.</P
><P
>Make sure you are root while doing this, otherwise mindi will
fail, now do this.</P
><P
>If you have any problems, please:-</P
><P
></P
><UL
><LI
><P
>less /var/log/mindi.log</P
></LI
><LI
><P
>feel free to edit mindi (it's a shell script, btw) to try
to fix the problem yourself</P
></LI
><LI
><P
>contact the <A
HREF="http://lists.sourceforge.net/lists/listinfo/mondo-devel"
TARGET="_top"
>mondorescue mailing list</A
> if you get stuck.</P
></LI
></UL
><P
>Type:-</P
><P
></P
><DIV
CLASS="INFORMALTABLE"
><P
></P
><A
NAME="AEN536"
></A
><TABLE
BORDER="1"
CLASS="CALSTABLE"
><COL><TBODY
><TR
><TD
> bash# mindi </TD
></TR
></TBODY
></TABLE
><P
></P
></DIV
><P
>Example screen output, selecting to use your own kernel, to
create boot disks, and to create a bootable CD image:</P
><P
></P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="SCREEN"
> # mindi
Mindi Linux mini-distro generator v1.09-r762
Latest Mindi is available from http://www.mondorescueg
BusyBox sources are available from http://www.busybox.net
------------------------------------------------------------------------------
Do you want to use your own kernel to build the boot disk (y/n) ?y
Would you like to use LILO (instead of syslinux)
for your boot media (y/n) ?n
Analyzing dependency requirements Done.
Making complete dependency list Done.
Analyzing your keyboard's configuration.
Adding the following keyboard mapping tables: us-latin1 Done.
Assembling dependency files................................................................... Done.
The files have been subdivided into 5 directories. Your mountlist will look like this:-
Finding all volume groups
No volume groups found
No volume groups found
No volume groups found
No volume groups found
DEVICE MOUNTPOINT FORMAT SIZE (MB)
/dev/hda1 / ext3 399
/dev/hda9 /home ext3 48478
/dev/hda6 /usr ext3 4999
/dev/hda7 /var ext3 1000
/dev/hda5 swap swap 349
/dev/hda8 swap swap 2003
Finding all volume groups
No volume groups found
No volume groups found
No volume groups found
No volume groups found
Tarring and zipping the groups.................. Done.
Creating data disk #1...#2...#3...#4...#5... Done.
Making 1722KB boot disk...........................1440+0 enregistrements lus.
1440+0 enregistrements écrits.
mke2fs 1.38 (30-Jun-2005)
Failed to copy /boot/vmlinuz-2.6.12-15mdk-i686-up-4GB to ramdisk
Making 2880KB boot disk...........................mkfs.vfat 2.10 (22 Sep 2003)
... 2880 KB boot disks were created OK Done.
In the directory '/var/cache/mindi' you will find the images:-
mindi-data-1.img mindi-data-2.img mindi-data-3.img mindi-data-4.img mindi-data-5.img mindi-root.1440.img
Shall I make a bootable CD image? (y/n) y
NB: Mindi's bootable CD always uses isolinux.
For a bootable CD w/LILO, please use Mondo.
Finished.
Boot and data disk images were created.
#
</PRE
></TD
></TR
></TABLE
><P
>If your kernel is too large (more than about 900KB) then you
cannot make boot media, although you can still make a bootable
CD image. The easiest way to test Mindi in either case is to say
'n' to its first question and 'y' to its second, then use the
separate application cdrecord or wodim to make a bootable CD-R or
CD-RW.</P
><P
>Use the cdrecord or wodim application to write the CD image:</P
><P
></P
><DIV
CLASS="INFORMALTABLE"
><P
></P
><A
NAME="AEN547"
></A
><TABLE
BORDER="1"
CLASS="CALSTABLE"
><COL><TBODY
><TR
><TD
> bash# cd /var/cache/mindi</TD
></TR
><TR
><TD
> bash# cdrecord -scanbus</TD
></TR
><TR
><TD
> bash# wodim --devices</TD
></TR
></TBODY
></TABLE
><P
></P
></DIV
><P
>The output of the above call will tell you your
CD writer's node. It is usually '0,0,0'. Choose one of the
following calls to write the CD, depending on whether the disk in
the drive is a CD-R or a CD-RW. Please replace 'x,x,x' with your
writer's node. For further information, type 'man cdrecord" from a
Linux command line.</P
><P
>If writing to a CD-RW Drive/Disc:</P
><P
></P
><DIV
CLASS="INFORMALTABLE"
><P
></P
><A
NAME="AEN559"
></A
><TABLE
BORDER="1"
CLASS="CALSTABLE"
><COL><TBODY
><TR
><TD
>bash# cdrecord -v blank=fast dev=x,x,x speed=4 mindi.iso (for CD-RW)</TD
></TR
><TR
><TD
> bash# wodim -v blank=fast dev=/dev/xxx speed=4 mindi.iso (for CD-RW)</TD
></TR
></TBODY
></TABLE
><P
></P
></DIV
><P
>If writing to a CD-R Drive/Disc:</P
><P
></P
><DIV
CLASS="INFORMALTABLE"
><P
></P
><A
NAME="AEN568"
></A
><TABLE
BORDER="1"
CLASS="CALSTABLE"
><COL><TBODY
><TR
><TD
>bash# cdrecord -v dev=x,x,x speed=4 mindi.iso (for CD-R)</TD
></TR
><TR
><TD
> bash# wodim -v dev=/dev/xxx speed=4 mindi.iso (for CD-R)</TD
></TR
></TBODY
></TABLE
><P
></P
></DIV
></DIV
></DIV
><DIV
CLASS="CHAPTER"
><HR><H1
><A
NAME="BACKUP"
></A
>Chapter 6. Backup</H1
><DIV
CLASS="SECT1"
><H2
CLASS="SECT1"
><A
NAME="BACKUP-RECOMMANDATIONS"
>6.1. Recommendations</A
></H2
><P
></P
><UL
><LI
><P
>Shut down all possible applications (this minimizes any
compare differences following the backup). Especially shutdown
properly any running database on your system, as the recovery
may lead to corrupted data. Or if applicable, boot to single user mode.</P
></LI
><LI
><P
>Type:</P
></LI
></UL
><P
></P
><DIV
CLASS="INFORMALTABLE"
><P
></P
><A
NAME="AEN585"
></A
><TABLE
BORDER="1"
CLASS="CALSTABLE"
><COL><TBODY
><TR
><TD
> bash# mondoarchive </TD
></TR
></TBODY
></TABLE
><P
></P
></DIV
><P
>For most users, that should be enough. :-) Mondoarchive will
usually autodetect your hardware and configure it for you.</P
><P
>If you are a power user (or you like to control every detail
of how Mondo runs) then you may want to look at the command-line
switches. For example:-</P
><P
></P
><DIV
CLASS="INFORMALTABLE"
><P
></P
><A
NAME="AEN593"
></A
><TABLE
BORDER="1"
CLASS="CALSTABLE"
><COL><TBODY
><TR
><TD
> bash# mondoarchive -Ow9 -gF -I /home </TD
></TR
></TBODY
></TABLE
><P
></P
></DIV
><P
>cdrecord or wodim will tell you where your CD recorder lives, in SCSI
terms, which looks like '0,0,0'. The previous call to mondoarchive tells
Mondo to backup everything to a 4x CD-RW drive that has
a CD-RW disk in it. (Use -Oc instead of -Ow if you are using
CD-R.)</P
><P
>Please put the first CD-R(W) in the drive now. You will be
prompted to insert CD #2 but you will not be prompted to insert the
first disk. However, if you forget, do not worry: if Mondo fails to
write the first (or any) disk, it will offer to retry, abort or
fail.</P
><P
>Find the speed/compression
compromise that best suits your needs. Here maximum (-9) compression level is used.</P
><P
>If you are using cron then please consult the chapter that Conor Daly has dedicated to that <A
HREF="#BACKUP-CRON"
>topic</A
></P
></DIV
><DIV
CLASS="SECT1"
><HR><H2
CLASS="SECT1"
><A
NAME="BACKUP-CMD"
>6.2. Backup Commands and Options</A
></H2
><P
>Backup Command:</P
><P
></P
><DIV
CLASS="INFORMALTABLE"
><P
></P
><A
NAME="AEN607"
></A
><TABLE
BORDER="1"
CLASS="CALSTABLE"
><COL><TBODY
><TR
><TD
> mondoarchive <-option1> <-option2> ... <-optionN> </TD
></TR
></TBODY
></TABLE
><P
></P
></DIV
><P
>E.g.,</P
><P
></P
><DIV
CLASS="INFORMALTABLE"
><P
></P
><A
NAME="AEN614"
></A
><TABLE
BORDER="1"
CLASS="CALSTABLE"
><COL><TBODY
><TR
><TD
> bash# mondoarchive -E "/mnt/dos /mnt/cdrom" -9 -Oc 8 </TD
></TR
></TBODY
></TABLE
><P
></P
></DIV
><P
>Would create backup CD to a CD-R disc at the highest
compression level, writing at speed 8 and ignoring the /mnt/dos and
/mnt/cdrom directories.</P
><P
>To see a detailed list of switches and their meaning, see the
<A
HREF="http://www.mondorescue.org/docs/mondoarchive.8.html"
TARGET="_top"
>HTML
man page</A
> on the website or type 'man mondoarchive' at the
console.</P
><DIV
CLASS="SECT2"
><HR><H3
CLASS="SECT2"
><A
NAME="BACKUP-CMD-CDR"
>6.2.1. Standard Example With CD-R</A
></H3
><P
></P
><DIV
CLASS="INFORMALTABLE"
><P
></P
><A
NAME="AEN625"
></A
><TABLE
BORDER="1"
CLASS="CALSTABLE"
><COL><TBODY
><TR
><TD
> bash# mondoarchive -Oc 2 -g </TD
></TR
></TBODY
></TABLE
><P
></P
></DIV
><P
>Replace '2' in '-Oc 2' with the writer's speed. If
mondoarchive cannot find your CD-R then please add '-d 0,0,0' (or
whatever your CD writer's SCSI node is; usually, it is 0,0,0) to
the call.</P
><P
>Please insert the first disk in the writer while the PC is
chugging away. If Mondo needs additional CD-R(W) then it will ask
for them.</P
></DIV
><DIV
CLASS="SECT2"
><HR><H3
CLASS="SECT2"
><A
NAME="BACKUP-CMD-CDRW"
>6.2.2. Standard Example With CD-RW</A
></H3
><P
></P
><DIV
CLASS="INFORMALTABLE"
><P
></P
><A
NAME="AEN635"
></A
><TABLE
BORDER="1"
CLASS="CALSTABLE"
><COL><TBODY
><TR
><TD
> bash# mondoarchive -Ow 2 -g </TD
></TR
></TBODY
></TABLE
><P
></P
></DIV
><P
>Replace '2' in '-Ow 2' with the writer's speed.</P
></DIV
><DIV
CLASS="SECT2"
><HR><H3
CLASS="SECT2"
><A
NAME="BACKUP-CMD-TAPE"
>6.2.3. Standard Example With Tape</A
></H3
><P
></P
><DIV
CLASS="INFORMALTABLE"
><P
></P
><A
NAME="AEN644"
></A
><TABLE
BORDER="1"
CLASS="CALSTABLE"
><COL><TBODY
><TR
><TD
> bash# mondoarchive -Ot -d /dev/st0 -g </TD
></TR
></TBODY
></TABLE
><P
></P
></DIV
></DIV
><DIV
CLASS="SECT2"
><HR><H3
CLASS="SECT2"
><A
NAME="BACKUP-CMD-FAILSAFE"
>6.2.4. Standard Example With Failsafe kernel</A
></H3
><P
></P
><DIV
CLASS="INFORMALTABLE"
><P
></P
><A
NAME="AEN652"
></A
><TABLE
BORDER="1"
CLASS="CALSTABLE"
><COL><TBODY
><TR
><TD
> bash# mondoarchive -k FAILSAFE -Ow 2 </TD
></TR
></TBODY
></TABLE
><P
></P
></DIV
><P
>If you have problems during the restore phase, due to your kernel
(which may be the case on some distributions), you may want to explore the Failsafe
approach, In order for this option to work you'll have to get
the mindi-kernel tarball or package for your distribution.</P
></DIV
><DIV
CLASS="SECT2"
><HR><H3
CLASS="SECT2"
><A
NAME="BACKUP-CMD-NETWORK"
>6.2.5. Standard Example With Network Backup</A
></H3
><P
></P
><DIV
CLASS="INFORMALTABLE"
><P
></P
><A
NAME="AEN661"
></A
><TABLE
BORDER="1"
CLASS="CALSTABLE"
><COL><TBODY
><TR
><TD
> bash# mount nfs://192.168.1.3:/home/nfs -t nfs /mnt/nfs</TD
></TR
><TR
><TD
> bash# mondoarchive -OVn nfs://192.168.1.3:/home/nfs -g -s 200m</TD
></TR
><TR
><TD
> bash# umount /mnt/nfs </TD
></TR
></TBODY
></TABLE
><P
></P
></DIV
><P
>The resultant ISO's can be burned to CD's if you want (which
isn't a good idea unless you're a Mondo expert because they'll try
to restore over a network by default, which is silly because the
archives are on the CD's). Or, you can boot from the Mindi media
(or mondorescue.iso) and hit ENTER a few times to restore.</P
><P
>Those ISO images can also be used for a PXE restore. For this
to work, please refer to the file README.pxe provided with
your mindi package.</P
></DIV
></DIV
></DIV
><DIV
CLASS="CHAPTER"
><HR><H1
><A
NAME="BACKUP-CRON"
></A
>Chapter 7. HOWTO run mondo interactively using cron</H1
><DIV
CLASS="SECT1"
><H2
CLASS="SECT1"
><A
NAME="BACKUP-CRON-OVERVIEW"
>7.1. Overview</A
></H2
><P
> Mondoarchive is designed to run interactively (at least where
media changes are necessary). Cron does not allow user interaction
with a job. This section addresses the problem by using screen as a
wrapper for mondo.</P
><P
> This section is Copyright 2003 Conor Daly.</P
></DIV
><DIV
CLASS="SECT1"
><HR><H2
CLASS="SECT1"
><A
NAME="BACKUP-CRON-INTRO"
>7.2. Introduction</A
></H2
><P
>Mondoarchive is designed to run interactively. That's not strictly
true, if you run mondoarchive without the '-g' switch, it will just
run. However, there is a problem where media changes are necessary.
The user must change the media and tell mondoarchive that the change
has been done. The problem lies in the fact that cron does not allow
user interaction with a job. If you schedule a mondoarchive job via
cron, you better be sure it needs only one media. In practical terms,
this means using tapes or ISOs (if CD-R(W) is your backup medium).
However, for tape users, there's always the possibility that the
backup will overflow the tape while for CD-R(W) users, there is the
added hassle of burning the ISOs in the morning. If your CD_R(W)
backup routinely occupies more than one media, this is not for you
(use the ISO option and burn the CDs in the morning). This HOWTO
addresses the problem by using screen as a wrapper for mondo.</P
></DIV
><DIV
CLASS="SECT1"
><HR><H2
CLASS="SECT1"
><A
NAME="BACKUP-CRON-WHO"
>7.3. Who should read this?</A
></H2
><DIV
CLASS="SECT2"
><H3
CLASS="SECT2"
><A
NAME="AEN683"
>7.3.1. Insurance</A
></H3
><P
>Mondo users who wish to automate the backup and whose backups
routinely occupy close to one media are the best audience. If you
backup to tape, the occasion will arise when the backup will overflow
your tape. In this instance, mondoarchive will ask for another tape.
If you're using cron to start the backup, you won't be able to tell
mondo that the new tape is mounted and the backup will fail. If you
backup to CD-R(W), the same situation will arise but sooner.
</P
></DIV
><DIV
CLASS="SECT2"
><HR><H3
CLASS="SECT2"
><A
NAME="AEN686"
>7.3.2. Efficiency</A
></H3
><P
>If your backup already occupies two media, this method will allow
as much of the backup as possible to proceed during quiet periods.
Time the backup to start with enough time to complete the first media
shortly before the operator arrives for work. The next media can
be mounted and the backup completed asap and minimises the time for
which users are inconvenienced by the backup (eg. database locked...).
</P
></DIV
></DIV
><DIV
CLASS="SECT1"
><HR><H2
CLASS="SECT1"
><A
NAME="BACKUP-CRON-PROBLEM"
>7.4. The Problem</A
></H2
><DIV
CLASS="SECT2"
><H3
CLASS="SECT2"
><A
NAME="AEN691"
>7.4.1. Cron's environment</A
></H3
><P
>When a user submits a job with cron, their environment is not
preserved. This is reasonable since cron jobs are typically ongoing
and may be adversely affected if the user's environment changes subsequent
to the cron submission. Thus, a cron job should call a script that
set's up the correct environment before starting the user's desired
program. The 'at' command does this nicely.
</P
></DIV
><DIV
CLASS="SECT2"
><HR><H3
CLASS="SECT2"
><A
NAME="AEN694"
>7.4.2. Interactivity</A
></H3
><P
>When a job is started with cron, it runs as a background process.
No interaction with the program is possible (unless it is capable
of interacting via a FIFO or some such) except termination via its
pid. The only program that I know of that allows such interaction
and serves as a wrapper for other processes is 'screen'
</P
></DIV
><DIV
CLASS="SECT2"
><HR><H3
CLASS="SECT2"
><A
NAME="AEN697"
>7.4.3. Screen</A
></H3
><P
>There's one little problem with screen though. It expects to
attach to a terminal when it first starts. This won't happen under
cron so screen will fail. Fortunately, screen comes with a "start
detached" (-d) option.
</P
></DIV
></DIV
><DIV
CLASS="SECT1"
><HR><H2
CLASS="SECT1"
><A
NAME="BACKUP-CRON-SOLUTION"
>7.5. The Solution</A
></H2
><DIV
CLASS="SECT2"
><H3
CLASS="SECT2"
><A
NAME="AEN702"
>7.5.1. Briefly</A
></H3
><P
><P
></P
><UL
><LI
><P
>Use 'at' to run your usual mondoarchive command</P
></LI
><LI
><P
>Grab the script generated by 'at' and make a copy of it</P
></LI
><LI
><P
>Edit that script to use 'screen -m -d <your mondoarchive command>'</P
></LI
><LI
><P
>Run that script from your crontab</P
></LI
><LI
><P
>Use 'screen -r' to attach to the mondo screen to change CDs</P
></LI
><LI
><P
>Use '<CTRL>-a d' to detach the screen again</P
></LI
></UL
></P
></DIV
><DIV
CLASS="SECT2"
><HR><H3
CLASS="SECT2"
><A
NAME="AEN718"
>7.5.2. In Detail</A
></H3
><DIV
CLASS="SECT3"
><H4
CLASS="SECT3"
><A
NAME="AEN720"
>7.5.2.1. at</A
></H4
><P
>Use the 'at' command to submit your usual mondoarchive command.
My mondoarchive command is:</P
><DIV
CLASS="INFORMALTABLE"
><P
></P
><A
NAME="AEN723"
></A
><TABLE
BORDER="1"
CLASS="CALSTABLE"
><COL><TBODY
><TR
><TD
> # mondoarchive -D -Ow 10 -S /home/mondo/ -T /home/mondo/ -g \
-E "\"/home/cdaly/GIS/W2K /home/mondo/\"" -9 </TD
></TR
></TBODY
></TABLE
><P
></P
></DIV
><P
> To submit the mondoarchive command with 'at' do:</P
><DIV
CLASS="INFORMALTABLE"
><P
></P
><A
NAME="AEN729"
></A
><TABLE
BORDER="1"
CLASS="CALSTABLE"
><COL><TBODY
><TR
><TD
> # at now + 5 min
mondoarchive -D -Ow 10 -S /home/mondo/ -T /home/mondo/ -g \
-E "\"/home/cdaly/GIS/W2K /home/mondo/\"" -9
<CTRL>-d</TD
></TR
></TBODY
></TABLE
><P
></P
></DIV
><P
> This generates a script in /var/spool/at/ which sets up your
environment and runs your command. Grab this script to become your
cron job.
</P
></DIV
><DIV
CLASS="SECT3"
><HR><H4
CLASS="SECT3"
><A
NAME="AEN735"
>7.5.2.2. Grab the 'at' script</A
></H4
><P
> Make a copy of the script generated by the 'at' command to use
as the basis for your cron job.
</P
><DIV
CLASS="INFORMALTABLE"
><P
></P
><A
NAME="AEN738"
></A
><TABLE
BORDER="1"
CLASS="CALSTABLE"
><COL><TBODY
><TR
><TD
> grep mondo /var/spool/at/* </TD
></TR
><TR
><TD
>cp /var/spool/at/<file-from-grep> /root/mondo-cronscript</TD
></TR
></TBODY
></TABLE
><P
></P
></DIV
><P
> You'll need to edit this.</P
></DIV
><DIV
CLASS="SECT3"
><HR><H4
CLASS="SECT3"
><A
NAME="AEN746"
>7.5.2.3. Edit mondo-cronscript</A
></H4
><P
>To use screen, you'll need to edit the cronscript and add the
screen command. My mondo-cronscript looks like:</P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="SCREEN"
> #!/bin/sh
# atrun uid=0 gid=0
# mail cdaly 0 umask 22
PWD=/root; export PWD
XAUTHORITY=/root/.xauthyOrD4f; export XAUTHORITY
HOSTNAME=bofh.irmet.ie; export HOSTNAME
PVM_RSH=/usr/bin/rsh; export PVM_RSH
QTDIR=/usr/lib/qt-2.3.1; export QTDIR
LESSOPEN=\|/usr/bin/lesspipe.sh\ %s; export LESSOPEN
XPVM_ROOT=/usr/share/pvm3/xpvm; export XPVM_ROOT
KDEDIR=/usr; export KDEDIR
USER=root; export USER
LS_COLORS=no=00:fi=00:di=01\;34:ln=01\;36:pi=40\;33:so=01\;35:bd=40\;33\;01:cd=40\;33\;01:or=01\;05\;37\;41:mi=01\;05\;37\;41:ex=01\;32:\*.cmd=01\;32:\*.exe=01\;32:\*.com=01\;32:\*.btm=01\;32:\*.bat=01\;32:\*.sh=01\;32:\*.csh=01\;32:\*.tar=01\;31:\*.tgz=01\;31:\*.arj=01\;31:\*.taz=01\;31:\*.lzh=01\;31:\*.zip=01\;31:\*.z=01\;31:\*.Z=01\;31:\*.gz=01\;31:\*.bz2=01\;31:\*.bz=01\;31:\*.tz=01\;31:\*.rpm=01\;31:\*.cpio=01\;31:\*.jpg=01\;35:\*.gif=01\;35:\*.bmp=01\;35:\*.xbm=01\;35:\*.xpm=01\;35:\*.png=01\;35:\*.tif=01\;35:; export LS_COLORS
MACHTYPE=i386-redhat-linux-gnu; export MACHTYPE
MAIL=/var/spool/mail/root; export MAIL
INPUTRC=/etc/inputrc; export INPUTRC
BASH_ENV=/root/.bashrc; export BASH_ENV
LANG=en_US; export LANG
LOGNAME=root; export LOGNAME
SHLVL=1; export SHLVL
II_SYSTEM=/usr/local/ingres; export II_SYSTEM
USERNAME=root; export USERNAME
HOSTTYPE=i386; export HOSTTYPE
OSTYPE=linux-gnu; export OSTYPE
HISTSIZE=1000; export HISTSIZE
LAMHELPFILE=/etc/lam/lam-helpfile; export LAMHELPFILE
PVM_ROOT=/usr/share/pvm3; export PVM_ROOT
HOME=/root; export HOME
SSH_ASKPASS=/usr/libexec/openssh/gnome-ssh-askpass;
export SSH_ASKPASS
PATH=/usr/local/ingres/ingres/bin:/usr/local/ingres/ingres/utility:/usr/kerberos/sbin:/usr/kerberos/bin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin:/usr/bin/X11:/usr/X11R6/bin:/root/bin; export PATH
cd /root || {
echo 'Execution directory inaccessible' >&2
exit 1
}
screen -m -d mondoarchive -D -Ow 10 -S /home/mondo/ \
-T /home/mondo/ -g -E "\"/home/cdaly/GIS/W2K /home/mondo/\"" -9
#done </PRE
></TD
></TR
></TABLE
><P
> The crucial line is this one:</P
><DIV
CLASS="INFORMALTABLE"
><P
></P
><A
NAME="AEN751"
></A
><TABLE
BORDER="1"
CLASS="CALSTABLE"
><COL><TBODY
><TR
><TD
> screen -m -d mondoarchive -D -Ow 10 -S /home/mondo/ -T /home/mondo/ -g -E "\"/home/cdaly/GIS/W2K /home/mondo/\"" -9</TD
></TR
></TBODY
></TABLE
><P
></P
></DIV
><P
>This uses 'screen -m -d' to <SPAN
CLASS="QUOTE"
>"-m -d Start screen in "detached" mode. This creates a new session
but doesn't attach to it. This is useful for system startup scripts.
(From 'man screen')"</SPAN
> </P
><P
> When screen starts, it will be in the background and "detached".</P
></DIV
><DIV
CLASS="SECT3"
><HR><H4
CLASS="SECT3"
><A
NAME="AEN759"
>7.5.2.4. Run the thing with cron</A
></H4
><P
> To get the whole thing running, do:</P
><DIV
CLASS="INFORMALTABLE"
><P
></P
><A
NAME="AEN762"
></A
><TABLE
BORDER="1"
CLASS="CALSTABLE"
><COL><TBODY
><TR
><TD
> crontab -e
</TD
></TR
></TBODY
></TABLE
><P
></P
></DIV
><P
>and add the following lines:</P
><DIV
CLASS="INFORMALTABLE"
><P
></P
><A
NAME="AEN768"
></A
><TABLE
BORDER="1"
CLASS="CALSTABLE"
><COL><TBODY
><TR
><TD
># run mondoarchive at 23:59 weekdays </TD
></TR
><TR
><TD
>59 23 * * 1-5 /root/mondo-cronscript</TD
></TR
></TBODY
></TABLE
><P
></P
></DIV
><P
> Your mondoarchive job will run at 23:59 monday-friday.</P
><P
>DON'T FORGET TO CHANGE TAPES!</P
></DIV
><DIV
CLASS="SECT3"
><HR><H4
CLASS="SECT3"
><A
NAME="AEN777"
>7.5.2.5. Getting at it...</A
></H4
><P
>Once your cron job is running regularly, you'll want to get to
it to change tapes and check status etc.</P
><DIV
CLASS="INFORMALTABLE"
><P
></P
><A
NAME="AEN780"
></A
><TABLE
BORDER="1"
CLASS="CALSTABLE"
><COL><TBODY
><TR
><TD
>screen -r </TD
></TR
></TBODY
></TABLE
><P
></P
></DIV
><P
>attaches to the running screen where you can change CDs etc</P
><DIV
CLASS="INFORMALTABLE"
><P
></P
><A
NAME="AEN786"
></A
><TABLE
BORDER="1"
CLASS="CALSTABLE"
><COL><TBODY
><TR
><TD
><CTRL>-a d </TD
></TR
></TBODY
></TABLE
><P
></P
></DIV
><P
>detaches the running screen again.</P
></DIV
><DIV
CLASS="SECT3"
><HR><H4
CLASS="SECT3"
><A
NAME="AEN792"
>7.5.2.6. Caveat</A
></H4
><P
>The script generated by 'at' is unique to the user/machine combination.
You MUST regenerate it on each machine where it will be used. Using
the one above will NOT work for you. MAKE YOUR OWN!</P
></DIV
></DIV
></DIV
></DIV
><DIV
CLASS="CHAPTER"
><HR><H1
><A
NAME="COMPARE"
></A
>Chapter 8. Compare</H1
><P
>Before you trust your backup CD, make sure your BIOS can boot
CD (and that it is configured to do so).</P
><P
></P
><UL
><LI
><P
>Boot from the first CD.</P
></LI
><LI
><P
>Type:</P
></LI
></UL
><P
></P
><DIV
CLASS="INFORMALTABLE"
><P
></P
><A
NAME="AEN804"
></A
><TABLE
BORDER="1"
CLASS="CALSTABLE"
><COL><TBODY
><TR
><TD
> LILO: compare </TD
></TR
></TBODY
></TABLE
><P
></P
></DIV
><P
>Follow the on-screen instructions. This will compare your
backup against your original file system.</P
><P
>FYI, no bad archives have been created since May 2000. Having
said that, I would still encourage you to run Compare before
trusting the backups.</P
><P
>To view the file differences, look at the file
'/tmp/changed.txt'. Normal differences include logs and other
dynamic system files that changed during the time of the backup
process. If only a few files differ - e.g. files in /var, files
ending in '&#732;', logs, temporary files, /etc/mtab,
/etc/adjtimex - then you know the archives are good. Your logs will
change over time, too. Bear in mind that a difference between the
backup and the live copy does not indicate a flaw in Mondo. It
indicates that you or your filesystem changed the files, so the
backup is no longer 100% up to date. However, that is inevitable,
as your filesystem changes from moment to moment (which is why you
back it up regularly).</P
></DIV
><DIV
CLASS="CHAPTER"
><HR><H1
><A
NAME="RESTORE"
></A
>Chapter 9. Restore</H1
><DIV
CLASS="SECT1"
><H2
CLASS="SECT1"
><A
NAME="RESTORE-OVERVIEW"
>9.1. Overview</A
></H2
><P
>I hope you don't have to restore from scratch very often.
It's nerve-wracking until you realize that Mondo's restore engine
is very reliable.</P
><P
>If you find that you cannot make your PC boot from the CD,
take heart: the first backup media of each set contains disk
images to give you the same functionality as this media (minus the
archives, of course) on other boot media. Remember, your Mondo CD is a
fully functional CD-based mini-distribution as well as a recovery
CD.</P
><P
>You can choose from the following modes:</P
><P
></P
><DIV
CLASS="VARIABLELIST"
><DL
><DT
>Interactive</DT
><DD
><P
>Restore step-by-step, or restore a subset of the
archives. This is the method you should mainly use for your
recovery needs.</P
></DD
><DT
>Nuke</DT
><DD
><P
>Wipe your drives and restore everything,
automatically and unattended. Warning: This does exactly what is
says, so be careful using it.</P
></DD
><DT
>Expert</DT
><DD
><P
>Boot to a shell prompt. If you want to do anything
creative, you should boot into Expert Mode. It's called expert, I
think that says it all.</P
></DD
></DL
></DIV
><P
>If the CD is not found during the initial restore CD boot
attempt, reboot the PC a second time prior to reporting failure.
Occasional timing errors and hardware/software/system conflicts do
occur.</P
></DIV
><DIV
CLASS="SECT1"
><HR><H2
CLASS="SECT1"
><A
NAME="RESTORE-TIPS"
>9.2. Tips and Tricks</A
></H2
><P
>Ideally, restore your system to a spare hard drive to test
the integrity and reliability of your disks. To do that, either
edit your mountlist to make the devices point to your spare hard
drive, or swap your hard drive cables between boots.</P
><P
>At a bare minimum, compare your CD against your file system
before you decide whether to trust them.</P
><P
>To test Mondo's ability to handle your LILO or GRUB boot
loader and accompanying configuration file:</P
><P
></P
><UL
><LI
><P
>Boot from the backup CD into Expert Mode</P
></LI
><LI
><P
>Type:</P
></LI
></UL
><P
></P
><DIV
CLASS="INFORMALTABLE"
><P
></P
><A
NAME="AEN844"
></A
><TABLE
BORDER="1"
CLASS="CALSTABLE"
><COL><TBODY
><TR
><TD
> bash# mondorestore -Z mbr </TD
></TR
></TBODY
></TABLE
><P
></P
></DIV
><P
></P
><UL
><LI
><P
>To fix any mess it made (not that it should) type:</P
></LI
></UL
><P
></P
><DIV
CLASS="INFORMALTABLE"
><P
></P
><A
NAME="AEN853"
></A
><TABLE
BORDER="1"
CLASS="CALSTABLE"
><COL><TBODY
><TR
><TD
> bash# mount-me</TD
></TR
><TR
><TD
> bash# chroot /mnt/RESTORING
</TD
></TR
><TR
><TD
> </TD
></TR
><TR
><TD
>bash# lilo OR grub-install '(hd0)'
</TD
></TR
><TR
><TD
>bash# exit</TD
></TR
><TR
><TD
> bash# unmount-me </TD
></TR
></TBODY
></TABLE
><P
></P
></DIV
><P
></P
><UL
><LI
><P
>If it did not work then please copy /tmp/mondorestore.log to
to your hard disk, USB key, ..., gzip it and e-mail it to the
<A
HREF="http://lists.sourceforge.net/lists/listinfo/mondo-devel"
TARGET="_top"
>mondorescue mailing list</A
>.</P
></LI
></UL
><DIV
CLASS="SECT2"
><HR><H3
CLASS="SECT2"
><A
NAME="AEN872"
>9.2.1. Barebones (Nuke) Restore</A
></H3
><P
>Imagine that your hard drives happen to be wiped,
deliberately or accidentally. Or, imagine that you want to clone
your existing operating system. In either case, you want to run in
Nuke Mode.</P
><P
>If you want to wipe everything and restore your whole system
from CD, please:</P
><P
></P
><UL
><LI
><P
>Use the -H option when invoking mondoarchive</P
></LI
><LI
><P
>Boot from the first Mondo CD</P
></LI
><LI
><P
>Press RESTORE<enter></P
></LI
><LI
><P
>Insert the subsequent CD when asked</P
></LI
><LI
><P
>Watch the screen for errors</P
></LI
></UL
><P
>That's it. The restoration process for tape or NFS users is
similarly easy: just boot, answer the on-screen prompts, and
wait.</P
><P
>Now, should something go wrong, you will be able to examine
/tmp/mondorestore.log to see what happened. All is not lost. You
can fdisk and format the partitions yourself, using the tools that
come with the CD. You can then run mondorestore in Interactive Mode
and say 'no' when asked if you want Mondo to partition/format your
drives.</P
><P
>If you want to see exactly what Mondo is doing while it is
restoring, press <Alt><left cursor> to view its
logfile, in a virtual console, scrolling past.</P
></DIV
><DIV
CLASS="SECT2"
><HR><H3
CLASS="SECT2"
><A
NAME="AEN890"
>9.2.2. Interactive Restore</A
></H3
><P
>Interactive Mode is for people who have lost a subset of data
from their live file system, or perhaps who have lost some data
from their latest backup and want to restore a subset of data from
an earlier backup. If you want to restore only some files or if you
do not want to prep/format your drives, then you should boot into
Interactive Mode. The interactive mode will provide an 'Editing
mountlist screen' that allows you to setup a different disk
geometry.</P
><P
>To move up and down between partitions in the 'Editing
mountlist screen', use the Up and Down arrows. To move between the
main window and the buttons at the bottom, use the Left and Right
cursor keys. TAB shifts focus from one screen item to the other in
a haphazard fashion, owing to the complexities of the Newt
library.</P
><P
>If you want to restore selectively, just press <enter>
and follow the on-screen instructions. You will be asked to say
yes/no to a range of questions.</P
><P
>If you are planning to modify your partition table, you would
do well to read up on the partition layout and the use of fdisk, it
gives you some pointers on how to best lay out partitions.
You can find a good guide at the
<A
HREF="http://www.tldp.org/HOWTO/Partition/index.html"
TARGET="_top"
>Partition HOWTO</A
></P
><P
>If you want to restore a subset of the backup then:</P
><P
></P
><UL
><LI
><P
>Boot from the CD</P
></LI
><LI
><P
>Type:</P
></LI
></UL
><P
></P
><DIV
CLASS="INFORMALTABLE"
><P
></P
><A
NAME="AEN904"
></A
><TABLE
BORDER="1"
CLASS="CALSTABLE"
><COL><TBODY
><TR
><TD
> bash# interactive </TD
></TR
></TBODY
></TABLE
><P
></P
></DIV
><P
></P
><UL
><LI
><P
>Then, after booting, answer the questions as follows:</P
></LI
></UL
><P
></P
><DIV
CLASS="INFORMALTABLE"
><P
></P
><A
NAME="AEN913"
></A
><TABLE
BORDER="1"
CLASS="CALSTABLE"
><COL><TBODY
><TR
><TD
> Do you want to partition your devices? no
</TD
></TR
><TR
><TD
>Do you want to format them? no
</TD
></TR
><TR
><TD
>Do you want to restore everything? no
</TD
></TR
><TR
><TD
>Do you want to restore something? yes
</TD
></TR
><TR
><TD
>Which path do you want to restore? /mydata [e.g.]
</TD
></TR
><TR
><TD
>Do you want to run LILO to setup your boot sectors? Yes </TD
></TR
></TBODY
></TABLE
><P
></P
></DIV
></DIV
><DIV
CLASS="SECT2"
><HR><H3
CLASS="SECT2"
><A
NAME="AEN928"
>9.2.3. Expert Restore</A
></H3
><P
>If you are planning to modify your partition table, you would
do well to read up on the partition layout and the use of fdisk, it
gives you some could pointers on how to best lay out partitions.
You can find good a guide at the
<A
HREF="http://www.ibiblio.org/pub/Linux/docs/HOWTO/mini/Partition/index.html"
TARGET="_top"
>Partition HOWTO</A
></P
><P
>To restore manually, please:</P
><P
></P
><UL
><LI
><P
>Boot from the first CD, then type:</P
></LI
></UL
><P
></P
><DIV
CLASS="INFORMALTABLE"
><P
></P
><A
NAME="AEN937"
></A
><TABLE
BORDER="1"
CLASS="CALSTABLE"
><COL><TBODY
><TR
><TD
> bash# expert </TD
></TR
></TBODY
></TABLE
><P
></P
></DIV
><P
></P
><UL
><LI
><P
>Then do whatever you like. :) You may type the following, of
course:</P
></LI
></UL
><P
></P
><DIV
CLASS="INFORMALTABLE"
><P
></P
><A
NAME="AEN946"
></A
><TABLE
BORDER="1"
CLASS="CALSTABLE"
><COL><TBODY
><TR
><TD
> bash# mondorestore </TD
></TR
></TBODY
></TABLE
><P
></P
></DIV
></DIV
><DIV
CLASS="SECT2"
><HR><H3
CLASS="SECT2"
><A
NAME="AEN951"
>9.2.4. Modified partitions - Restore to a different disk geometry</A
></H3
><P
>One of the nice things about Mondo is that it lets you wipe
your existing system and restore it in any layout you like (within
reason). You can move from non-RAID to RAID,install and utilize
additional drives, move from ext2 to ReiserFS, etc., all without
risking the loss of data.</P
><P
>If the user excluded a particular partition from backup and
specifically excluded it from the mountlist itself using -E then
Mondo will insert a small (32MB) partition at restore-time, in
order to avoid having to re-jig fstab, the partition table,
etc.</P
><P
>To do this:</P
><P
></P
><UL
><LI
><P
>Boot into Expert Mode, then type:</P
></LI
></UL
><P
></P
><DIV
CLASS="INFORMALTABLE"
><P
></P
><A
NAME="AEN960"
></A
><TABLE
BORDER="1"
CLASS="CALSTABLE"
><COL><TBODY
><TR
><TD
> bash# mondorestore </TD
></TR
></TBODY
></TABLE
><P
></P
></DIV
><P
></P
><UL
><LI
><P
>(edit the mountlist using the on-screen editor)</P
></LI
></UL
><P
>If you want to move from ext2 to ReiserFS, you can do it here
(so long as your kernel supports ReiserFS). Ditto for XFS, JFS or
ext3, ext4.</P
><P
>Mondorestore will try to modify your /etc/fstab to reflect
changes you have made to the mountlist. If you are not using LILO,
you can still create your own /mnt/RESTORING/etc/lilo.conf and run
lilo -r /mnt/RESTORING to configure your boot sectors and Master
Boot Record.</P
><P
>Mondo (technically, Mindi on behalf of Mondo) creates a file
called a mountlist. This can be found on the ramdisk at
/tmp/mountlist.txt; it looks something like this:</P
><P
></P
><DIV
CLASS="INFORMALTABLE"
><P
></P
><A
NAME="AEN972"
></A
><TABLE
BORDER="1"
CLASS="CALSTABLE"
><COL><TBODY
><TR
><TD
> /dev/hda1 /mnt/windows vfat 4096000</TD
></TR
><TR
><TD
> /dev/hda5 / reiserfs 6023000</TD
></TR
><TR
><TD
> /dev/hda6 /tmp xfs 955000</TD
></TR
><TR
><TD
> /dev/hda7 /usr ext3 4096000 </TD
></TR
></TBODY
></TABLE
><P
></P
></DIV
><P
>It is fairly easy to understand the list. Each line refers to
a single device/partition. The line format is:</P
><P
></P
><DIV
CLASS="INFORMALTABLE"
><P
></P
><A
NAME="AEN985"
></A
><TABLE
BORDER="1"
CLASS="CALSTABLE"
><COL><TBODY
><TR
><TD
> <device> <partition> <format> <Kilobytes> </TD
></TR
></TBODY
></TABLE
><P
></P
></DIV
><P
>If you have added a hard drive and want to take advantage of
the additional space, you could amend the above mountlist to
read:</P
><P
></P
><DIV
CLASS="INFORMALTABLE"
><P
></P
><A
NAME="AEN992"
></A
><TABLE
BORDER="1"
CLASS="CALSTABLE"
><COL><TBODY
><TR
><TD
> /dev/hda1 /mnt/windows vfat 6096000</TD
></TR
><TR
><TD
> /dev/hda5 / reiserfs 9123000</TD
></TR
><TR
><TD
> /dev/hda6 /tmp xfs 955000</TD
></TR
><TR
><TD
> /dev/hdb1 /usr ext3 8192000</TD
></TR
><TR
><TD
> /dev/hdb2 /home xfs 8192000 </TD
></TR
></TBODY
></TABLE
><P
></P
></DIV
><P
>This assumes that your old hard drive is /dev/hda and the new
hard drive is /dev/hdb.</P
><P
>Or, if you want to add RAID support, create a new
/etc/raidtab on the ramdisk (which is beyond the scope of this
HOWTO) and then write a mountlist like this:</P
><P
></P
><DIV
CLASS="INFORMALTABLE"
><P
></P
><A
NAME="AEN1008"
></A
><TABLE
BORDER="1"
CLASS="CALSTABLE"
><COL><TBODY
><TR
><TD
> /dev/hda1 /mnt/windows vfat 6096000</TD
></TR
><TR
><TD
> /dev/md0 / reiserfs 9123000</TD
></TR
><TR
><TD
> /dev/md1 /tmp xfs 955000</TD
></TR
><TR
><TD
> /dev/md2 /usr ext3 8192000</TD
></TR
><TR
><TD
> /dev/md3 /home xfs 8192000 </TD
></TR
></TBODY
></TABLE
><P
></P
></DIV
><P
>So long as your /etc/raidtab file is sane, Mondo can
automatically partition and format your disks for you, including
the RAID devices.</P
><P
>Once you have finished editing /tmp/mountlist.txt using
mondorestore's built-in editor then you may choose 'OK'. Please
note that this will not write anything to your hard disk. You will
only reformat or repartition your disks if you say 'Yes' when asked
if you want to do those things.</P
></DIV
><DIV
CLASS="SECT2"
><HR><H3
CLASS="SECT2"
><A
NAME="AEN1023"
>9.2.5. Advanced</A
></H3
><P
>It is now possible to restore to a live filesystem using
Mondo. In other words, you do not have to boot your PC from your
media in order to restore files. Mondo was originally designed
for disaster recovery - situations in which you cannot boot your
PC. If you can boot your PC, it is not really a disaster, is it? :)
Well, if you have wiped out your priceless collection of "MTV's
Bjork Unplugged" MP3's, perhaps it is. Anyway, just type this as
root</P
><P
></P
><DIV
CLASS="INFORMALTABLE"
><P
></P
><A
NAME="AEN1027"
></A
><TABLE
BORDER="1"
CLASS="CALSTABLE"
><COL><TBODY
><TR
><TD
> bash# mondorestore </TD
></TR
></TBODY
></TABLE
><P
></P
></DIV
><P
></P
><DIV
CLASS="INFORMALTABLE"
><P
></P
><A
NAME="AEN1033"
></A
><TABLE
BORDER="1"
CLASS="CALSTABLE"
><COL><COL><TBODY
><TR
><TD
><A
HREF="images/rest1.png"
TARGET="_top"
><SPAN
CLASS="INLINEMEDIAOBJECT"
><IMG
SRC="images/rest1-mini.png"></SPAN
></A
></TD
><TD
>Choose your type of backup media. The live restoration process is
very similar to what you'll experience if you type mondorestore
with no parameters after booting from a Mondo media.</TD
></TR
><TR
><TD
><A
HREF="images/rest2.png"
TARGET="_top"
><SPAN
CLASS="INLINEMEDIAOBJECT"
><IMG
SRC="images/rest2-mini.png"></SPAN
></A
></TD
><TD
>Hit 'OK' when you have inserted the tape/CD. If you generated a
tape backup, the tape itself should be enough. If you generated a
CD backup, the first CD should be enough. Otherwise, you may need
the boot media.</TD
></TR
><TR
><TD
><A
HREF="images/rest3.png"
TARGET="_top"
><SPAN
CLASS="INLINEMEDIAOBJECT"
><IMG
SRC="images/rest3-mini.png"></SPAN
></A
></TD
><TD
>Flag the files and directories you wish to restore. Use the 'More'
and 'Less' buttons to open and close subdirectories.</TD
></TR
><TR
><TD
><A
HREF="images/rest4.png"
TARGET="_top"
><SPAN
CLASS="INLINEMEDIAOBJECT"
><IMG
SRC="images/rest4-mini.png"></SPAN
></A
></TD
><TD
>Specify the location to restore the files to. In general, '/' is
appropriate. If you do not want to overwrite newer versions of the
files you are restoring then specify /tmp/BKP or similar as the
restore path.</TD
></TR
><TR
><TD
><A
HREF="images/rest5.png"
TARGET="_top"
><SPAN
CLASS="INLINEMEDIAOBJECT"
><IMG
SRC="images/rest5-mini.png"></SPAN
></A
></TD
><TD
>Mondorestore will retrieve configuration information from the
media. (The sample screen is for tape users. CD users will see
something different.)</TD
></TR
><TR
><TD
><A
HREF="images/rest6.png"
TARGET="_top"
><SPAN
CLASS="INLINEMEDIAOBJECT"
><IMG
SRC="images/rest6-mini.png"></SPAN
></A
></TD
><TD
>Data will be restored to the hard disk - first the regular files,
then any big (32MB or greater) files in the restore set.</TD
></TR
></TBODY
></TABLE
><P
></P
></DIV
><P
>I hope this manual was useful for you.</P
></DIV
></DIV
></DIV
><DIV
CLASS="CHAPTER"
><HR><H1
><A
NAME="FAQ"
></A
>Chapter 10. FAQ</H1
><DIV
CLASS="SECT1"
><H2
CLASS="SECT1"
><A
NAME="FAQ-OVERVIEW"
>10.1. Overview</A
></H2
><P
>Are the errors from Mindi or Mondo? Look at
/var/log/mondoarchive.log or /var/log/mindi.log (if run alone). Pipe
screen errors which relate to the creation of boot disk(s) and or
data disk(s) to a text file.</P
><P
>See the <A
HREF="http://www.mondorescue.org"
TARGET="_top"
>MondoRescue</A
> for details. If you are going to e-mail
<A
HREF="http://lists.sourceforge.net/lists/listinfo/mondo-devel"
TARGET="_top"
>mondorescue mailing list</A
> then
please attach that text file (zipped!) and give :</P
><P
></P
><UL
><LI
><P
>Your kernel version (uname -a)</P
></LI
><LI
><P
>Your Linux distro's name and version (/etc/distro-release)</P
></LI
><LI
><P
>Whether your kernel supports initrd and loopfs; it should! (grep -E '^CONFIG_BLK_DEV_LOOP|^CONFIG_BLK_DEV_INITRD' /usr/src/linux/.config </P
></LI
><LI
><P
>What sort of PC you are using, including hard disk configurations (results of dmidecode, lshw, fdisk -l are useful here)</P
></LI
></UL
><P
>Mondo is freely available under the GPL and you are given it for no charge.
When you e-mail the <A
HREF="http://lists.sourceforge.net/lists/listinfo/mondo-devel"
TARGET="_top"
>mondorescue mailing list</A
>, please bear that in mind.</P
></DIV
><DIV
CLASS="SECT1"
><HR><H2
CLASS="SECT1"
><A
NAME="FAQ-GENERAL"
>10.2. General Questions</A
></H2
><DIV
CLASS="QANDASET"
><DL
><DT
>10.2.1. <A
HREF="#AEN1102"
>Q: What is "Mindi"?</A
></DT
><DT
>10.2.2. <A
HREF="#AEN1107"
>Q: Why is it called "Mondo"?</A
></DT
><DT
>10.2.3. <A
HREF="#AEN1112"
>Q: Mondo does not work on my system. It
keels over and dies. What's wrong?</A
></DT
><DT
>10.2.4. <A
HREF="#AEN1120"
>Q: What if the error is in Mindi?</A
></DT
><DT
>10.2.5. <A
HREF="#AEN1127"
>Q: Can I trust Mondo?</A
></DT
><DT
>10.2.6. <A
HREF="#AEN1133"
>Q: How do I report a bug?</A
></DT
><DT
>10.2.7. <A
HREF="#AEN1139"
>Q: I think Mondo should (...insert
suggestion here...) and I have rewritten it accordingly. Would you
like to see my patch?</A
></DT
><DT
>10.2.8. <A
HREF="#AEN1144"
>Q: I think Mondo should (...insert
suggestion here...); will you incorporate this feature for me,
please?</A
></DT
><DT
>10.2.9. <A
HREF="#AEN1150"
>Q: Mondo says, "XXX is missing," and
then terminates. What's wrong?</A
></DT
><DT
>10.2.10. <A
HREF="#AEN1156"
>Q: Can Mondo handle multi-CD backups and
restores?</A
></DT
><DT
>10.2.11. <A
HREF="#AEN1161"
>Q: Can Mondo handle Linux/Windows
dual-boot systems?</A
></DT
><DT
>10.2.12. <A
HREF="#AEN1166"
>Q: Can Mondo backup Windows-only
systems?</A
></DT
><DT
>10.2.13. <A
HREF="#AEN1171"
>Q: Does Mondo support LVM?</A
></DT
><DT
>10.2.14. <A
HREF="#AEN1177"
>Q: What if I don't use LILO? What if I
use GRUB?</A
></DT
><DT
>10.2.15. <A
HREF="#AEN1182"
>Q: I get the error, 'Cannot find
/tmp/dev.0' or 'Cannot mount device 0x0701'; what do I do?</A
></DT
><DT
>10.2.16. <A
HREF="#AEN1188"
>Q: Can I create a Mondo CD and then use
it to create an archive of any OS on any PC?</A
></DT
><DT
>10.2.17. <A
HREF="#AEN1193"
>Q: Why do you insist on putting media
disk images on Mondo CD? They waste space and I never use them. The
CD works just fine, so why keep the media disk images?</A
></DT
><DT
>10.2.18. <A
HREF="#AEN1198"
>Q: Why doesn't the Mondo project have a
cool-looking animal logo?</A
></DT
><DT
>10.2.19. <A
HREF="#AEN1203"
>Q: Is there a Mondo user 'Code of
Conduct?</A
></DT
></DL
><DIV
CLASS="QANDAENTRY"
><DIV
CLASS="QUESTION"
><P
><A
NAME="AEN1102"
></A
><B
>10.2.1. </B
>Q: What is "Mindi"?</P
></DIV
><DIV
CLASS="ANSWER"
><P
><B
> </B
>A: Mindi, a.k.a. Mindi-Linux, makes a mini-distribution from
your kernel, modules, modules, tools and libraries. It can also
generate an El Torito 2.88/5.76MB boot disk image. Mondo uses Mindi to
create a mini-distro, then boots from it and runs on it.</P
></DIV
></DIV
><DIV
CLASS="QANDAENTRY"
><DIV
CLASS="QUESTION"
><P
><A
NAME="AEN1107"
></A
><B
>10.2.2. </B
>Q: Why is it called "Mondo"?</P
></DIV
><DIV
CLASS="ANSWER"
><P
><B
> </B
>A: The Teenage Mutant Ninja Turtles described cool things as
'mondo'. Hugo Rabson wasn't sure what to call this project. 'Faust' was one
idea he had, partly as a dig at his former boss who practically owned
him because of his legal status at the time. In the end, he chose
something short and distinctive.</P
></DIV
></DIV
><DIV
CLASS="QANDAENTRY"
><DIV
CLASS="QUESTION"
><P
><A
NAME="AEN1112"
></A
><B
>10.2.3. </B
>Q: Mondo does not work on my system. It
keels over and dies. What's wrong?</P
></DIV
><DIV
CLASS="ANSWER"
><P
><B
> </B
>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
of SuSE/SLES, some flavors of Slackware, etc.
The more distributions we support, the more moving targets we have to
hit. Please bear this in mind when e-mailing the list. :) If you
would like to help us by beta-testing Mondo (or Mindi) on your PC
then we would be very interested in working with you to work around
the eccentricities of your Linux distro. However, rest assured, 90%
of the bugs reported are actually symptoms of FooLinux X.Y's
unique way of doing things.</P
><P
>Please send a copy of <TT
CLASS="FILENAME"
>/var/log/mondoarchive.log</TT
> to the <A
HREF="http://lists.sourceforge.net/lists/listinfo/mondo-devel"
TARGET="_top"
>mondorescue mailing list</A
>
along with a description of your distro, your kernel, etc.
Oh, and before sending it, please try to read it.</P
></DIV
></DIV
><DIV
CLASS="QANDAENTRY"
><DIV
CLASS="QUESTION"
><P
><A
NAME="AEN1120"
></A
><B
>10.2.4. </B
>Q: What if the error is in Mindi?</P
></DIV
><DIV
CLASS="ANSWER"
><P
><B
> </B
>A: Please send a copy of <TT
CLASS="FILENAME"
>/var/log/mindi.log</TT
> to the <A
HREF="http://lists.sourceforge.net/lists/listinfo/mondo-devel"
TARGET="_top"
>mondorescue mailing list</A
>
along with a description of your distro, your kernel, etc.
Oh, and before sending it, please read it as it is much easier to understand it.</P
></DIV
></DIV
><DIV
CLASS="QANDAENTRY"
><DIV
CLASS="QUESTION"
><P
><A
NAME="AEN1127"
></A
><B
>10.2.5. </B
>Q: Can I trust Mondo?</P
></DIV
><DIV
CLASS="ANSWER"
><P
><B
> </B
>A: Mondo has generated reliable archives since May 2000.
Lost data occured by using bad CD-R disks and not verifying their
contents. Some users have not tried booting from their CD until
crunch time. Remember to boot into Compare Mode to verify the
backup before you trust it. If Mondo did not work, you would not be
reading this. If it does not work for you, your kernel is usually
the culprit. Check <A
HREF="#OVERVIEW-SYSRQ-KERNELREQ"
>Linux Kernel
support</A
> to see what your kernel should support. Please
e-mail the list if you need some help with this.</P
></DIV
></DIV
><DIV
CLASS="QANDAENTRY"
><DIV
CLASS="QUESTION"
><P
><A
NAME="AEN1133"
></A
><B
>10.2.6. </B
>Q: How do I report a bug?</P
></DIV
><DIV
CLASS="ANSWER"
><P
><B
> </B
>A: E-mail the bug report (mondo.err.xxxxx.tgz) to the <A
HREF="http://lists.sourceforge.net/lists/listinfo/mondo-devel"
TARGET="_top"
>mondorescue mailing list</A
>.
Ok you've read it already but it's really important if you want help.
If you don't send a logfile then there isn't a lot that we can do for you, so
PLEASE include a logfile at the very least.</P
></DIV
></DIV
><DIV
CLASS="QANDAENTRY"
><DIV
CLASS="QUESTION"
><P
><A
NAME="AEN1139"
></A
><B
>10.2.7. </B
>Q: I think Mondo should (...insert
suggestion here...) and I have rewritten it accordingly. Would you
like to see my patch?</P
></DIV
><DIV
CLASS="ANSWER"
><P
><B
> </B
>A: Absolutely! :-) The best way for you to make Mondo do what
you want is to modify it and then send the patch. That way, we
can all benefit.</P
></DIV
></DIV
><DIV
CLASS="QANDAENTRY"
><DIV
CLASS="QUESTION"
><P
><A
NAME="AEN1144"
></A
><B
>10.2.8. </B
>Q: I think Mondo should (...insert
suggestion here...); will you incorporate this feature for me,
please?</P
></DIV
><DIV
CLASS="ANSWER"
><P
><B
> </B
>A: Please enter the suggestion in our feature system at <A
HREF="http://www.mondorescue.org"
TARGET="_top"
>MondoRescue</A
></P
></DIV
></DIV
><DIV
CLASS="QANDAENTRY"
><DIV
CLASS="QUESTION"
><P
><A
NAME="AEN1150"
></A
><B
>10.2.9. </B
>Q: Mondo says, "XXX is missing," and
then terminates. What's wrong?</P
></DIV
><DIV
CLASS="ANSWER"
><P
><B
> </B
>A: A good Linux distribution should contain XXX but the
designers, in their infinite wisdom, decided not to include that
particular tool. Check <A
HREF="http://www.mondorescue.org/downloads.shtml#dependencies"
TARGET="_top"
>Related
Linux Packages</A
> and install the missing package. If that
fails, contact the vendor/distributor/manufacturer/designer of your
distro.</P
></DIV
></DIV
><DIV
CLASS="QANDAENTRY"
><DIV
CLASS="QUESTION"
><P
><A
NAME="AEN1156"
></A
><B
>10.2.10. </B
>Q: Can Mondo handle multi-CD backups and
restores?</P
></DIV
><DIV
CLASS="ANSWER"
><P
><B
> </B
>A: Yes, up to twenty CD per set. This 20-CD limit results
from laziness on mondorescue's part. I'll be removed in the future. However, if
your system occupies more than 20 CD, may it's time for another type of media ?</P
></DIV
></DIV
><DIV
CLASS="QANDAENTRY"
><DIV
CLASS="QUESTION"
><P
><A
NAME="AEN1161"
></A
><B
>10.2.11. </B
>Q: Can Mondo handle Linux/Windows
dual-boot systems?</P
></DIV
><DIV
CLASS="ANSWER"
><P
><B
> </B
>A: Yes. If your system currently boots into Linux or Windows
via LILO, you can backup and restore both OSes at the same time
using Mondo. If you are using NTFS then add the switch, '-x
<device>'.</P
></DIV
></DIV
><DIV
CLASS="QANDAENTRY"
><DIV
CLASS="QUESTION"
><P
><A
NAME="AEN1166"
></A
><B
>10.2.12. </B
>Q: Can Mondo backup Windows-only
systems?</P
></DIV
><DIV
CLASS="ANSWER"
><P
><B
> </B
>A: Not at the moment.</P
></DIV
></DIV
><DIV
CLASS="QANDAENTRY"
><DIV
CLASS="QUESTION"
><P
><A
NAME="AEN1171"
></A
><B
>10.2.13. </B
>Q: Does Mondo support LVM?</P
></DIV
><DIV
CLASS="ANSWER"
><P
><B
> </B
>A: Mondo supports LVM v1 and v2. Mondo backs up and restores your
existing setup but it does not make it easy for you to change your
LVM configuration, at the moment. You have to edit <TT
CLASS="FILENAME"
>/tmp/i-want-my-lvm</TT
> at boot-time
to do that.</P
></DIV
></DIV
><DIV
CLASS="QANDAENTRY"
><DIV
CLASS="QUESTION"
><P
><A
NAME="AEN1177"
></A
><B
>10.2.14. </B
>Q: What if I don't use LILO? What if I
use GRUB?</P
></DIV
><DIV
CLASS="ANSWER"
><P
><B
> </B
>A: GRUB is supported by Mondo.</P
></DIV
></DIV
><DIV
CLASS="QANDAENTRY"
><DIV
CLASS="QUESTION"
><P
><A
NAME="AEN1182"
></A
><B
>10.2.15. </B
>Q: I get the error, 'Cannot find
/tmp/dev.0' or 'Cannot mount device 0x0701'; what do I do?</P
></DIV
><DIV
CLASS="ANSWER"
><P
><B
> </B
>A: Please free up <TT
CLASS="FILENAME"
>/dev/loop0</TT
> using 'losetup /dev/loop0 -d' to
unmount that loop device. If your OS will not let you do that,
contact your local support group or Linux vendor.</P
></DIV
></DIV
><DIV
CLASS="QANDAENTRY"
><DIV
CLASS="QUESTION"
><P
><A
NAME="AEN1188"
></A
><B
>10.2.16. </B
>Q: Can I create a Mondo CD and then use
it to create an archive of any OS on any PC?</P
></DIV
><DIV
CLASS="ANSWER"
><P
><B
> </B
>A: Not yet. You can use Mondo to backup Linux or
Linux/Windows dual boot. One day, Mondo will let you backup
partitions it can't read or write, by treating each partition as
one long file to be backed up. This file will be chopped,
compressed and archived like any other big file.</P
></DIV
></DIV
><DIV
CLASS="QANDAENTRY"
><DIV
CLASS="QUESTION"
><P
><A
NAME="AEN1193"
></A
><B
>10.2.17. </B
>Q: Why do you insist on putting media
disk images on Mondo CD? They waste space and I never use them. The
CD works just fine, so why keep the media disk images?</P
></DIV
><DIV
CLASS="ANSWER"
><P
><B
> </B
>A: Because. It helped us in the past. If you
really, truly want them gone then please submit a patch to make
them optional.</P
></DIV
></DIV
><DIV
CLASS="QANDAENTRY"
><DIV
CLASS="QUESTION"
><P
><A
NAME="AEN1198"
></A
><B
>10.2.18. </B
>Q: Why doesn't the Mondo project have a
cool-looking animal logo?</P
></DIV
><DIV
CLASS="ANSWER"
><P
><B
> </B
>A: Excellent question! Please submit graphics of candidate
animal logos!</P
></DIV
></DIV
><DIV
CLASS="QANDAENTRY"
><DIV
CLASS="QUESTION"
><P
><A
NAME="AEN1203"
></A
><B
>10.2.19. </B
>Q: Is there a Mondo user 'Code of
Conduct?</P
></DIV
><DIV
CLASS="ANSWER"
><P
><B
> </B
>A: Yes. Read the HOWTO. Submit patches. Recommend realistic
improvements. Be courteous to other users on the discussion list.
Do not whine.</P
></DIV
></DIV
></DIV
></DIV
><DIV
CLASS="SECT1"
><HR><H2
CLASS="SECT1"
><A
NAME="FAQ-BOOTING"
>10.3. Booting and Kernel related Questions</A
></H2
><DIV
CLASS="QANDASET"
><DL
><DT
>10.3.1. <A
HREF="#AEN1211"
>Q: When I try to boot from the Mondo CD,
it says, "VFS: Unable to mount root fs." I am using an old Debian
distro. What do I do?</A
></DT
><DT
>10.3.2. <A
HREF="#AEN1217"
>Q: When I try to boot from the Mondo CD,
it says, "Cannot mount root fs - kernel panic," or something
similar. What do I do?</A
></DT
><DT
>10.3.3. <A
HREF="#AEN1223"
>Q: When I try to boot from the Mondo CD,
it says, "UPGRADE YOUR RAM". What does that mean?</A
></DT
><DT
>10.3.4. <A
HREF="#AEN1229"
>Q: When I try to boot from the Mondo CD,
it says something about not finding my CD-ROM drive and then it
blames the kernel. What does that mean?</A
></DT
><DT
>10.3.5. <A
HREF="#AEN1235"
>Q: The LILO Mondo media takes ages to
boot. How can I speed it up?</A
></DT
><DT
>10.3.6. <A
HREF="#AEN1240"
>Q: I made a Mondo CD using the failsafe
kernel (i.e. I said 'no' when Mondo asked if I wanted to use my own
kernel). It still doesn't boot. Help!</A
></DT
><DT
>10.3.7. <A
HREF="#AEN1246"
>Q: Why won't Mondo boot from my CD?
It says my kernel is flawed/outdated/ whatever, and when I wrote to
the ML, they told me the same thing... but I still don't get it. I
mean, my kernel works for everything else. Why not Mondo?</A
></DT
><DT
>10.3.8. <A
HREF="#AEN1252"
>Q: Why do I only need a boot disk if I'm
using a tape drive? Where are the data disks?</A
></DT
><DT
>10.3.9. <A
HREF="#AEN1258"
>Q: Why does it say, "Process accounting
FAILED" when I reboot?</A
></DT
><DT
>10.3.10. <A
HREF="#AEN1263"
>Q: Why does it say,
&#8220;request_module[block-major-1]: Root fs not mounted VFS:
Cannot open root device "100" or 01:00 Please append a correct
"root=" boot option kernel panic: VFS: Unable to mount root fs on
01:00&#8221; when i boot from the CD?</A
></DT
><DT
>10.3.11. <A
HREF="#AEN1269"
>Q: My tape drive
doesn't play nicely with Mondo at boot-time. What do I do?</A
></DT
></DL
><DIV
CLASS="QANDAENTRY"
><DIV
CLASS="QUESTION"
><P
><A
NAME="AEN1211"
></A
><B
>10.3.1. </B
>Q: When I try to boot from the Mondo CD,
it says, "VFS: Unable to mount root fs." I am using an old Debian
distro. What do I do?</P
></DIV
><DIV
CLASS="ANSWER"
><P
><B
> </B
>A: Ask Debian's designers why they, unlike every other distro
I can find, have included cramfs and other 'goodies' with their
kernel. In the meantime, please use '-k FAILSAFE' in your command
line when calling Mondo.</P
><P
>A: From Sarge onwards, all stock Debian 2.6 kernels should work fine. If
you are still using stock Debian 2.4 kernels, FAILSAFE is the way to go.
Of course, if you have compiled your own kernel and experience problems,
FAILSAFE is the way to go as well, but this is not really
Debian-specific.</P
></DIV
></DIV
><DIV
CLASS="QANDAENTRY"
><DIV
CLASS="QUESTION"
><P
><A
NAME="AEN1217"
></A
><B
>10.3.2. </B
>Q: When I try to boot from the Mondo CD,
it says, "Cannot mount root fs - kernel panic," or something
similar. What do I do?</P
></DIV
><DIV
CLASS="ANSWER"
><P
><B
> </B
>A: Recompile your kernel (or use '-k FAILSAFE'). Take a look
at <A
HREF="#OVERVIEW-SYSRQ-KERNELREQ"
>Linux Kernel support</A
> to
see what your kernel must support.</P
></DIV
></DIV
><DIV
CLASS="QANDAENTRY"
><DIV
CLASS="QUESTION"
><P
><A
NAME="AEN1223"
></A
><B
>10.3.3. </B
>Q: When I try to boot from the Mondo CD,
it says, "UPGRADE YOUR RAM". What does that mean?</P
></DIV
><DIV
CLASS="ANSWER"
><P
><B
> </B
>A: Recompile your kernel and add Virtual memory file system
support. Take a look at <A
HREF="#OVERVIEW-SYSRQ-KERNELREQ"
>Linux
Kernel support</A
> to see what your kernel must support. (Of
course, if your PC has less than 64MB of RAM, you could always...
what's the phrase? I know, upgrade your RAM!)</P
></DIV
></DIV
><DIV
CLASS="QANDAENTRY"
><DIV
CLASS="QUESTION"
><P
><A
NAME="AEN1229"
></A
><B
>10.3.4. </B
>Q: When I try to boot from the Mondo CD,
it says something about not finding my CD-ROM drive and then it
blames the kernel. What does that mean?</P
></DIV
><DIV
CLASS="ANSWER"
><P
><B
> </B
>A: Your kernel must support initrd, loopfs, IDE|SCSI|USB CD-ROM's, and
ramdisks. Take a look at <A
HREF="#OVERVIEW-SYSRQ-KERNELREQ"
>Linux
Kernel support</A
> to see what your kernel must support. If
your kernel does not support these things, Mondo will not boot from
your CD. However, when running Mindi, you may choose to use _its_
kernel instead of your own.</P
></DIV
></DIV
><DIV
CLASS="QANDAENTRY"
><DIV
CLASS="QUESTION"
><P
><A
NAME="AEN1235"
></A
><B
>10.3.5. </B
>Q: The LILO Mondo media takes ages to
boot. How can I speed it up?</P
></DIV
><DIV
CLASS="ANSWER"
><P
><B
> </B
>A: Edit mindi (it's a shell script, btw) and change
LILO_OPTIONS="" to LILO_OPTIONS="-c". This enables map compaction
in lilo and speeds up booting, for more info see the lilo man
page.</P
></DIV
></DIV
><DIV
CLASS="QANDAENTRY"
><DIV
CLASS="QUESTION"
><P
><A
NAME="AEN1240"
></A
><B
>10.3.6. </B
>Q: I made a Mondo CD using the failsafe
kernel (i.e. I said 'no' when Mondo asked if I wanted to use my own
kernel). It still doesn't boot. Help!</P
></DIV
><DIV
CLASS="ANSWER"
><P
><B
> </B
>A: OK, now that is a bug. :-) I included a kernel with Mondo
(technically, with Mindi, which Mondo uses) to make sure that users
could use Mondo despite flaws in their own kernels. If you are
using Mondo/Mindi's kernel but still cannot boot from your Mondo CD
then please e-mail the <A
HREF="http://lists.sourceforge.net/lists/listinfo/mondo-devel"
TARGET="_top"
>mondorescue mailing list</A
>.</P
></DIV
></DIV
><DIV
CLASS="QANDAENTRY"
><DIV
CLASS="QUESTION"
><P
><A
NAME="AEN1246"
></A
><B
>10.3.7. </B
>Q: Why won't Mondo boot from my CD?
It says my kernel is flawed/outdated/ whatever, and when I wrote to
the ML, they told me the same thing... but I still don't get it. I
mean, my kernel works for everything else. Why not Mondo?</P
></DIV
><DIV
CLASS="ANSWER"
><P
><B
> </B
>A: Because Mondo makes a boot disk using your kernel. I bet
your other software doesn't do that. Also, not all kernels are
suitable for boot disks. I'm sorry but that's Life. Upgrade your
kernel and/or recompile it. Take a look at
<A
HREF="#OVERVIEW-SYSRQ-KERNELREQ"
>Linux Kernel support</A
> to see
what your kernel must support.</P
></DIV
></DIV
><DIV
CLASS="QANDAENTRY"
><DIV
CLASS="QUESTION"
><P
><A
NAME="AEN1252"
></A
><B
>10.3.8. </B
>Q: Why do I only need a boot disk if I'm
using a tape drive? Where are the data disks?</P
></DIV
><DIV
CLASS="ANSWER"
><P
><B
> </B
>A: On the tape. :-) The first 32MB of the tape will be set
aside for a large tarball containing the data disks, a list of all
files backed up, and other sundries. If Mondo and Mindi do their
respective jobs then you won't need additional media, just the
boot media and the tape(s).</P
><P
>As of 2.2.6 mondorescue does support OBDR for tapes.
So if you have a tape supporting that protocol such as HP tape readers, you may directly boot from the tape as well.</P
></DIV
></DIV
><DIV
CLASS="QANDAENTRY"
><DIV
CLASS="QUESTION"
><P
><A
NAME="AEN1258"
></A
><B
>10.3.9. </B
>Q: Why does it say, "Process accounting
FAILED" when I reboot?</P
></DIV
><DIV
CLASS="ANSWER"
><P
><B
> </B
>A: You were using Process Accounting. Red Hat (or whichever
distro you are using) does not provide a startup/shutdown script
yet. So, when you try to backup the process log, it just grows and
grows as Mondo tries to back it up. Mondo doesn't back it up
anymore and that's why. The unfortunate side-effect is... well,
what you see on your screen. Type 'touch /var/log/pacct' and then
'paccton' to fix the error message.</P
></DIV
></DIV
><DIV
CLASS="QANDAENTRY"
><DIV
CLASS="QUESTION"
><P
><A
NAME="AEN1263"
></A
><B
>10.3.10. </B
>Q: Why does it say,
&#8220;request_module[block-major-1]: Root fs not mounted VFS:
Cannot open root device "100" or 01:00 Please append a correct
"root=" boot option kernel panic: VFS: Unable to mount root fs on
01:00&#8221; when i boot from the CD?</P
></DIV
><DIV
CLASS="ANSWER"
><P
><B
> </B
>A: Recompile your kernel and add initrd support. Take a look
at <A
HREF="#OVERVIEW-SYSRQ-KERNELREQ"
>Linux Kernel support</A
> to
see what your kernel must support.</P
></DIV
></DIV
><DIV
CLASS="QANDAENTRY"
><DIV
CLASS="QUESTION"
><P
><A
NAME="AEN1269"
></A
><B
>10.3.11. </B
>Q: My tape drive
doesn't play nicely with Mondo at boot-time. What do I do?</P
></DIV
><DIV
CLASS="ANSWER"
><P
><B
> </B
>A: Play with the 'mt' command (package mt-st). Use its setblksize and
defblksize switches to reconfigure your tape drive if necessary.
Some tape drives just are painful. If yours is one of
them then God help you. Mondo can handle any tape drive whose drive
and firmware can handle fopen(), fwrite(), fread() and fclose().
Mondo uses standard C libraries to talk to your tape streamer. If
your tape streamer can't handle that then you had better call a
priest. Either that or ask for a refund.</P
></DIV
></DIV
></DIV
></DIV
><DIV
CLASS="SECT1"
><HR><H2
CLASS="SECT1"
><A
NAME="FAQ-INSTALL"
>10.4. Installation related Questions</A
></H2
><DIV
CLASS="QANDASET"
><DL
><DT
>10.4.1. <A
HREF="#AEN1277"
>Q: Why do I get, "newt.h not found," or
"popt.h not found," several times when I try to install
Mondo?</A
></DT
><DT
>10.4.2. <A
HREF="#AEN1283"
>Q: Newt won't compile when I try. What's
the problem?</A
></DT
><DT
>10.4.3. <A
HREF="#AEN1289"
>Q: I've just used up 6 CD-R, only to
find that Mondo won't boot!</A
></DT
><DT
>10.4.4. <A
HREF="#AEN1294"
>Q: Lots of packages,
required by Mondo, are missing from my system. What do I do?</A
></DT
></DL
><DIV
CLASS="QANDAENTRY"
><DIV
CLASS="QUESTION"
><P
><A
NAME="AEN1277"
></A
><B
>10.4.1. </B
>Q: Why do I get, "newt.h not found," or
"popt.h not found," several times when I try to install
Mondo?</P
></DIV
><DIV
CLASS="ANSWER"
><P
><B
> </B
>A: You have not installed libnewt and/or libnewt-devel.
Please do so. Check <A
HREF="http://www.mondorescue.org/downloads.shtml#dependencies"
TARGET="_top"
>Related Linux
Packages</A
> to see what Mondo requires and where you can get
tarballs and RPM's. Make sure you are using the right version of
newt/libnewt. Read the error messages carefully.</P
></DIV
></DIV
><DIV
CLASS="QANDAENTRY"
><DIV
CLASS="QUESTION"
><P
><A
NAME="AEN1283"
></A
><B
>10.4.2. </B
>Q: Newt won't compile when I try. What's
the problem?</P
></DIV
><DIV
CLASS="ANSWER"
><P
><B
> </B
>A: You are probably missing popt.h, which newt needs to
compile, it can be found in the 'popt' package. Check your
distribution and see if they have popt, if not check
<A
HREF="http://www.mondorescue.org/downloads.shtml#dependencies"
TARGET="_top"
>Related Linux Packages</A
> to
see where you can get it.</P
></DIV
></DIV
><DIV
CLASS="QANDAENTRY"
><DIV
CLASS="QUESTION"
><P
><A
NAME="AEN1289"
></A
><B
>10.4.3. </B
>Q: I've just used up 6 CD-R, only to
find that Mondo won't boot!</P
></DIV
><DIV
CLASS="ANSWER"
><P
><B
> </B
>A: You should have used CD-RW. ;) In the HOWTO, it gives
instructions on how to create a test CD (one, not six).</P
></DIV
></DIV
><DIV
CLASS="QANDAENTRY"
><DIV
CLASS="QUESTION"
><P
><A
NAME="AEN1294"
></A
><B
>10.4.4. </B
>Q: Lots of packages,
required by Mondo, are missing from my system. What do I do?</P
></DIV
><DIV
CLASS="ANSWER"
><P
><B
> </B
>A: Install them. :) If you are using RPM or deb
then you'll be told which packages you need. Mondo offers a lot of
those packages on its
<A
HREF="http://www.mondorescue.org/downloads.shtml"
TARGET="_top"
>Download</A
>
web page.</P
></DIV
></DIV
></DIV
></DIV
><DIV
CLASS="SECT1"
><HR><H2
CLASS="SECT1"
><A
NAME="FAQ-HARDWARE"
>10.5. Hardware related Questions</A
></H2
><DIV
CLASS="QANDASET"
><DL
><DT
>10.5.1. <A
HREF="#AEN1303"
>Q: Can Mondo handle CD-RW?</A
></DT
><DT
>10.5.2. <A
HREF="#AEN1308"
>Q: Does Mondo support tape
drives?</A
></DT
><DT
>10.5.3. <A
HREF="#AEN1323"
>Q: Does Mondo support my tape
drive?</A
></DT
><DT
>10.5.4. <A
HREF="#AEN1328"
>Q: Sometimes, my laptop won't mount
Mondo CD properly, or something. Umm...</A
></DT
><DT
>10.5.5. <A
HREF="#AEN1333"
>Q: Does Mondo support Hardware RAID?</A
></DT
><DT
>10.5.6. <A
HREF="#AEN1339"
>Q: Where is my CD burner, in SCSI terms?</A
></DT
><DT
>10.5.7. <A
HREF="#AEN1361"
>Q: Can Mondo handle SCSI devices?</A
></DT
><DT
>10.5.8. <A
HREF="#AEN1366"
>Q: Why doesn't cdrecord -scanbus work ?</A
></DT
></DL
><DIV
CLASS="QANDAENTRY"
><DIV
CLASS="QUESTION"
><P
><A
NAME="AEN1303"
></A
><B
>10.5.1. </B
>Q: Can Mondo handle CD-RW?</P
></DIV
><DIV
CLASS="ANSWER"
><P
><B
> </B
>A: Yes. Use '-Ow <speed> <device>' to make it
work.</P
></DIV
></DIV
><DIV
CLASS="QANDAENTRY"
><DIV
CLASS="QUESTION"
><P
><A
NAME="AEN1308"
></A
><B
>10.5.2. </B
>Q: Does Mondo support tape
drives?</P
></DIV
><DIV
CLASS="ANSWER"
><P
><B
> </B
>A: Yes. See above.</P
><P
>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:</P
><DIV
CLASS="INFORMALTABLE"
><P
></P
><A
NAME="AEN1313"
></A
><TABLE
BORDER="1"
CLASS="CALSTABLE"
><COL><TBODY
><TR
><TD
> bash# dmesg | grep tape</TD
></TR
><TR
><TD
> bash# cat /proc/scsi/scsi</TD
></TR
><TR
><TD
> bash# mt -f /dev/st0 status</TD
></TR
></TBODY
></TABLE
><P
></P
></DIV
></DIV
></DIV
><DIV
CLASS="QANDAENTRY"
><DIV
CLASS="QUESTION"
><P
><A
NAME="AEN1323"
></A
><B
>10.5.3. </B
>Q: Does Mondo support my tape
drive?</P
></DIV
><DIV
CLASS="ANSWER"
><P
><B
> </B
>A: If your tape drive and its firmware and the kernel-level
driver support fopen(), fread(), fwrite() and fclose() - standard C
library calls - then yes, Mondo should support it. If not, well,
you need a refund. :) Mondo plays nicely with any sane, sensible
drives. That's most of them, by the way. :) If your drive doesn't
play nicely with Mondo then you may try tinkering with setblksize
and defblksize using 'mt', or tweaking Mondo's block size by
recompiling it with make INTTAPE=4096 or INTTAPE=8192 or something.
Other than that, you need a priest or a refund.
Also, depending on the tape streamer model, a tape should be inserted
in the tape drive before starting mondoarchive, otherwise it may not
recognize the drive.</P
></DIV
></DIV
><DIV
CLASS="QANDAENTRY"
><DIV
CLASS="QUESTION"
><P
><A
NAME="AEN1328"
></A
><B
>10.5.4. </B
>Q: Sometimes, my laptop won't mount
Mondo CD properly, or something. Umm...</P
></DIV
><DIV
CLASS="ANSWER"
><P
><B
> </B
>A: Please insert the CD, close the CD-ROM tray, wait a few
seconds and then press Enter to acknowledge insertion of the next
CD. Your laptop is on crack and is sucking a little too hard on the
pipe.</P
></DIV
></DIV
><DIV
CLASS="QANDAENTRY"
><DIV
CLASS="QUESTION"
><P
><A
NAME="AEN1333"
></A
><B
>10.5.5. </B
>Q: Does Mondo support Hardware RAID?</P
></DIV
><DIV
CLASS="ANSWER"
><P
><B
> </B
>A: Yes. You may backup and restore RAID systems. You may also
backup a non-RAID system and restore as RAID (or vice versa) by
using the mountlist editor to edit your RAID and non-RAID
partitions and their settings. Mondo will do the partitioning and
formatting for you.</P
><P
>Tested Raid controllers includes all those showing only classical devices
such as /dev/sdx, and SmartArray cciss controllers.</P
></DIV
></DIV
><DIV
CLASS="QANDAENTRY"
><DIV
CLASS="QUESTION"
><P
><A
NAME="AEN1339"
></A
><B
>10.5.6. </B
>Q: Where is my CD burner, in SCSI terms?</P
></DIV
><DIV
CLASS="ANSWER"
><P
><B
> </B
>A: Type:</P
><P
></P
><DIV
CLASS="INFORMALTABLE"
><P
></P
><A
NAME="AEN1344"
></A
><TABLE
BORDER="1"
CLASS="CALSTABLE"
><COL><TBODY
><TR
><TD
> bash# cdrecord -scanbus
</TD
></TR
><TR
><TD
> bash# wodim --devices
</TD
></TR
></TBODY
></TABLE
><P
></P
></DIV
><P
>or for ATAPI type of devices on older kernel versions:</P
><P
></P
><DIV
CLASS="INFORMALTABLE"
><P
></P
><A
NAME="AEN1353"
></A
><TABLE
BORDER="1"
CLASS="CALSTABLE"
><COL><TBODY
><TR
><TD
> bash# cdrecord -scanbus dev=ATAPI
</TD
></TR
></TBODY
></TABLE
><P
></P
></DIV
><P
>you may replace ATAPI by ATA in the previous line with certain cdrecord versions and hadrware configurations</P
><P
>Find your CD burner's device# (e.g. '0,0,0'). Call Mondo with
the switch '-Oc <speed>' -d '<device>'. Or, if you feel
lucky, just use '-Oc 2'; Mondo will (a) assume you want to write at
4x to a CD-R and (b) will do its best to find your CD burner.</P
></DIV
></DIV
><DIV
CLASS="QANDAENTRY"
><DIV
CLASS="QUESTION"
><P
><A
NAME="AEN1361"
></A
><B
>10.5.7. </B
>Q: Can Mondo handle SCSI devices?</P
></DIV
><DIV
CLASS="ANSWER"
><P
><B
> </B
>A: Mondo should be able to handle almost any hardware. So
long as your kernel and modules support it, Mindi will support it
and therefore so will Mondo.</P
></DIV
></DIV
><DIV
CLASS="QANDAENTRY"
><DIV
CLASS="QUESTION"
><P
><A
NAME="AEN1366"
></A
><B
>10.5.8. </B
>Q: Why doesn't cdrecord -scanbus work ?</P
></DIV
><DIV
CLASS="ANSWER"
><P
><B
> </B
>A: If you have a 2.4.x kernel (typical example are fedora legacy kernels for redhat 7.X/8/9) and an IDE CDRW device, and the drive is not
listed when you run
<DIV
CLASS="INFORMALTABLE"
><P
></P
><A
NAME="AEN1370"
></A
><TABLE
BORDER="1"
CLASS="CALSTABLE"
><COL><TBODY
><TR
><TD
>bash# cdrecord -scanbus</TD
></TR
></TBODY
></TABLE
><P
></P
></DIV
>
try adding the following kernel option to your boot script to enable
SCSI emulation: hdx=ide-scsi, where "hdx" should be replaced with the
appropriate drive letter of the CDRW device, e.g., "hdc".
(Answer provided by Christopher Moriarity cdm7_at_cdc.gov)</P
></DIV
></DIV
></DIV
></DIV
><DIV
CLASS="SECT1"
><HR><H2
CLASS="SECT1"
><A
NAME="FAQ-BACKUP"
>10.6. Backup related Questions</A
></H2
><DIV
CLASS="QANDASET"
><DL
><DT
>10.6.1. <A
HREF="#AEN1379"
>Q: Mondo says, 'Cannot
run mindi --makemountlist' and aborts. What do I do?</A
></DT
><DT
>10.6.2. <A
HREF="#AEN1386"
>Q: Can Mondo burn CD as they are
created?</A
></DT
><DT
>10.6.3. <A
HREF="#AEN1391"
>Q: Mondo failed to burn my CD. It said
something like, "Error CDB A1 01 02 53 ..." and so on. What does
that mean?</A
></DT
><DT
>10.6.4. <A
HREF="#AEN1396"
>Q: May I backup my system with one
partition layout and restore with another?</A
></DT
><DT
>10.6.5. <A
HREF="#AEN1408"
>Q: Why does Mondo need so much free disk
space?</A
></DT
><DT
>10.6.6. <A
HREF="#AEN1413"
>Q: I am trying to do something clever,
e.g. write my ISO's to an NFS mount, and I get some weird error
messages. What do I do?</A
></DT
><DT
>10.6.7. <A
HREF="#AEN1419"
>Q: Can Mondo backup to data files on
another partition, e.g. an NFS mount?</A
></DT
><DT
>10.6.8. <A
HREF="#AEN1424"
>Q: Can Mondo backup _to_ an NFS
partition, i.e. backup over a network? How about restoring?</A
></DT
><DT
>10.6.9. <A
HREF="#AEN1434"
>Q: Does Mondo handle System or Hidden
attributes when archiving Dos/Win files?</A
></DT
></DL
><DIV
CLASS="QANDAENTRY"
><DIV
CLASS="QUESTION"
><P
><A
NAME="AEN1379"
></A
><B
>10.6.1. </B
>Q: Mondo says, 'Cannot
run mindi --makemountlist' and aborts. What do I do?</P
></DIV
><DIV
CLASS="ANSWER"
><P
><B
> </B
> A: Look at <TT
CLASS="FILENAME"
>/var/log/mindi.log</TT
> and see what it
says. Also, try typing 'mindi --makemountlist /tmp/mountlist.txt'
to see what Mindi says. Send the log to the <A
HREF="http://lists.sourceforge.net/lists/listinfo/mondo-devel"
TARGET="_top"
>mondorescue mailing list</A
> if you get stuck.</P
></DIV
></DIV
><DIV
CLASS="QANDAENTRY"
><DIV
CLASS="QUESTION"
><P
><A
NAME="AEN1386"
></A
><B
>10.6.2. </B
>Q: Can Mondo burn CD as they are
created?</P
></DIV
><DIV
CLASS="ANSWER"
><P
><B
> </B
>A: Yes. Use the '-Oc <speed>' switch. Use a negative
number for a dummy burn.</P
></DIV
></DIV
><DIV
CLASS="QANDAENTRY"
><DIV
CLASS="QUESTION"
><P
><A
NAME="AEN1391"
></A
><B
>10.6.3. </B
>Q: Mondo failed to burn my CD. It said
something like, "Error CDB A1 01 02 53 ..." and so on. What does
that mean?</P
></DIV
><DIV
CLASS="ANSWER"
><P
><B
> </B
>A: Cdrecord reported some serious errors while trying to burn
your CD. Check your CD burner, your CD-R and your kernel.</P
></DIV
></DIV
><DIV
CLASS="QANDAENTRY"
><DIV
CLASS="QUESTION"
><P
><A
NAME="AEN1396"
></A
><B
>10.6.4. </B
>Q: May I backup my system with one
partition layout and restore with another?</P
></DIV
><DIV
CLASS="ANSWER"
><P
><B
> </B
>A: Yes. Boot in Interactive Mode and edit the mountlist using
the snazzy new mountlist editor. Mondo can now edit your RAID
partitions for you. Just open /dev/md0 (or whatever) and select
"RAID.." to start. Or, to add a RAID device:</P
><P
></P
><UL
><LI
><P
>Add two or more partitions, of type and mountpoint
'raid'</P
></LI
><LI
><P
>Add device '/dev/md0' and click OK</P
></LI
><LI
><P
>Follow the prompts and your own common-sense :)</P
></LI
></UL
></DIV
></DIV
><DIV
CLASS="QANDAENTRY"
><DIV
CLASS="QUESTION"
><P
><A
NAME="AEN1408"
></A
><B
>10.6.5. </B
>Q: Why does Mondo need so much free disk
space?</P
></DIV
><DIV
CLASS="ANSWER"
><P
><B
> </B
>A: Because it need space to create the archive files with afio, then
again space to create the ISO images that you'll be able to burn.</P
></DIV
></DIV
><DIV
CLASS="QANDAENTRY"
><DIV
CLASS="QUESTION"
><P
><A
NAME="AEN1413"
></A
><B
>10.6.6. </B
>Q: I am trying to do something clever,
e.g. write my ISO's to an NFS mount, and I get some weird error
messages. What do I do?</P
></DIV
><DIV
CLASS="ANSWER"
><P
><B
> </B
>A: Well, (a) use '-T /tmp' or '-T /home' or something in your
call to Mondo. Oh, and (b) check the <TT
CLASS="FILENAME"
>/etc/exports</TT
> file on your NFS server
and verify the exported filesystem is writable for the client, and relaunch exportfs -a.</P
></DIV
></DIV
><DIV
CLASS="QANDAENTRY"
><DIV
CLASS="QUESTION"
><P
><A
NAME="AEN1419"
></A
><B
>10.6.7. </B
>Q: Can Mondo backup to data files on
another partition, e.g. an NFS mount?</P
></DIV
><DIV
CLASS="ANSWER"
><P
><B
> </B
>A: Yes. Just backup as usual but add '-d /mnt/nfs' or
wherever your partition is mounted; don't use '-Oc' or '-Ot' at
all; just '-Oi -d /root'. Then, after booting from the media
which Mondo generates, you need to type 'ISO' at the
console.</P
></DIV
></DIV
><DIV
CLASS="QANDAENTRY"
><DIV
CLASS="QUESTION"
><P
><A
NAME="AEN1424"
></A
><B
>10.6.8. </B
>Q: Can Mondo backup _to_ an NFS
partition, i.e. backup over a network? How about restoring?</P
></DIV
><DIV
CLASS="ANSWER"
><P
><B
> </B
>A: Yes. Use '-On <mount> <directory>'. Example:</P
><DIV
CLASS="INFORMALTABLE"
><P
></P
><A
NAME="AEN1428"
></A
><TABLE
BORDER="1"
CLASS="CALSTABLE"
><COL><TBODY
><TR
><TD
> bash# mondoarchive -On nfs://192.168.1.3:/home/nfs </TD
></TR
></TBODY
></TABLE
><P
></P
></DIV
></DIV
></DIV
><DIV
CLASS="QANDAENTRY"
><DIV
CLASS="QUESTION"
><P
><A
NAME="AEN1434"
></A
><B
>10.6.9. </B
>Q: Does Mondo handle System or Hidden
attributes when archiving Dos/Win files?</P
></DIV
><DIV
CLASS="ANSWER"
><P
><B
> </B
>A: No. It probably never will, either. Sorry.</P
></DIV
></DIV
></DIV
></DIV
><DIV
CLASS="SECT1"
><HR><H2
CLASS="SECT1"
><A
NAME="FAQ-COMPARE"
>10.7. Compare related Questions</A
></H2
><DIV
CLASS="QANDASET"
><DL
><DT
>10.7.1. <A
HREF="#AEN1442"
>Q: When I compare my archives to my file
system, Mondo tells me there are differences or errors. Are the
archives bad?</A
></DT
></DL
><DIV
CLASS="QANDAENTRY"
><DIV
CLASS="QUESTION"
><P
><A
NAME="AEN1442"
></A
><B
>10.7.1. </B
>Q: When I compare my archives to my file
system, Mondo tells me there are differences or errors. Are the
archives bad?</P
></DIV
><DIV
CLASS="ANSWER"
><P
><B
> </B
>A: Look at <TT
CLASS="FILENAME"
>/tmp/changed.files</TT
>; if the files are logfiles,
temp files or files which you think you may have changed recently
then the archives are simply out of date, albeit only by a few
minutes. Not a problem. However, if lots of files in /usr have
changed or if you get lots of errors then perhaps your CD, your
tapes or even your hardware could be to blame. Check your CD writer
or tape streamer.</P
><P
>Also, don't forget to review <TT
CLASS="FILENAME"
>/var/log/mondoarchive.log</TT
> for
more information.</P
></DIV
></DIV
></DIV
></DIV
><DIV
CLASS="SECT1"
><HR><H2
CLASS="SECT1"
><A
NAME="FAQ-RESTORE"
>10.8. Restore related Questions</A
></H2
><DIV
CLASS="QANDASET"
><DL
><DT
>10.8.1. <A
HREF="#AEN1453"
>Q: Can Mondo help me
move/resize/re-allocate my partitions?</A
></DT
><DT
>10.8.2. <A
HREF="#AEN1458"
>Q: My zip drive is a SCSI drive. When I
restore, Mondo craps out, saying it can't mount the drive (because
there is no disk in it). What do I do?</A
></DT
><DT
>10.8.3. <A
HREF="#AEN1463"
>Q: I received a message like, 'Fileset
NNN failed' during restore. What does it mean.</A
></DT
><DT
>10.8.4. <A
HREF="#AEN1468"
>Q: Why does my ext3 partition have less
space free than when I backed it up?</A
></DT
><DT
>10.8.5. <A
HREF="#AEN1473"
>Q: When I restore after
booting from the media, I sometimes get errors like, "Running
out of memory" or "Segmentation fault". What is going on?</A
></DT
><DT
>10.8.6. <A
HREF="#AEN1479"
>Q: I can't nuke-restore my LVM or RAID or
LVM-on-RAID setup. I have to do it manually. What now?</A
></DT
></DL
><DIV
CLASS="QANDAENTRY"
><DIV
CLASS="QUESTION"
><P
><A
NAME="AEN1453"
></A
><B
>10.8.1. </B
>Q: Can Mondo help me
move/resize/re-allocate my partitions?</P
></DIV
><DIV
CLASS="ANSWER"
><P
><B
> </B
>A: Yes. Just backup your system in Interactive Mode using
Mondo. Edit the mountlist when prompted.</P
></DIV
></DIV
><DIV
CLASS="QANDAENTRY"
><DIV
CLASS="QUESTION"
><P
><A
NAME="AEN1458"
></A
><B
>10.8.2. </B
>Q: My zip drive is a SCSI drive. When I
restore, Mondo craps out, saying it can't mount the drive (because
there is no disk in it). What do I do?</P
></DIV
><DIV
CLASS="ANSWER"
><P
><B
> </B
>A: Restore in Interactive Mode. Delete the SCSI drive from
the mountlist before you restore. Then Mondo won't try to partition
or format it. Next time you backup, use -E /dev/sdd (or whatever
your zip drive is). The /dev entry will be excluded from the
mountlist but not from the filelist. So, when you restore, you
won't accidentally reformat your zip disk. However, after
restoring, you will find that /dev/sdd (the _file_) will still be
present in your /dev directory. Cool, eh?</P
></DIV
></DIV
><DIV
CLASS="QANDAENTRY"
><DIV
CLASS="QUESTION"
><P
><A
NAME="AEN1463"
></A
><B
>10.8.3. </B
>Q: I received a message like, 'Fileset
NNN failed' during restore. What does it mean.</P
></DIV
><DIV
CLASS="ANSWER"
><P
><B
> </B
>A: It usually means either you had a very large (>2GB)
file which was not archived owing to a flaw in your distro or your
filesystem has changed in relation to the backup.</P
></DIV
></DIV
><DIV
CLASS="QANDAENTRY"
><DIV
CLASS="QUESTION"
><P
><A
NAME="AEN1468"
></A
><B
>10.8.4. </B
>Q: Why does my ext3 partition have less
space free than when I backed it up?</P
></DIV
><DIV
CLASS="ANSWER"
><P
><B
> </B
>A: Mondo creates a 10MB journal file area. Your journal was
probably smaller than that, hence the difference.</P
></DIV
></DIV
><DIV
CLASS="QANDAENTRY"
><DIV
CLASS="QUESTION"
><P
><A
NAME="AEN1473"
></A
><B
>10.8.5. </B
>Q: When I restore after
booting from the media, I sometimes get errors like, "Running
out of memory" or "Segmentation fault". What is going on?</P
></DIV
><DIV
CLASS="ANSWER"
><P
><B
> </B
>A: It sounds as if you are running out of disk
space, probably ram disk space. Type 'df -m' to see which
partitions are running low on space. Please send as much
information as you can to the <A
HREF="http://lists.sourceforge.net/lists/listinfo/mondo-devel"
TARGET="_top"
>mondorescue mailing list</A
>. This problem is
believed to have been fixed in 1.63 and 1.71.</P
></DIV
></DIV
><DIV
CLASS="QANDAENTRY"
><DIV
CLASS="QUESTION"
><P
><A
NAME="AEN1479"
></A
><B
>10.8.6. </B
>Q: I can't nuke-restore my LVM or RAID or
LVM-on-RAID setup. I have to do it manually. What now?</P
></DIV
><DIV
CLASS="ANSWER"
><P
><B
> </B
>A: You said it yourself. You have to do it manually. :) Sorry
but that's about it. At least you have all the tools to do it. I
assume you know how. If you don't, look at i-want-my-lvm (a script
on the ramdisk) if you're using LVM. It should give you a few
clues. RAID is harder but in general Mondo's RAID support is good.
After you've prepped and formatted your drives, run mondorestore
again but say 'no' when asked if you want Mondo to prep or format
your drives.</P
></DIV
></DIV
></DIV
></DIV
></DIV
><DIV
CLASS="APPENDIX"
><HR><H1
><A
NAME="GFDL"
></A
>Appendix A. GNU Free Documentation License</H1
><P
>Version 1.1, March 2000</P
><A
NAME="AEN1486"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
><P
>Copyright (C) 2000 Free Software Foundation, Inc.
59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
Everyone is permitted to copy and distribute verbatim copies
of this license document, but changing it is not allowed.</P
></BLOCKQUOTE
><DIV
CLASS="SECT1"
><HR><H2
CLASS="SECT1"
><A
NAME="FDL-PREAMBLE"
>0. PREAMBLE</A
></H2
><P
>The purpose of this License is to make a manual, textbook,
or other written document "free" in the sense of freedom: to
assure everyone the effective freedom to copy and redistribute it,
with or without modifying it, either commercially or
noncommercially. Secondarily, this License preserves for the
author and publisher a way to get credit for their work, while not
being considered responsible for modifications made by
others.</P
><P
>This License is a kind of "copyleft", which means that
derivative works of the document must themselves be free in the
same sense. It complements the GNU General Public License, which
is a copyleft license designed for free software.</P
><P
>We have designed this License in order to use it for manuals
for free software, because free software needs free documentation:
a free program should come with manuals providing the same
freedoms that the software does. But this License is not limited
to software manuals; it can be used for any textual work,
regardless of subject matter or whether it is published as a
printed book. We recommend this License principally for works
whose purpose is instruction or reference.</P
></DIV
><DIV
CLASS="SECT1"
><HR><H2
CLASS="SECT1"
><A
NAME="FDL-DEF"
>1. APPLICABILITY AND DEFINITIONS</A
></H2
><P
>This License applies to any manual or other work that
contains a notice placed by the copyright holder saying it can be
distributed under the terms of this License. The "Document",
below, refers to any such manual or work. Any member of the
public is a licensee, and is addressed as "you".</P
><P
>A "Modified Version" of the Document means any work
containing the Document or a portion of it, either copied
verbatim, or with modifications and/or translated into another
language.</P
><P
>A "Secondary Section" is a named appendix or a front-matter
section of the Document that deals exclusively with the
relationship of the publishers or authors of the Document to the
Document's overall subject (or to related matters) and contains
nothing that could fall directly within that overall subject.
(For example, if the Document is in part a textbook of
mathematics, a Secondary Section may not explain any mathematics.)
The relationship could be a matter of historical connection with
the subject or with related matters, or of legal, commercial,
philosophical, ethical or political position regarding
them.</P
><P
>The "Invariant Sections" are certain Secondary Sections
whose titles are designated, as being those of Invariant Sections,
in the notice that says that the Document is released under this
License.</P
><P
>The "Cover Texts" are certain short passages of text that
are listed, as Front-Cover Texts or Back-Cover Texts, in the
notice that says that the Document is released under this
License.</P
><P
>A "Transparent" copy of the Document means a
machine-readable copy, represented in a format whose specification
is available to the general public, whose contents can be viewed
and edited directly and straightforwardly with generic text
editors or (for images composed of pixels) generic paint programs
or (for drawings) some widely available drawing editor, and that
is suitable for input to text formatters or for automatic
translation to a variety of formats suitable for input to text
formatters. A copy made in an otherwise Transparent file format
whose markup has been designed to thwart or discourage subsequent
modification by readers is not Transparent. A copy that is not
"Transparent" is called "Opaque".</P
><P
>Examples of suitable formats for Transparent copies include
plain ASCII without markup, Texinfo input format, LaTeX input
format, SGML or XML using a publicly available DTD, and
standard-conforming simple HTML designed for human modification.
Opaque formats include PostScript, PDF, proprietary formats that
can be read and edited only by proprietary word processors, SGML
or XML for which the DTD and/or processing tools are not generally
available, and the machine-generated HTML produced by some word
processors for output purposes only.</P
><P
>The "Title Page" means, for a printed book, the title page
itself, plus such following pages as are needed to hold, legibly,
the material this License requires to appear in the title page.
For works in formats which do not have any title page as such,
"Title Page" means the text near the most prominent appearance of
the work's title, preceding the beginning of the body of the
text.</P
></DIV
><DIV
CLASS="SECT1"
><HR><H2
CLASS="SECT1"
><A
NAME="FDL-VERBATIMCP"
>2. VERBATIM COPYING</A
></H2
><P
>You may copy and distribute the Document in any medium,
either commercially or noncommercially, provided that this
License, the copyright notices, and the license notice saying this
License applies to the Document are reproduced in all copies, and
that you add no other conditions whatsoever to those of this
License. You may not use technical measures to obstruct or
control the reading or further copying of the copies you make or
distribute. However, you may accept compensation in exchange for
copies. If you distribute a large enough number of copies you
must also follow the conditions in section 3.</P
><P
>You may also lend copies, under the same conditions stated
above, and you may publicly display copies.</P
></DIV
><DIV
CLASS="SECT1"
><HR><H2
CLASS="SECT1"
><A
NAME="FDL-QUANTITYCP"
>3. COPYING IN QUANTITY</A
></H2
><P
>If you publish printed copies of the Document numbering more
than 100, and the Document's license notice requires Cover Texts,
you must enclose the copies in covers that carry, clearly and
legibly, all these Cover Texts: Front-Cover Texts on the front
cover, and Back-Cover Texts on the back cover. Both covers must
also clearly and legibly identify you as the publisher of these
copies. The front cover must present the full title with all
words of the title equally prominent and visible. You may add
other material on the covers in addition. Copying with changes
limited to the covers, as long as they preserve the title of the
Document and satisfy these conditions, can be treated as verbatim
copying in other respects.</P
><P
>If the required texts for either cover are too voluminous to
fit legibly, you should put the first ones listed (as many as fit
reasonably) on the actual cover, and continue the rest onto
adjacent pages.</P
><P
>If you publish or distribute Opaque copies of the Document
numbering more than 100, you must either include a
machine-readable Transparent copy along with each Opaque copy, or
state in or with each Opaque copy a publicly-accessible
computer-network location containing a complete Transparent copy
of the Document, free of added material, which the general
network-using public has access to download anonymously at no
charge using public-standard network protocols. If you use the
latter option, you must take reasonably prudent steps, when you
begin distribution of Opaque copies in quantity, to ensure that
this Transparent copy will remain thus accessible at the stated
location until at least one year after the last time you
distribute an Opaque copy (directly or through your agents or
retailers) of that edition to the public.</P
><P
>It is requested, but not required, that you contact the
authors of the Document well before redistributing any large
number of copies, to give them a chance to provide you with an
updated version of the Document.</P
></DIV
><DIV
CLASS="SECT1"
><HR><H2
CLASS="SECT1"
><A
NAME="FDL-MODIF"
>4. MODIFICATIONS</A
></H2
><P
>You may copy and distribute a Modified Version of the
Document under the conditions of sections 2 and 3 above, provided
that you release the Modified Version under precisely this
License, with the Modified Version filling the role of the
Document, thus licensing distribution and modification of the
Modified Version to whoever possesses a copy of it. In addition,
you must do these things in the Modified Version:</P
><P
></P
><OL
TYPE="A"
><LI
><P
>Use in the Title Page
(and on the covers, if any) a title distinct from that of the
Document, and from those of previous versions (which should, if
there were any, be listed in the History section of the
Document). You may use the same title as a previous version if
the original publisher of that version gives permission.</P
></LI
><LI
><P
>List on the Title Page,
as authors, one or more persons or entities responsible for
authorship of the modifications in the Modified Version,
together with at least five of the principal authors of the
Document (all of its principal authors, if it has less than
five).</P
></LI
><LI
><P
>State on the Title page
the name of the publisher of the Modified Version, as the
publisher.</P
></LI
><LI
><P
>Preserve all the
copyright notices of the Document.</P
></LI
><LI
><P
>Add an appropriate
copyright notice for your modifications adjacent to the other
copyright notices.</P
></LI
><LI
><P
>Include, immediately
after the copyright notices, a license notice giving the public
permission to use the Modified Version under the terms of this
License, in the form shown in the Addendum below.</P
></LI
><LI
><P
>Preserve in that license
notice the full lists of Invariant Sections and required Cover
Texts given in the Document's license notice.</P
></LI
><LI
><P
>Include an unaltered
copy of this License.</P
></LI
><LI
><P
>Preserve the section
entitled "History", and its title, and add to it an item stating
at least the title, year, new authors, and publisher of the
Modified Version as given on the Title Page. If there is no
section entitled "History" in the Document, create one stating
the title, year, authors, and publisher of the Document as given
on its Title Page, then add an item describing the Modified
Version as stated in the previous sentence.</P
></LI
><LI
><P
>Preserve the network
location, if any, given in the Document for public access to a
Transparent copy of the Document, and likewise the network
locations given in the Document for previous versions it was
based on. These may be placed in the "History" section. You
may omit a network location for a work that was published at
least four years before the Document itself, or if the original
publisher of the version it refers to gives permission.</P
></LI
><LI
><P
>In any section entitled
"Acknowledgements" or "Dedications", preserve the section's
title, and preserve in the section all the substance and tone of
each of the contributor acknowledgements and/or dedications
given therein.</P
></LI
><LI
><P
>Preserve all the
Invariant Sections of the Document, unaltered in their text and
in their titles. Section numbers or the equivalent are not
considered part of the section titles.</P
></LI
><LI
><P
>Delete any section
entitled "Endorsements". Such a section may not be included in
the Modified Version.</P
></LI
><LI
><P
>Do not retitle any
existing section as "Endorsements" or to conflict in title with
any Invariant Section.</P
></LI
></OL
><P
>If the Modified Version includes new front-matter sections
or appendices that qualify as Secondary Sections and contain no
material copied from the Document, you may at your option
designate some or all of these sections as invariant. To do this,
add their titles to the list of Invariant Sections in the Modified
Version's license notice. These titles must be distinct from any
other section titles.</P
><P
>You may add a section entitled "Endorsements", provided it
contains nothing but endorsements of your Modified Version by
various parties--for example, statements of peer review or that
the text has been approved by an organization as the authoritative
definition of a standard.</P
><P
>You may add a passage of up to five words as a Front-Cover
Text, and a passage of up to 25 words as a Back-Cover Text, to the
end of the list of Cover Texts in the Modified Version. Only one
passage of Front-Cover Text and one of Back-Cover Text may be
added by (or through arrangements made by) any one entity. If the
Document already includes a cover text for the same cover,
previously added by you or by arrangement made by the same entity
you are acting on behalf of, you may not add another; but you may
replace the old one, on explicit permission from the previous
publisher that added the old one.</P
><P
>The author(s) and publisher(s) of the Document do not by
this License give permission to use their names for publicity for
or to assert or imply endorsement of any Modified Version.</P
></DIV
><DIV
CLASS="SECT1"
><HR><H2
CLASS="SECT1"
><A
NAME="FDL-COMBINING"
>5. COMBINING DOCUMENTS</A
></H2
><P
>You may combine the Document with other documents released
under this License, under the terms defined in section 4 above for
modified versions, provided that you include in the combination
all of the Invariant Sections of all of the original documents,
unmodified, and list them all as Invariant Sections of your
combined work in its license notice.</P
><P
>The combined work need only contain one copy of this
License, and multiple identical Invariant Sections may be replaced
with a single copy. If there are multiple Invariant Sections with
the same name but different contents, make the title of each such
section unique by adding at the end of it, in parentheses, the
name of the original author or publisher of that section if known,
or else a unique number. Make the same adjustment to the section
titles in the list of Invariant Sections in the license notice of
the combined work.</P
><P
>In the combination, you must combine any sections entitled
"History" in the various original documents, forming one section
entitled "History"; likewise combine any sections entitled
"Acknowledgements", and any sections entitled "Dedications". You
must delete all sections entitled "Endorsements."</P
></DIV
><DIV
CLASS="SECT1"
><HR><H2
CLASS="SECT1"
><A
NAME="FDL-COLLECTION"
>6. COLLECTIONS OF DOCUMENTS</A
></H2
><P
>You may make a collection consisting of the Document and
other documents released under this License, and replace the
individual copies of this License in the various documents with a
single copy that is included in the collection, provided that you
follow the rules of this License for verbatim copying of each of
the documents in all other respects.</P
><P
>You may extract a single document from such a collection,
and distribute it individually under this License, provided you
insert a copy of this License into the extracted document, and
follow this License in all other respects regarding verbatim
copying of that document.</P
></DIV
><DIV
CLASS="SECT1"
><HR><H2
CLASS="SECT1"
><A
NAME="FDL-AGGREGATION"
>7. AGGREGATION WITH INDEPENDENT WORKS</A
></H2
><P
>A compilation of the Document or its derivatives with other
separate and independent documents or works, in or on a volume of
a storage or distribution medium, does not as a whole count as a
Modified Version of the Document, provided no compilation
copyright is claimed for the compilation. Such a compilation is
called an "aggregate", and this License does not apply to the
other self-contained works thus compiled with the Document, on
account of their being thus compiled, if they are not themselves
derivative works of the Document.</P
><P
>If the Cover Text requirement of section 3 is applicable to
these copies of the Document, then if the Document is less than
one quarter of the entire aggregate, the Document's Cover Texts
may be placed on covers that surround only the Document within the
aggregate. Otherwise they must appear on covers around the whole
aggregate.</P
></DIV
><DIV
CLASS="SECT1"
><HR><H2
CLASS="SECT1"
><A
NAME="FDL-TRANSLATION"
>8. TRANSLATION</A
></H2
><P
>Translation is considered a kind of modification, so you may
distribute translations of the Document under the terms of section
4. Replacing Invariant Sections with translations requires
special permission from their copyright holders, but you may
include translations of some or all Invariant Sections in addition
to the original versions of these Invariant Sections. You may
include a translation of this License provided that you also
include the original English version of this License. In case of
a disagreement between the translation and the original English
version of this License, the original English version will
prevail.</P
></DIV
><DIV
CLASS="SECT1"
><HR><H2
CLASS="SECT1"
><A
NAME="FDL-TERM"
>9. TERMINATION</A
></H2
><P
>You may not copy, modify, sublicense, or distribute the
Document except as expressly provided for under this License. Any
other attempt to copy, modify, sublicense or distribute the
Document is void, and will automatically terminate your rights
under this License. However, parties who have received copies, or
rights, from you under this License will not have their licenses
terminated so long as such parties remain in full
compliance.</P
></DIV
><DIV
CLASS="SECT1"
><HR><H2
CLASS="SECT1"
><A
NAME="FDL-FUTUREREV"
>10. FUTURE REVISIONS OF THIS LICENSE</A
></H2
><P
>The Free Software Foundation may publish new, revised
versions of the GNU Free Documentation License from time to time.
Such new versions will be similar in spirit to the present
version, but may differ in detail to address new problems or
concerns. See <A
HREF="http://www.gnu.org/copyleft/"
TARGET="_top"
>http://www.gnu.org/copyleft/</A
>.</P
><P
>Each version of the License is given a distinguishing
version number. If the Document specifies that a particular
numbered version of this License "or any later version" applies to
it, you have the option of following the terms and conditions
either of that specified version or of any later version that has
been published (not as a draft) by the Free Software Foundation.
If the Document does not specify a version number of this License,
you may choose any version ever published (not as a draft) by the
Free Software Foundation.</P
></DIV
><DIV
CLASS="SECT1"
><HR><H2
CLASS="SECT1"
><A
NAME="FDL-HOWTO"
>How to use this License for your documents</A
></H2
><P
>To use this License in a document you have written, include
a copy of the License in the document and put the following
copyright and license notices just after the title page:</P
><A
NAME="AEN1576"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
><P
> Copyright (c) YEAR YOUR NAME.
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License, Version 1.1
or any later version published by the Free Software Foundation;
with the Invariant Sections being LIST THEIR TITLES, with the
Front-Cover Texts being LIST, and with the Back-Cover Texts being LIST.
A copy of the license is included in the section entitled "GNU
Free Documentation License".</P
></BLOCKQUOTE
><P
>If you have no Invariant Sections, write "with no Invariant
Sections" instead of saying which ones are invariant. If you have
no Front-Cover Texts, write "no Front-Cover Texts" instead of
"Front-Cover Texts being LIST"; likewise for Back-Cover
Texts.</P
><P
>If your document contains nontrivial examples of program
code, we recommend releasing these examples in parallel under your
choice of free software license, such as the GNU General Public
License, to permit their use in free software.</P
></DIV
></DIV
></DIV
></BODY
></HTML
>
distrib
>
Mandriva
>
2010.1
>
x86_64
>
media
>
contrib-release
>
by-pkgid
>
6b813956fff19ec40e6f3032f36ef13c
>
files
>
14
