Am 08.03.2011 08:45, schrieb J. Echter:
> Hi,
>
> my backups yesterday ran all OK, but today i bacula doesn't start up
> after a reboot.
>
> Error Message i get is:
>
> sudo ./bacula-sd -t -c -v /etc/bacula/bacula-dir.conf
> 08-Mar 08:44 bacula-sd: ERROR TERMINATION at parse_conf.c:971
> Config err
Hi,
my backups yesterday ran all OK, but today i bacula doesn't start up
after a reboot.
Error Message i get is:
sudo ./bacula-sd -t -c -v /etc/bacula/bacula-dir.conf
08-Mar 08:44 bacula-sd: ERROR TERMINATION at parse_conf.c:971
Config error: Keyword "DirPort" not permitted in this resource.
Pe
On Mon, Mar 7, 2011 at 1:24 PM, Win Htin wrote:
> Thanks John. Do you recollect which actual database I have to look into?
>
http://bacula.org/5.0.x-manuals/en/problems/problems/Tips_Suggestions.html#SECTION0036
John
---
I have been working on a configuration for backing up to disk during
the evening and then copying the volume(s) to tape using a copy job
during the day. I have previously only used Bacula to back up to disk
volumes and need some pointers on how to solve a couple of issues that
I am running
On Mon, Mar 7, 2011 at 2:11 PM, Michael Edwards
wrote:
> I canceled a job about an hour ago as it wasn't going to run. It is the
> only job that would be writing to the volume mounted in drive 1 of our 2
> drive Dell Powervault. Drive 0 is in use doing backups from another
> pool. After about a
I canceled a job about an hour ago as it wasn't going to run. It is the
only job that would be writing to the volume mounted in drive 1 of our 2
drive Dell Powervault. Drive 0 is in use doing backups from another
pool. After about a half an hour, I noticed that other jobs were
"waiting on st
Thanks John. Do you recollect which actual database I have to look into?
On Mon, Mar 7, 2011 at 12:15 PM, John Drescher wrote:
>> I noticed every time I have to cancel a running job, the tape/volume
>> goes into error state. I assumed the job would terminate gracefully
>> with an eod mark but se
> I noticed every time I have to cancel a running job, the tape/volume
> goes into error state. I assumed the job would terminate gracefully
> with an eod mark but seems not. Is there a way I can put an eod mark
> and put the tape back to append mode? I am running version 2.2.6 on
> RHEL 4.6 server
Hi folks,
I noticed every time I have to cancel a running job, the tape/volume
goes into error state. I assumed the job would terminate gracefully
with an eod mark but seems not. Is there a way I can put an eod mark
and put the tape back to append mode? I am running version 2.2.6 on
RHEL 4.6 serve
On Monday 07 March 2011 14:33:50 Dan Langille wrote:
> On 3/7/2011 6:49 AM, Silver Salonen wrote:
> > On Monday 07 March 2011 13:37:42 Dan Langille wrote:
> >> On 3/4/2011 10:31 PM, Mehma Sarja wrote:
> >>> On 3/4/11 4:32 AM, Dan Langille wrote:
> This situation occurs often. Usually every mor
On 3/7/2011 6:49 AM, Silver Salonen wrote:
> On Monday 07 March 2011 13:37:42 Dan Langille wrote:
>> On 3/4/2011 10:31 PM, Mehma Sarja wrote:
>>> On 3/4/11 4:32 AM, Dan Langille wrote:
This situation occurs often. Usually every morning. If I cancel the top
job (in this ca 54502), the oth
On Monday 07 March 2011 13:37:42 Dan Langille wrote:
> On 3/4/2011 10:31 PM, Mehma Sarja wrote:
> > On 3/4/11 4:32 AM, Dan Langille wrote:
> >> This situation occurs often. Usually every morning. If I cancel the top
> >> job (in this ca 54502), the other jobs will proceed.
> >>
> >>
> >>
> >> Runn
On 3/4/2011 10:31 PM, Mehma Sarja wrote:
> On 3/4/11 4:32 AM, Dan Langille wrote:
>> This situation occurs often. Usually every morning. If I cancel the top
>> job (in this ca 54502), the other jobs will proceed.
>>
>>
>>
>> Running Jobs:
>> Console connected at 04-Mar-11 12:23
>> JobId Level
13 matches
Mail list logo
