Hello Josh, You're right, in the case of a virtual two-drive autochanger, if we configure the second drive (index 1) as read only, the drive index 0 (read/write) will be selected for reading and there will no available drive for writing since the second one is read only.
The way this could be solved is configuring the first drive as read only. This worked for me for a two-drive autochanger and virtual full backup. I've not tested this with physical autochangers. Best regards, Ana On Fri, Sep 4, 2015 at 5:02 PM, Josh Fisher <[email protected]> wrote: > > > On 9/4/2015 2:06 PM, Ana Emília M. Arruda wrote: > > Hello Josh, > > Are you using a physical or virtual autochanger? > > I haven´t tried the read-only feature yet. But I was wondering if in the > case of a physical autochanger you could have the read-only drive also > configured as a standalone drive. This way it would be possible to > configure your Virtual Full to use this standalone drive for reading and > all the other ones for writing. > > > This is with a virtual autochanger. But how is does one specify the read > drive separately from the write drive? > > > Best regards, > Ana > > On Fri, Sep 4, 2015 at 11:56 AM, Josh Fisher <[email protected]> wrote: > >> Is anyone using the relatively new read-only feature of Device >> resources? I had thought to use this feature to reserve an autochanger >> drive as the read drive for virtual full backups. But in a two-drive >> autochanger, making drive 1 read-only is problematic. A virtual full job >> will select the read drive before it selects the write drive. I have >> confirmed that it will, or at least can, select drive 0 (the read/write >> drive) as the read drive for the virtual full job and then be stuck >> without a writable drive, causing the job to fail. I would have thought >> that when selecting a read drive for a virtual full or copy job that the >> selection would prefer an available read-only drive over an available >> read/write drive, but that does not seem to be the case. Any thoughts? >> >> >> ------------------------------------------------------------------------------ >> _______________________________________________ >> Bacula-users mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/bacula-users >> > > > > ------------------------------------------------------------------------------ > > > > _______________________________________________ > Bacula-users mailing > [email protected]https://lists.sourceforge.net/lists/listinfo/bacula-users > > >
------------------------------------------------------------------------------
_______________________________________________ Bacula-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bacula-users
