Thanks!! I have the tutorial printed out and I've been following the tutorial to the letter. When I select the client to run here is my output: This is not in tutorial.
A job name must be specified.
The defined Job resources are:
1: Client1
2: BackupCatalog
3: RestoreFiles
Select Job resource (1-3): 1
Run Backup job
JobName: Client1
FileSet: Full Set
Level: Incremental
Client: ninja3-fd
Storage: File
Pool: Default
When: 2006-01-26 12:14:21
Priority: 10
OK to run? (yes/mod/no): yes
Job started. JobId=13
*messages
26-Jan 09:59 ninja3-dir: *Console*.2006-01-26_09.31.11 Warning: bnet.c:852 Could not connect to Storage daemon on ninja3:9103. ERR=Connection refused
Retrying ...
26-Jan 10:04 ninja3-dir: *Console*.2006-01-26_09.31.11 Warning: bnet.c:852 Could not connect to Storage daemon on ninja3:9103. ERR=Connection refused
Retrying ...
26-Jan 12:14 ninja3-dir: No prior Full backup Job record found.
26-Jan 12:14 ninja3-dir: No prior or suitable Full backup found. Doing FULL backup.
26-Jan 12:14 ninja3-dir: Start Backup JobId 13, Job=Client1.2006-01-26_12.14.51
26-Jan 12:14 ninja3-dir: Client1.2006-01-26_12.14.51 Fatal error:
Storage daemon didn't accept Device "FileStorage" because:
The defined Job resources are:
1: Client1
2: BackupCatalog
3: RestoreFiles
Select Job resource (1-3): 1
Run Backup job
JobName: Client1
FileSet: Full Set
Level: Incremental
Client: ninja3-fd
Storage: File
Pool: Default
When: 2006-01-26 12:14:21
Priority: 10
OK to run? (yes/mod/no): yes
Job started. JobId=13
*messages
26-Jan 09:59 ninja3-dir: *Console*.2006-01-26_09.31.11 Warning: bnet.c:852 Could not connect to Storage daemon on ninja3:9103. ERR=Connection refused
Retrying ...
26-Jan 10:04 ninja3-dir: *Console*.2006-01-26_09.31.11 Warning: bnet.c:852 Could not connect to Storage daemon on ninja3:9103. ERR=Connection refused
Retrying ...
26-Jan 12:14 ninja3-dir: No prior Full backup Job record found.
26-Jan 12:14 ninja3-dir: No prior or suitable Full backup found. Doing FULL backup.
26-Jan 12:14 ninja3-dir: Start Backup JobId 13, Job=Client1.2006-01-26_12.14.51
26-Jan 12:14 ninja3-dir: Client1.2006-01-26_12.14.51 Fatal error:
Storage daemon didn't accept Device "FileStorage" because:
JobId: 13
Job: Client1.2006-01-26_12.14.51
Backup Level: Full (upgraded from Incremental)
Client: "ninja3-fd" x86_64-unknown-linux-gnu,redhat,(Stentz)
FileSet: "Full Set" 2006-01-20 23:05:02
Pool: "Default"
Storage: "File"
Scheduled time: &nbs p; 26-Jan-2006 12:14:21
Start time: 26-Jan-2006 12:14:53
End time: 26-Jan-2006 12:14:54
Priority: 10
FD Files Written: 0
SD Files Written: 0
FD Bytes Written: 0
SD Bytes Written: 0
Rate: 0.0 KB/s
Software Compression: None
Volume name(s):
Volume Session Id: 1
Volume Session Time: 1138288149
Last Volume Bytes: 0
Non-fatal FD errors: 0
SD Errors: 0
FD termination status:
SD termination status:
Termination: *** Backup Error ***
Job: Client1.2006-01-26_12.14.51
Backup Level: Full (upgraded from Incremental)
Client: "ninja3-fd" x86_64-unknown-linux-gnu,redhat,(Stentz)
FileSet: "Full Set" 2006-01-20 23:05:02
Pool: "Default"
Storage: "File"
Scheduled time: &nbs p; 26-Jan-2006 12:14:21
Start time: 26-Jan-2006 12:14:53
End time: 26-Jan-2006 12:14:54
Priority: 10
FD Files Written: 0
SD Files Written: 0
FD Bytes Written: 0
SD Bytes Written: 0
Rate: 0.0 KB/s
Software Compression: None
Volume name(s):
Volume Session Id: 1
Volume Session Time: 1138288149
Last Volume Bytes: 0
Non-fatal FD errors: 0
SD Errors: 0
FD termination status:
SD termination status:
Termination: *** Backup Error ***
-------------- Original message --------------
From: Michael Galloway <[EMAIL PROTECTED]>
> 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 w ill 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 de tails 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
