follow the tutorial explicitly:
You will notice that the default Storage daemon device is named File and that
it will use device /tmp, which is not currently open.
Now, let's actually run a job with:
run
you should get the following output:
Using default Catalog name=MyCatalog DB=bacula
A job name must be specified.
The defined Job resources are:
1: Client1
2: BackupCatalog
3: RestoreFiles
Select Job resource (1-3):
Here, Bacula has listed the three different Jobs that you can run, and you
should choose number 1 and type enter, at which point you will get:
Run Backup job
JobName: Client1
FileSet: Full Set
Level: Incremental
Client: rufus-fd
Storage: File
Pool: Default
When: 2003-04-28 14:18:57
OK to run? (yes/mod/no):
At this point, take some time to look carefully at what is printed and
understand it. It is asking you if it is OK to run a job named Client1 with
FileSet Full Set (we listed above) as an Incremental job on your Client (your
client name will be different), and to use Storage File and Pool Default, and
finally, it wants to run it now (the current time should be displayed by your
console).
Here we have the choice to run (yes), to modify one or more of the above
parameters (mod), or to not run the job (no). Please enter yes, at which point
you should immediately get the command prompt (an asterisk). If you wait a few
seconds, then enter the command messages you will get back something like:
28-Apr-2003 14:22 rufus-dir: Last FULL backup time not found. Doing
FULL backup.
28-Apr-2003 14:22 rufus-dir: Start Backup JobId 1,
Job=Client1.2003-04-28_14.22.33
28-Apr-2003 14:22 rufus-sd: Job Client1.2003-04-28_14.22.33 waiting.
Cannot find any appendable volumes.
Please use the "label" command to create a new Volume for:
Storage: FileStorage
Media type: File
Pool: Default
The first message, indicates that no previous Full backup was done, so Bacula
is upgrading our Incremental job to a Full backup (this is normal). The second
message indicates that the job started with JobId 1., and the third message
tells us that Bacula cannot find any Volumes in the Pool for writing the
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
you want by doing a status dir. In order to continue, we must create a Volume
that Bacula can write on. We do so with:
label
and Bacula will print:
The defined Storage resources are:
1: File
Item 1 selected automatically.
Enter new Volume name:
at which point, you should enter some name beginning with a letter and
containing only letters and numbers (period, hyphen, and underscore) are also
permitted. For example, enter TestVolume001, and you should get back:
On Thu, Jan 26, 2006 at 03:57:44PM +0000, [EMAIL PROTECTED] wrote:
> I've figure out why the storage daemon would not run. I had to do a bacula
> stop and then do a bacula start and my problem went away. Back to my
> tutorial. When I do a status device this what I get. In the tutorial the
> Device "DDS-4 statement wasn't there. When I run my job it termanates. How
> can I work around this just to see if my job will backup up the tmp
> directory??
>
>
> Device status:
> Device "FileStorage" (/tmp) is not open or does not exist.
> Device "DDS-4" (/dev/nst0) open but no Bacula volume is mounted.
> Total Bytes Read=0 Blocks Read=0 Bytes/block=0
> Positioned at File=0 Block=0
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Bacula-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bacula-users
