Hi Marco
Please explain your fork of Bacula with reference in particular to
https://github.com/bareos/bareos/tree/9e1f8dc06d606e11a2128a29dc7cb0a55adcdaf3
It would be also useful if you could explain your reasons for the fork
to the Bacula community.
Is it true you were an commercial subcontrac
There is some stuff I still don't understand here, and I'd like to avoid
learning the hard way. For instance, I never realized that "File
Retention" referred to the individual file records in the database, not
to the actual files on backup. So I ended up losing many of my File
records (learning the
Hello Paul,
Thank you for your kind words; they mean much more to me than
you might imagine.
I for one use lots of open source, but find time to contribute to Bacula,
so I understand that not everyone contribute. Besides for me the
greatest part
of Bacula is knowing that lots of people use it an
> That seems a working solution, but creating a symbolic link for every
> volume required by a restore job introduces a manual operation that
> would be better to avoid, especially if a lot of incremental volumes are
> being considered.
We use symbolic links here and have never had any problems.
On Tue, Dec 17, 2013 at 9:36 AM, John Drescher wrote:
>> But, in my opinion, an Autochanger is a too specific tape related concept
>> that introduces a lot of complexity that is not really needed by a
>> filesystem solution, i'd prefer not to deal with redundant configuration
>> tasks performed ex
> But, in my opinion, an Autochanger is a too specific tape related concept
> that introduces a lot of complexity that is not really needed by a
> filesystem solution, i'd prefer not to deal with redundant configuration
> tasks performed exclusively in order to work around software architectural
>
2013/12/17 Uwe Schuerkamp
> On Mon, Dec 16, 2013 at 05:09:18PM +0100, stefano scotti wrote:
> >
> >
> > The problem here is that different storages refer to different
> > directories, and Bacula pretends to find the new volume in the same
> > directory of the old one.
> > Now that the MediaType
On Mon, Dec 16, 2013 at 05:09:18PM +0100, stefano scotti wrote:
>
>
> The problem here is that different storages refer to different
> directories, and Bacula pretends to find the new volume in the same
> directory of the old one.
> Now that the MediaType is the same, no fatal errors are expose
