own bootstrap files, or so that you can edit a bootstrap file produced by {\bf
Bacula}. However, normally the bootstrap file will be automatically created
for you during the
-\ilink{restore}{_ChapterStart13} command in the Console program, or
+\ilink{restore_command}{_ConsoleChapter} command in the Console program, or
by using a
\ilink{ Write Bootstrap}{writebootstrap} record in your Backup
Jobs, and thus you will never need to know the details of this file.
configuration while Bacula is running, it is advisable to restart the
Director at the next convenient opportunity.
-
+\label{restore_command}
\item [restore]
\index[console]{restore}
The restore command allows you to select one or more Jobs (JobIds) to be
the default bacula-dir.conf file. This will allow you to quickly restore your
catalog in the event it is wiped out -- otherwise it is many excruciating
hours of work.
+\item Make a copy of the bacula-dir.conf, bacula-sd.conf, and
+ bacula-fd.conf files that you are using on your server. Put it in a safe
+ place (on another machine) as these files can be difficult to
+ reconstruct if your server dies.
\item Make a Bacula Rescue CDROM! See the
\ilink{Disaster Recovery Using a Bacula Rescue
- CDROM}{_ChapterStart38} chapter. It is trivial to make such a CDROM,
+ CDROM}{_ChapterRescue} chapter. It is trivial to make such a CDROM,
and it can make system recovery in the event of a lost hard disk infinitely
easier.
\item After doing your first backup restore some or all the data. Do this for
\ilink{Basic Volume Management}{_ChapterStart39},\\
\ilink{Using Pools to Manage Volumes}{_ChapterStart11}.
\item Perform a bare metal recovery using the Bacula Rescue CDROM. See the
- \ilink{Disaster Recovery Using a Bacula Rescue CDROM}{_ChapterStart38}
+ \ilink{Disaster Recovery Using a Bacula Rescue CDROM}{_ChapterRescue}
chapter.
\end{itemize}
\index[general]{How Can I Be Sure that Bacula Really Saves and Restores
All Files? } It is really quite simple, but took me a while to figure
out how to "prove" it. First make a Bacula Rescue disk, see the
- \ilink{Disaster Recovery Using Bacula}{_ChapterStart38} of this manual.
+ \ilink{Disaster Recovery Using Bacula}{_ChapterRescue} chapter
+ of this manual.
Second, you run a full backup of all your files on all partitions.
Third, you run an Verify InitCatalog Job on the same FileSet, which
effectively makes a record of all the files on your system. Fourth, you
Ludovic Strappazon has pointed out that this feature can be used to backup a
full Microsoft Windows disk. Simply boot into the system using a Linux Rescue
disk, then load a statically linked Bacula as described in the
- \ilink{ Disaster Recovery Using Bacula}{_ChapterStart38} chapter of
+ \ilink{ Disaster Recovery Using Bacula}{_ChapterRescue} chapter of
this manual. Then save the whole disk partition. In the case of a disaster,
you can then restore the desired partition by again booting with the rescue
disk and doing a restore of the partition.
{\bf Bacula} is a backup, restore and verification program and is not a
complete disaster recovery system in itself, but it can be a key part of one
if you plan carefully and follow the instructions included in the
-\ilink{ Disaster Recovery}{_ChapterStart38} Chapter of this manual.
+\ilink{ Disaster Recovery}{_ChapterRescue} Chapter of this manual.
With proper planning, as mentioned in the Disaster Recovery chapter {\bf
Bacula} can be a central component of your disaster recovery system. For
If you intend to use Bacula as a disaster recovery tool rather than simply a
program to restore lost or damaged files, you will want to read the
-\ilink{Disaster Recovery Using Bacula Chapter}{_ChapterStart38} of
+\ilink{Disaster Recovery Using Bacula Chapter}{_ChapterRescue} of
this manual.
In any case, you are strongly urged to carefully test restoring some files
with SYSTEM ownership and permissions. In this case, you may have problems
accessing the newly restored files.
-To avoid this problem, you should create any alternate directory before doing
-the
-restore. Bacula will not change the ownership and permissions of the directory
-if it is already created as long as it is not one of the directories being
-restored (i.e. written to tape).
+To avoid this problem, you should create any alternate directory before
+doing the restore. Bacula will not change the ownership and permissions of
+the directory if it is already created as long as it is not one of the
+directories being restored (i.e. written to tape).
The default restore location is {\bf /tmp/bacula-restores/} and if you are
restoring from drive {\bf E:}, the default will be
\item Set "Block Positioning = no" in your Device resource and try the
restore. This is a new directive and untested.
\item Set "Minimum Block Size = 512" and "Maximum Block Size = 512" and
- try the restore. Again send me the full job report output. If you are able
- to
- determine the block size your drive was previously using, you should try
- that size if 512 does not work.
+ try the restore. Again send me the full job report output. If you are
+ able to determine the block size your drive was previously using, you
+ should try that size if 512 does not work.
\item Try editing the restore.bsr file at the Run xxx yes/mod/no prompt
- before starting the restore job and remove all the VolBlock statements.
- These
- are what causes Bacula to reposition the tape, and where problems occur if
- you have a fixed block size set for your drive. The VolFile commands also
- cause repositioning, but this will work regardless of the block size.
+ before starting the restore job and remove all the VolBlock statements.
+ These are what causes Bacula to reposition the tape, and where problems
+ occur if you have a fixed block size set for your drive. The VolFile
+ commands also cause repositioning, but this will work regardless of the
+ block size.
\item Use bextract to extract the files you want -- it reads the Volume
- sequentially if you use the include list feature, or if you use a .bsr file,
- but remove all the VolBlock statements after the .bsr file is created (at
- the
- Run yes/mod/no) prompt but before you start the restore.
+ sequentially if you use the include list feature, or if you use a .bsr
+ file, but remove all the VolBlock statements after the .bsr file is
+ created (at the Run yes/mod/no) prompt but before you start the restore.
\end{enumerate}
\subsection*{Example Restore Job Resource}
This command is the same as the {\bf help} command.
\end{description}
+\label{database_restore}
\subsection*{Restoring When Things Go Wrong}
\index[general]{Restoring When Things Go Wrong }
+\index[general]{Restoring Your Database}
+\index[general]{Database!Restoring}
\addcontentsline{toc}{subsection}{Restoring When Things Go Wrong}
This and the following sections will try to present a few of the kinds of
problems that can come up making restoring more difficult. I'll try to
provide a few ideas how to get out of these problem situations.
+In addition to what is presented here, there is more specific information
+on restoring a \ilink{Client}{restore_client} and your
+\ilink{Server}{restore_server} in the \ilink{Disaster Recovery Using
+Bacula}{_ChapterRescue} chapter of this manual.
\begin{description}
+\item[Problem]
+ My database is broken.
+\item[Solution]
For SQLite, use the vacuum command to try to fix the database. For either
MySQL or PostgreSQL, see the vendor's documentation. They have specific tools
that check and repair databases.
current backup or a backup prior to a specified time and date.
\item Restore of a complete system starting from bare metal. This is mostly
automated for Linux systems and partially automated for Solaris. See
- \ilink{Disaster Recovery Using Bacula}{_ChapterStart38}. This is also
+ \ilink{Disaster Recovery Using Bacula}{_ChapterRescue}. This is also
reported to work on Win2K/XP systems.
\item Listing and Restoration of files using stand-alone {\bf bls} and {\bf
bextract} tool programs. Among other things, this permits extraction of files
-Beta-1.38.4 (12 January 2006)
+Beta-1.38.4 (14 January 2006)
projects / bacula / docs / commitdiff