On 02/26/2015 07:19 PM, Heitor Faria wrote:
>> On 02/26/2015 03:08 PM, Heitor Faria wrote:
>>> [...] I was auto-labeling the volumes for each job like:
>>> xxx-1.bac, xxx-2.bac, xxx-.bac, etc where starts at 1
>>> for each job. Is there some variable that has that behavior?
>>> [..
> On 02/26/2015 03:08 PM, Heitor Faria wrote:
> > [...] I was auto-labeling the volumes for each job like:
> > xxx-1.bac, xxx-2.bac, xxx-.bac, etc where starts at 1
> > for each job. Is there some variable that has that behavior?
> > [...]
> >>>
> >>> Hey Mr. McGraw: you should try
On 02/26/2015 03:08 PM, Heitor Faria wrote:
> [...] I was auto-labeling the volumes for each job like:
> xxx-1.bac, xxx-2.bac, xxx-.bac, etc where starts at 1
> for each job. Is there some variable that has that behavior?
> [...]
>>>
>>> Hey Mr. McGraw: you should try LabelFormat =
> >>> [...]
> >>> I was auto-labeling the volumes for each job like: xxx-1.bac,
> >>> xxx-2.bac, xxx-.bac, etc where starts at 1 for each job.
> >>> Is there some variable that has that behavior?
> >>> [...]
> >
> > Hey Mr. McGraw: you should try LabelFormat = "xxx-${NumVols}.bac"
> > What is xxx?
On 02/26/2015 06:11 AM, Heitor Faria wrote:
>> On 02/23/2015 10:45 AM, S McGraw wrote:
>>> [...]
>>> I was auto-labeling the volumes for each job like: xxx-1.bac,
>>> xxx-2.bac, xxx-.bac, etc where starts at 1 for each job.
>>> Is there some variable that has that behavior?
>>> [...]
>
> Hey Mr. M
- Mensagem original -
> De: "S McGraw"
> Para: bacula-users@lists.sourceforge.net
> Enviadas: Quarta-feira, 25 de fevereiro de 2015 23:08:12
> Assunto: Re: [Bacula-users] Status of Python api?
>
> On 02/23/2015 10:45 AM, S McGraw wrote:
> >[...]
> > I was auto-labeling the volumes for
On Wed, 25 Feb 2015 17:42:48 -0800
Periko Support wrote:
> I have a Centos 5x x64 with bacula 5.x running, I need to replace my
> tape(Tandberg) 200/400 with a bigger one, but I have some doubts if
> some else is running tandberg LTO-4 800/1.6GB scsi external without
> issues?
I'm running Tandbe