Hi,
29.01.2009 11:19, ToMasz wrote:
> I've been using bacula 1.38.11 for some time and recently upgraded
> successfully one of my file daemons to ver. 2.4.4.
> Now I'm thinking about complete upgrade on all machines including
> director but am unsure about possible pitfalls.
There are some pitfal
On Thu, Jan 29, 2009 at 9:45 AM, Allan Black wrote:
> John Drescher wrote:
>> On Thu, Jan 29, 2009 at 5:19 AM, ToMasz wrote:
>>> I've been using bacula 1.38.11 for some time and recently upgraded
>>> successfully one of my file daemons to ver. 2.4.4.
>>> Now I'm thinking about complete upgrade on
John Drescher wrote:
> On Thu, Jan 29, 2009 at 5:19 AM, ToMasz wrote:
>> I've been using bacula 1.38.11 for some time and recently upgraded
>> successfully one of my file daemons to ver. 2.4.4.
>> Now I'm thinking about complete upgrade on all machines including
>> director but am unsure about pos
John Drescher wrote:
> On Thu, Jan 29, 2009 at 5:19 AM, ToMasz wrote:
>> I've been using bacula 1.38.11 for some time and recently upgraded
>> successfully one of my file daemons to ver. 2.4.4.
>> Now I'm thinking about complete upgrade on all machines including
>> director but am unsure about pos
On Thu, Jan 29, 2009 at 5:19 AM, ToMasz wrote:
> I've been using bacula 1.38.11 for some time and recently upgraded
> successfully one of my file daemons to ver. 2.4.4.
> Now I'm thinking about complete upgrade on all machines including
> director but am unsure about possible pitfalls.
> Will my c
I've been using bacula 1.38.11 for some time and recently upgraded
successfully one of my file daemons to ver. 2.4.4.
Now I'm thinking about complete upgrade on all machines including
director but am unsure about possible pitfalls.
Will my config files still work? Or maybe newer versions use other
