Hi all,
David Dumortier a écrit :
> Hello,
>
> John Drescher a écrit :
>> On Mon, Nov 23, 2009 at 4:16 AM, David Dumortier
>> wrote:
>>>
>>> My bacula-sd.conf :
>>> Device {
>>> Name = stockage
>>> Media Type = File
>>> Archive Device = /mnt/sauvegardes
>>> LabelMedia = yes;
On Wed, Nov 25, 2009 at 4:07 AM, David Dumortier
wrote:
> Hi all,
>
> David Dumortier a écrit :
>> Hello,
>>
>> John Drescher a écrit :
>>> On Mon, Nov 23, 2009 at 4:16 AM, David Dumortier
>>> wrote:
My bacula-sd.conf :
Device {
Name = stockage
Media Type = File
A
Hello List,
I've got a best practice question. When a Job is started it changes to
Status=Running and the FD tries to connect to the SD. Let's assume this
fails due to network outages, or in my case I configured an IP for the
SD which is not accessible from the Client.
What happens is the Job
John Drescher a écrit :
> On Wed, Nov 25, 2009 at 4:07 AM, David Dumortier
> wrote:
>> Hi all,
>>
>> David Dumortier a écrit :
>>> Hello,
>>>
>>> John Drescher a écrit :
On Mon, Nov 23, 2009 at 4:16 AM, David Dumortier
wrote:
>
> My bacula-sd.conf :
> Device {
> Name =
On Wed, Nov 25, 2009 at 10:08 AM, David Dumortier
wrote:
>
> John Drescher a écrit :
>> On Wed, Nov 25, 2009 at 4:07 AM, David Dumortier
>> wrote:
>>> Hi all,
>>>
>>> David Dumortier a écrit :
Hello,
John Drescher a écrit :
> On Mon, Nov 23, 2009 at 4:16 AM, David Dumortier
>>>
Dear,
The client of version 3 are funcional with Windows 7 professional ?
someone did the test?
Thanks
Mauricio
--
**
Mauricio Bertholino
mauri...@bertholino.com.br
Fone: 11-7616-0777
**
---
On Wed, 25 Nov 2009, bac...@bertholino.com.br wrote:
> The client of version 3 are funcional with Windows 7 professional ?
I have installed a bacula-fd v3.0.3 on Windows 7 Professional and run some
backups against it successfully.
I wouldn't call it rigorous testing, but it seemed to work fine.
Hi,
25.11.2009 14:20, Sascha Retzki wrote:
> Hello List,
>
> I've got a best practice question. When a Job is started it changes to
> Status=Running and the FD tries to connect to the SD. Let's assume this
> fails due to network outages, or in my case I configured an IP for the
> SD which is n
> > After updating two Bacula 3.0.2 servers to version 3.0.3 both of them
> > started to claim this:
> >
> >
> > /etc/cron.daily/0logwatch:
> >
> > Cannot find shared script applybaculadate
> >
> >
> > Both are 64-bit CentOS5 systems, rpm installations.
> >
> > This is obviously due to so
Hi,
25.11.2009 20:16, Timo Neuvonen wrote:
>>> After updating two Bacula 3.0.2 servers to version 3.0.3 both of them
>>> started to claim this:
>>>
>>>
>>> /etc/cron.daily/0logwatch:
>>>
>>> Cannot find shared script applybaculadate
>>>
>>>
>>> Both are 64-bit CentOS5 systems, rpm instal
Chandranshu . wrote:
>
> The only change I made was to insert the password 'bacula' in the
> bacula-dir.conf file in the CATALOG section. And this was after it didn't
> work without passwords. The relevant section of the bacula-dir.conf file is:
> # Generic catalog service
> Catalog {
> Name
It is my understanding that one must use the same job name for full and
incremental backups, otherwise Bacula is not able to perform an
incremental backup.
I have a need to send full backups of machines to one disk and
incremental backups to another disk. If I have to use the same job
definition f
Moby schrieb:
> It is my understanding that one must use the same job name for full and
> incremental backups, otherwise Bacula is not able to perform an
> incremental backup.
> I have a need to send full backups of machines to one disk and
> incremental backups to another disk. If I have to use t
13 matches
Mail list logo
