| 1 |
\chapter{File Services Daemon} |
| 2 |
\label{blb:TheChapterStart11} |
| 3 |
\label{blb:developers:file:daemon} |
| 4 |
\index{File Services Daemon } |
| 5 |
\index{Daemon!File Services } |
| 6 |
|
| 7 |
Please note, this section is somewhat out of date as the code has evolved |
| 8 |
significantly. The basic idea has not changed though. |
| 9 |
|
| 10 |
This chapter is intended to be a technical discussion of the File daemon |
| 11 |
services and as such is not targeted at end users but rather at developers and |
| 12 |
system administrators that want or need to know more of the working details of |
| 13 |
\textbf{\bacula{}}. |
| 14 |
|
| 15 |
The \textbf{\bacula{} File Services} consist of the programs that run on the system |
| 16 |
to be backed up and provide the interface between the Host File system and |
| 17 |
\bacula{} -- in particular, the Director and the Storage services. |
| 18 |
|
| 19 |
When time comes for a backup, the Director gets in touch with the File daemon |
| 20 |
on the client machine and hands it a set of ``marching orders'' which, if |
| 21 |
written in English, might be something like the following: |
| 22 |
|
| 23 |
OK, \textbf{File daemon}, it's time for your daily incremental backup. I want you |
| 24 |
to get in touch with the Storage daemon on host archive.mysite.com and perform |
| 25 |
the following save operations with the designated options. You'll note that |
| 26 |
I've attached include and exclude lists and patterns you should apply when |
| 27 |
backing up the file system. As this is an incremental backup, you should save |
| 28 |
only files modified since the time you started your last backup which, as you |
| 29 |
may recall, was 2000-11-19-06:43:38. Please let me know when you're done and |
| 30 |
how it went. Thank you. |
| 31 |
|
| 32 |
So, having been handed everything it needs to decide what to dump and where to |
| 33 |
store it, the File daemon doesn't need to have any further contact with the |
| 34 |
Director until the backup is complete providing there are no errors. If there |
| 35 |
are errors, the error messages will be delivered immediately to the Director. |
| 36 |
While the backup is proceeding, the File daemon will send the file coordinates |
| 37 |
and data for each file being backed up to the Storage daemon, which will in |
| 38 |
turn pass the file coordinates to the Director to put in the catalog. |
| 39 |
|
| 40 |
During a \textbf{Verify} of the catalog, the situation is different, since the |
| 41 |
File daemon will have an exchange with the Director for each file, and will |
| 42 |
not contact the Storage daemon. |
| 43 |
|
| 44 |
A \textbf{Restore} operation will be very similar to the \textbf{Backup} except that |
| 45 |
during the \textbf{Restore} the Storage daemon will not send storage coordinates |
| 46 |
to the Director since the Director presumably already has them. On the other |
| 47 |
hand, any error messages from either the Storage daemon or File daemon will |
| 48 |
normally be sent directly to the Directory (this, of course, depends on how |
| 49 |
the Message resource is defined). |
| 50 |
|
| 51 |
\section{Commands Received from the Director for a Backup} |
| 52 |
\index{Backup!Commands Received from the Director for a } |
| 53 |
\index{Commands Received from the Director for a Backup } |
| 54 |
|
| 55 |
To be written\ldots{} |
| 56 |
|
| 57 |
\section{Commands Received from the Director for a Restore} |
| 58 |
\index{Commands Received from the Director for a Restore } |
| 59 |
\index{Restore!Commands Received from the Director for a } |
| 60 |
|
| 61 |
To be written \ldots{} |