Re: [Bacula-users] Labeling when using native virtual autochanger

Thank you Dan :) Regards, Ana On Fri, Oct 23, 2015 at 9:51 AM, Dan Langille wrote: > > On Sep 12, 2015, at 2:42 PM, Ana Emília M. Arruda > wrote: > > Hello Dan, > > On Sun, Sep 6, 2015 at 6:56 PM, Dan Langille wrote: > >> I'm not

Re: [Bacula-users] Labeling when using native virtual autochanger

> On Sep 12, 2015, at 2:42 PM, Ana Emília M. Arruda > wrote: > > Hello Dan, > > On Sun, Sep 6, 2015 at 6:56 PM, Dan Langille > wrote: > I'm not sure if this is a configuration problem or

Re: [Bacula-users] Labeling when using native virtual autochanger

Hello Dan, On Sun, Sep 6, 2015 at 6:56 PM, Dan Langille wrote: > I'm not sure if this is a configuration problem or not. The problem > recurred later in the day when the pool filled up. > ​I don't think this is a configuration problem, but ​a version 7.0.5 bug. I was able

Re: [Bacula-users] Labeling when using native virtual autochanger

I'm not sure if this is a configuration problem or not. The problem recurred later in the day when the pool filled up. > On Sep 6, 2015, at 11:16 AM, Dan Langille > wrote: > > >> On Sep 6, 2015, at 9:51 AM, Dan Langille >

Re: [Bacula-users] Labeling when using native virtual autochanger

This is a long post but contains details which might hint at the cause of the problem. The backups have resumed, but the underlying problem persists. > On Sep 4, 2015, at 3:34 PM, Dan Langille > wrote: > > >> On Sep 3, 2015, at 12:26 AM, Ana

Re: [Bacula-users] Labeling when using native virtual autochanger

> On Sep 6, 2015, at 9:51 AM, Dan Langille > wrote: > > This is a long post but contains details which might hint at the cause of the > problem. > > The backups have resumed, but the underlying problem persists. > > >> On Sep 4, 2015, at 3:34

Re: [Bacula-users] Labeling when using native virtual autochanger

> On Sep 3, 2015, at 12:26 AM, Ana Emília M. Arruda > wrote: > > Hello Dan, > > On Wed, Sep 2, 2015 at 11:06 PM, Dan Langille > wrote: > >> On Aug 25, 2015, at 6:55 PM, Ana Emília M.

Re: [Bacula-users] Labeling when using native virtual autochanger

Hello Dan, On Wed, Sep 2, 2015 at 11:06 PM, Dan Langille wrote: > > On Aug 25, 2015, at 6:55 PM, Ana Emília M. Arruda > wrote: > > Hello Dan, > > Heitor is right :) > > > Thank you. > > Ana: what are you using to quickly test these configurations? I

Re: [Bacula-users] Labeling when using native virtual autochanger

> On Aug 25, 2015, at 6:55 PM, Ana Emília M. Arruda > wrote: > > Hello Dan, > > Heitor is right :) Thank you. Ana: what are you using to quickly test these configurations? I suspect a VM or similar. > > I run tests with exactly

Re: [Bacula-users] Labeling when using native virtual autochanger

Hello, 2015-08-25 23:13 GMT+02:00 Heitor Faria hei...@bacula.com.br: Dan, At a glance I think you must have a Drive Index=0 at the universe of drives of your autochanger. Device = vDrive-1, vDrive-2, vDrive-3, vDrive-4, vDrive-5 I never considered that I needed to start indexing

Re: [Bacula-users] Labeling when using native virtual autochanger

Dan, On your Virtual Autochanger, you are doing two things different from what I have always done, which could potential create problems for you. The two directives that you should remove from your Virtual Autochanger Device definitions are: AlwaysOpen = yes RemovableMedia = yes Best

Re: [Bacula-users] Labeling when using native virtual autochanger

On Aug 25, 2015, at 8:43 AM, Josh Fisher jfis...@pvct.com wrote: On 8/24/2015 5:24 PM, Dan Langille wrote: I recently started using the Virtual Autochanger as described in 'Best Practices for Disk Based Backup' [1] It is working for me, but I encountered a problem with the

Re: [Bacula-users] Labeling when using native virtual autochanger

On 08/25/2015 03:47 PM, Dan Langille wrote: Lots of space on there: $ zfs list system/usr/local/bacula NAME USED AVAIL REFER MOUNTPOINT system/usr/local/bacula 11.1T 4.42T 10.4T /usr/jails/crey/usr/local/bacula Are you sure it's supposed to work? I was under

Re: [Bacula-users] Labeling when using native virtual autochanger

On Aug 25, 2015, at 7:03 AM, Ana Emília M. Arruda emiliaarr...@gmail.com wrote: Hello again, Have you noticed a device not found error in your bconsole messages? *mount The defined Storage resources are: 1: CreyFile 2: CompaqStorageWorksTapeLibrary Select Storage

Re: [Bacula-users] Labeling when using native virtual autochanger

] Labeling when using native virtual autochanger On Aug 25, 2015, at 8:43 AM, Josh Fisher jfis...@pvct.com wrote: On 8/24/2015 5:24 PM, Dan Langille wrote: I recently started using the Virtual Autochanger as described in 'Best Practices for Disk Based Backup' [1] It is working for me

Re: [Bacula-users] Labeling when using native virtual autochanger

Hello Dan, I was unable to reproduce this. The only situation where I got the error: 24-Aug 01:45 bacula-dir JobId 215534: Created new Volume=DiffAuto-4861, Pool=DiffFile, MediaType=File in catalog. 24-Aug 01:45 crey-sd JobId 215534: Warning: mount.c:212 Open of file device vDrive-1

Re: [Bacula-users] Labeling when using native virtual autochanger

Hello again, Have you noticed a device not found error in your bconsole messages? *mountThe defined Storage resources are: 1: CreyFile 2: CompaqStorageWorksTapeLibrarySelect Storage resource (1-2): 1Connecting to Storage daemon CreyFile at crey.int.unixathome.org:9103 ...Enter autochanger

Re: [Bacula-users] Labeling when using native virtual autochanger

Hello Dan, Heitor is right :) I run tests with exactly your configuration and had the same issue. The drive index 0 must exist and belongs to the autochanger resource. You have an Index 0 drive in your configuration: vRestore. But it is not in the Autochanger definition. If you put it there, it

Re: [Bacula-users] Labeling when using native virtual autochanger

Dan, At a glance I think you must have a Drive Index=0 at the universe of drives of your autochanger. Device = vDrive-1, vDrive-2, vDrive-3, vDrive-4, vDrive-5 I never considered that I needed to start indexing my drives from zero. Hmm. Thank you. I will look into that. It is just

Re: [Bacula-users] Labeling when using native virtual autochanger

On Aug 25, 2015, at 4:56 PM, Dimitri Maziuk dmaz...@bmrb.wisc.edu wrote: On 08/25/2015 03:47 PM, Dan Langille wrote: Lots of space on there: $ zfs list system/usr/local/bacula NAME USED AVAIL REFER MOUNTPOINT system/usr/local/bacula 11.1T 4.42T 10.4T

Re: [Bacula-users] Labeling when using native virtual autochanger

On Aug 25, 2015, at 4:54 PM, Heitor Faria hei...@bacula.com.br wrote: Dan, At a glance I think you must have a Drive Index=0 at the universe of drives of your autochanger. Device = vDrive-1, vDrive-2, vDrive-3, vDrive-4, vDrive-5 I never considered that I needed to start indexing my

Re: [Bacula-users] Labeling when using native virtual autochanger

On Aug 25, 2015, at 5:13 PM, Heitor Faria hei...@bacula.com.br wrote: Dan, At a glance I think you must have a Drive Index=0 at the universe of drives of your autochanger. Device = vDrive-1, vDrive-2, vDrive-3, vDrive-4, vDrive-5 I never considered that I needed to start indexing

Re: [Bacula-users] Labeling when using native virtual autochanger

On 8/24/2015 5:24 PM, Dan Langille wrote: I recently started using the Virtual Autochanger as described in 'Best Practices for Disk Based Backup' [1] It is working for me, but I encountered a problem with the audo-label process. My bacula-sd.conf and the full transcript of the logging

[Bacula-users] Labeling when using native virtual autochanger

I recently started using the Virtual Autochanger as described in 'Best Practices for Disk Based Backup' [1] It is working for me, but I encountered a problem with the audo-label process. My bacula-sd.conf and the full transcript of the logging problem is at: