On Tue, Dec 17, 2013 at 03:19:57PM +0100, stefano scotti wrote:
> Do you, Uwe, confirm that an Autochanger is the only way to have working
> and automated restore jobs with volumes in different directories?
>
> Thank you again.
Hi Stefano,
I've never used the virtual autochanger so I cannot real
> 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
2013/12/16 Uwe Schuerkamp
> On Fri, Dec 13, 2013 at 04:43:29PM +0100, stefano scotti wrote:
> > i took a step forward.
> >
> > i understood that the problem arise only if i try to restore a directory
> > whose files are present in different volumes.
> > if i try to restore a single file i don't h
On Fri, Dec 13, 2013 at 04:43:29PM +0100, stefano scotti wrote:
> i took a step forward.
>
> i understood that the problem arise only if i try to restore a directory
> whose files are present in different volumes.
> if i try to restore a single file i don't have any problem, that's because
> Bacul
> thank you John for your clarification.
The problem is you can not switch storage devices during a single job.
You need to have all of your data on the same storage device.
> do you know how i can realize a "virtual disk autochanger" configuration or
> where i can find some documentation about i
2013/12/13 John Drescher
>
>
>
> On Fri, Dec 13, 2013 at 10:43 AM, stefano scotti <
> scottistefan...@gmail.com> wrote:
>
>> i took a step forward.
>>
>> i understood that the problem arise only if i try to restore a directory
>> whose files are present in different volumes.
>> if i try to restor
> 10-dic 17:46 thisdir-sd JobId 762: acquire.c:121 Changing read
> device. Want Media Type="JobName_diff" have="JobName_full"
>device="JobName_full" (/path/to/storage/JobName_full)
I think that you want to make sure the Media Type for each Storage
Device is "File". It looks like
On Fri, Dec 13, 2013 at 10:43 AM, stefano scotti
wrote:
> i took a step forward.
>
> i understood that the problem arise only if i try to restore a directory
> whose files are present in different volumes.
> if i try to restore a single file i don't have any problem, that's because
> Bacula is abl
i took a step forward.
i understood that the problem arise only if i try to restore a directory
whose files are present in different volumes.
if i try to restore a single file i don't have any problem, that's because
Bacula is able to identify the correct volume associated with that file.
but, if
13 matches
Mail list logo