\index[general]{Daemons!Starting the }
\addcontentsline{toc}{subsection}{Starting the Daemons}
-To start the three daemons, from your installation directory, simply enter:
+Assuming you have built from source or have installed the rpms,
+to start the three daemons, from your installation directory, simply enter:
-./bacula start This script starts the Storage daemon, the File daemon, and the
+./bacula start
+
+The {\bf bacula} script starts the Storage daemon, the File daemon, and the
Director daemon, which all normally run as daemons in the background. If you
are using the autostart feature of Bacula, your daemons will either be
automatically started on reboot, or you can control them individually with the
files {\bf bacula-dir}, {\bf bacula-fd}, and {\bf bacula-sd}, which are
usually located in {\bf /etc/init.d}, though the actual location is system
dependent.
+Some distributions may do this differently.
Note, on Windows, currently only the File daemon is ported, and it must be
started differently. Please see the
./bconsole
-Note, on 1.32 versions and lower, the command name is {\bf console} rather
-than bconsole. Alternatively to running the command line console, if you have
+Alternatively to running the command line console, if you have
GNOME installed and used the {\bf \verb:--:enable-gnome} on the configure command,
you may use the GNOME Console program:
./gnome-console
-For simplicity, here we will describe only the {\bf ./console} program. Most
-of what is described here applies equally well to {\bf ./gnome-console}.
+Another possibilty is to run the wxWidgets program {\bf wx-console}.
+
+For simplicity, here we will describe only the {\bf ./bconsole} program. Most
+of what is described here applies equally well to {\bf ./gnome-console}
+and to {\bf wx-console}
The {\bf ./bconsole} runs the Bacula Console program, which connects to the
Director daemon. Since Bacula is a network program, you can run the Console
\item Have possibly edited your {\bf bacula-dir.conf} file to personalize it
a bit. BE CAREFUL! if you change the Director's name or password, you will
need to make similar modifications in the other .conf files. For the moment
-it is probably better to make no changes.
+ it is probably better to make no changes.
\item You have started Bacula with {\bf ./bacula start}
\item You have invoked the Console program with {\bf ./bconsole}
- \end{itemize}
+\end{itemize}
Furthermore, we assume for the moment you are using the default configuration
files.
{\bf Catalog} is used for backing up Bacula's catalog and is not of interest
to us for the moment. The {\bf Inc:} entries are the files or directories that
will be included in the backup and the {\bf Exc:} are those that will be
-excluded.
+excluded. You can change what is backed up by editing {\bf bacula-dir.conf}
+and changing the {\bf File =} line in the {\bf FileSet} resource.
Now is the time to run your first backup job. We are going to backup your
Bacula source directory to a File Volume in your {\bf /tmp} directory just to
output. This is normal because we have not yet created (labeled) any Volumes.
Bacula indicates to you all the details of the volume it needs.
-At this point, the job is blocked waiting for a Volume. You can check this if
+At this point, the job is BLOCKED waiting for a Volume. You can check this if
you want by doing a {\bf status dir}. In order to continue, we must create a
Volume that Bacula can write on. We do so with:
to be restored. You will be presented several methods
of specifying the JobIds. Then you will be allowed to
select which files from those JobIds are to be restored.
+
To select the JobIds, you have the following choices:
1: List last 20 Jobs run
2: List Jobs where a given File is saved
6: Select backup for a client before a specified time
7: Enter a list of files to restore
8: Enter a list of files to restore before a specified time
- 9: Cancel
-Select item: (1-9):
+ 9: Find the JobIds of the most recent backup for a client
+ 10: Find the JobIds for a backup for a client before a specified time
+ 11: Enter a list of directories to restore for found JobIds
+ 12: Cancel
+Select item: (1-12):
\end{verbatim}
\normalsize
Client: rufus-fd
Storage: File
JobId: *None*
-When: 2003-04-28 14:53:54
+When: 2005-04-28 14:53:54
OK to run? (yes/mod/no):
\end{verbatim}
\normalsize
\footnotesize
\begin{verbatim}
-28-Apr-2003 14:56 rufus-dir: Bacula 1.30 (28Apr03): 28-Apr-2003 14:56
+28-Apr-2005 14:56 rufus-dir: Bacula 1.30 (28Apr03): 28-Apr-2003 14:56
JobId: 2
-Job: RestoreFiles.2003-04-28_14.56.06
+Job: RestoreFiles.2005-04-28_14.56.06
Client: rufus-fd
-Start time: 28-Apr-2003 14:56
-End time: 28-Apr-2003 14:56
+Start time: 28-Apr-2005 14:56
+End time: 28-Apr-2005 14:56
Files Restored: 1,444
Bytes Restored: 38,816,381
Rate: 9704.1 KB/s
FD termination status: OK
Termination: Restore OK
-28-Apr-2003 14:56 rufus-dir: Begin pruning Jobs.
-28-Apr-2003 14:56 rufus-dir: No Jobs found to prune.
-28-Apr-2003 14:56 rufus-dir: Begin pruning Files.
-28-Apr-2003 14:56 rufus-dir: No Files found to prune.
-28-Apr-2003 14:56 rufus-dir: End auto prune.
+28-Apr-2005 14:56 rufus-dir: Begin pruning Jobs.
+28-Apr-2005 14:56 rufus-dir: No Jobs found to prune.
+28-Apr-2005 14:56 rufus-dir: Begin pruning Files.
+28-Apr-2005 14:56 rufus-dir: No Files found to prune.
+28-Apr-2005 14:56 rufus-dir: End auto prune.
\end{verbatim}
\normalsize
projects / bacula / docs / blobdiff