Re: [Bacula-users] Status of Python api?
On 02/27/2015 09:59 AM, Heitor Faria wrote: > >>> ... [I] ponder if it might be worthwhile to rethink the way I am >>> doing backups. >> >> How much manual work is involved and how much is the time of whoever >> does it worth? E.g. RDX might me cheaper. Or BackupPC. > > [2] Or hiring a VPS (e.g.: www.chicagovps.net) and install a bacula-sd on it. > =) I expect Amazon VTL is even better, but I don't think that gives you physical DVDs. As I understand it, sending BackupPC's "archive" job to a DVD is trivial, except you still have to put the disk in the drive -- dep. on how often you do that, RDX may be a better option. -- Dimitri Maziuk Programmer/sysadmin BioMagResBank, UW-Madison -- http://www.bmrb.wisc.edu signature.asc Description: OpenPGP digital signature -- Dive into the World of Parallel Programming The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Status of Python api?
> > All post-bacula handling (write to DVD, off-siting, moving > > storage locations around to fit varying storage needs/capacities, > > etc) are done by hand or with the help of scripts > > > ... [I] ponder if it might be worthwhile to rethink the way I am > > doing backups. > > How much manual work is involved and how much is the time of whoever > does it worth? E.g. RDX might me cheaper. Or BackupPC. [2] Or hiring a VPS (e.g.: www.chicagovps.net) and install a bacula-sd on it. =) > Dimitri > > -- Dive into the World of Parallel Programming The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Status of Python api?
On 2015-02-26 19:06, S McGraw wrote: > All post-bacula handling (write to DVD, off-siting, moving > storage locations around to fit varying storage needs/capacities, > etc) are done by hand or with the help of scripts > ... [I] ponder if it might be worthwhile to rethink the way I am > doing backups. How much manual work is involved and how much is the time of whoever does it worth? E.g. RDX might me cheaper. Or BackupPC. Dimitri -- Dive into the World of Parallel Programming The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Status of Python api?
* DVDs=$(bc <<< "$Bytes / (4724464025.6 ^ 2)")
==
Heitor Medrado de Faria - LPIC-III | ITIL-F
02 a 13 de Março - Novo Treinamento Telepresencial Bacula:
http://www.bacula.com.br/?p=2174
61 8268-4220
Site: www.bacula.com.br | Facebook: heitor.faria | Gtalk: heitorfa...@gmail.com
===
- Mensagem original -
> De: "Heitor Faria"
> Para: "S McGraw"
> Cc: bacula-users@lists.sourceforge.net
> Enviadas: Sexta-feira, 27 de fevereiro de 2015 11:08:23
> Assunto: Re: [Bacula-users] Status of Python api?
>
>
> > That's an interesting suggestion. I was worried the "estimate"
> > command might be very slow but it seemed quick enough. Perhaps a
> > potential problem might be a difference between the estimate and
> > actual bytes, perhaps because a large file was created in the
> > interim.
> >
> > Another possibility occurred to me prompted by your idea... again
> > in a RunBeforeJob script, label a fixed number of volumes (I can
> > put a fairly accurate upper bound on the backup data size for each
> > client) and after the job delete the volumes that were not used.
> > I'm not immediately sure the best way to determine which weren't
> > used but I think that won't be too hard. I guess the risk here
> > is that if the after job failed for some reason, the unused volumes
> > would be left in the pool and would be used the next night.
>
> Mr. McGraw: I know it's not you want but I got curious, if you wanna test...
>
> create_volumes_before_job.sh:
>
> Bytes=$(echo "estimate job=BackupClient1 level=$Level" | bconsole | sed
> '/bytes=/!d;s/^.*bytes=//;s/[.,]//g')
> echo " Job total Bytes=$Bytes "
> DVDs=$(bc <<< "$Bytes / (4.4 * 1024 ^ 2)")
> echo " DVDs required=$DVDs "
> for ((Counter=0; Counter<=$DVDs; Counter++))
> {
>echo "label pool=Default storage=File1 volume=BackupClient1-$Counter"
>|bconsole
>Counter=$((Counter + 1))
> }
>
> --
> Dive into the World of Parallel Programming The Go Parallel Website,
> sponsored
> by Intel and developed in partnership with Slashdot Media, is your hub for
> all
> things parallel software development, from weekly thought leadership blogs to
> news, videos, case studies, tutorials and more. Take a look and join the
> conversation now. http://goparallel.sourceforge.net/
> ___
> Bacula-users mailing list
> Bacula-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bacula-users
>
--
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the
conversation now. http://goparallel.sourceforge.net/
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Status of Python api?
> That's an interesting suggestion. I was worried the "estimate"
> command might be very slow but it seemed quick enough. Perhaps a
> potential problem might be a difference between the estimate and
> actual bytes, perhaps because a large file was created in the
> interim.
>
> Another possibility occurred to me prompted by your idea... again
> in a RunBeforeJob script, label a fixed number of volumes (I can
> put a fairly accurate upper bound on the backup data size for each
> client) and after the job delete the volumes that were not used.
> I'm not immediately sure the best way to determine which weren't
> used but I think that won't be too hard. I guess the risk here
> is that if the after job failed for some reason, the unused volumes
> would be left in the pool and would be used the next night.
Mr. McGraw: I know it's not you want but I got curious, if you wanna test...
create_volumes_before_job.sh:
Bytes=$(echo "estimate job=BackupClient1 level=$Level" | bconsole | sed
'/bytes=/!d;s/^.*bytes=//;s/[.,]//g')
echo " Job total Bytes=$Bytes "
DVDs=$(bc <<< "$Bytes / (4.4 * 1024 ^ 2)")
echo " DVDs required=$DVDs "
for ((Counter=0; Counter<=$DVDs; Counter++))
{
echo "label pool=Default storage=File1 volume=BackupClient1-$Counter"
|bconsole
Counter=$((Counter + 1))
}
--
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the
conversation now. http://goparallel.sourceforge.net/
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Status of Python api?
On Thu, Feb 26, 2015 at 10:06 PM, S McGraw 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?
>> [...]
Hey Mr. McGraw: you should try LabelFormat =
"xxx-${NumVols}.bac" What is xxx? If is the client name you can
uses ${Client}. You could check all Bacula Variables via Google:
http://www.bacula.org/5.2.x-manuals/en/misc/misc/Variable_Expansion.html
>>>
> >> Thanks for that suggestion. I read the Variable Expansion
>>> chapter many times but interpreted "current number of Volumes in
>>> the Pool" as being a fixed number for a pool with a large number of
>>> pre-labeled volumes.
>>>
>>> I just tried using NumVols but the number it produced was 5177. I
>>> guess was wrong about the pre-labeled part but it does seem to be
>>> total number of volumes in the pool and not a number for the
>>> volumes used in the current job so far which is what I need.
>>
>> 1. Sorry for misunderstanding it. I really don't see the need of
>> associating volumes names with their jobs and it can be very messy
>> when they are recycled, since a Job can take a variable amount of
>> volumes and Bacula already provide that association (e.g: list
>> jobmedia, restore job..., etc.).
>
> I agree it is messy (I would say unworkable) when recycling is
> used but I don't do recycling.
>
> I backup to smaller-than-DVD sized disk volumes and write those
> to DVD. In such an environment, volume recycling is pointless.
>
> All post-bacula handling (write to DVD, off-siting, moving
> storage locations around to fit varying storage needs/capacities,
> etc) are done by hand or with the help of scripts since Bacula
> provides no support for DVD as a storage medium. I find it
> easier to manage those tasks when I can look at filename and
> be able to determine information about what is in the volume
> than to have to go though a level of indirection for that information,
> either by asking Bacula or querying the catalog database directly.
> And of course the current labeling scheme is baked into the
> scripts that I have to help with the post-bacula volume management.
>
> I've been using the current labeling scheme successfully for
> 5 years, including disaster recovery simulation so I don't see
> a strong reason to change now unless I have to.
Hi,
are you sure that you cant configure bacula to make a backup direct to DVD ???
I have one client configured to use a DVD storage just now.
basicaly, I backup all information from clients to internal bacula
disk and after this I make a job copy to DVD (internal disk to DVD).
about the label name, if the idea is just to "make easy" to manual
select the volume... maybe you can use:
Client_name-Date-JodID
good luck
--
--
Victor Hugo dos Santos
http://www.vhsantos.net
Linux Counter #224399
--
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the
conversation now. http://goparallel.sourceforge.net/
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Status of Python api?
--
Heitor Medrado de Faria
+55 61 82684220
Precisa de treinamento Bacula presencial, telepresencial ou online? Acesse:
http://www.bacula.com.br
>> Just an idea: you could use a RunBeforeJob Shell Script to create the
>number of volumes needed to complete a job. Something like that:
>>
>> echo "estimate job=BackupClient1 level=${Level}" |bconsole |grep -o
>-P 'bytes.{0,16}'
>>
>> Then clear the bytes= from the result, divide per 4.4Gb (?) and than
>create the needed volumes:
>>
>> echo "label pool=${Pool} storage=${Storage}
>volume=-shell-variable" |bconsole
>>
>> The full solution requires shell script knowledge that I don't have,
>but I think it's the closest thing to the Python script you had.
>> Good luck.
>
>That's an interesting suggestion. I was worried the "estimate"
>command might be very slow but it seemed quick enough. Perhaps a
>potential problem might be a difference between the estimate and
>actual bytes, perhaps because a large file was created in the
>interim.
>
>Another possibility occurred to me prompted by your idea... again
>in a RunBeforeJob script, label a fixed number of volumes (I can
>put a fairly accurate upper bound on the backup data size for each
>client) and after the job delete the volumes that were not used.
>I'm not immediately sure the best way to determine which weren't
>used but I think that won't be too hard. I guess the risk here
>is that if the after job failed for some reason, the unused volumes
>would be left in the pool and would be used the next night.
You can run an AfterJob script even if job fails. I think it's the RunOnError
option.
Best regards.
--
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the
conversation now. http://goparallel.sourceforge.net/
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Status of Python api?
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?
>>> [...]
>
> Hey Mr. McGraw: you should try LabelFormat =
> "xxx-${NumVols}.bac" What is xxx? If is the client name you can
> uses ${Client}. You could check all Bacula Variables via Google:
> http://www.bacula.org/5.2.x-manuals/en/misc/misc/Variable_Expansion.html
>> >> Thanks for that suggestion. I read the Variable Expansion
chapter many times but interpreted "current number of Volumes in
the Pool" as being a fixed number for a pool with a large number of
pre-labeled volumes.
I just tried using NumVols but the number it produced was 5177. I
guess was wrong about the pre-labeled part but it does seem to be
total number of volumes in the pool and not a number for the
volumes used in the current job so far which is what I need.
>>>
>>> 1. Sorry for misunderstanding it. I really don't see the need of
>>> associating volumes names with their jobs and it can be very messy
>>> when they are recycled, since a Job can take a variable amount of
>>> volumes and Bacula already provide that association (e.g: list
>>> jobmedia, restore job..., etc.).
>>
>> I agree it is messy (I would say unworkable) when recycling is
>> used but I don't do recycling.
>>
>> I backup to smaller-than-DVD sized disk volumes and write those
>> to DVD. In such an environment, volume recycling is pointless.
>>
>> All post-bacula handling (write to DVD, off-siting, moving
>> storage locations around to fit varying storage needs/capacities,
>> etc) are done by hand or with the help of scripts since Bacula
>> provides no support for DVD as a storage medium. I find it
>> easier to manage those tasks when I can look at filename and
>> be able to determine information about what is in the volume
>> than to have to go though a level of indirection for that information,
>> either by asking Bacula or querying the catalog database directly.
>> And of course the current labeling scheme is baked into the
>> scripts that I have to help with the post-bacula volume management.
>
> echo "estimate job=BackupClient1 level=${Level}" |bconsole |grep -o -P
> 'bytes.{0,16}'
>
> Just an idea: you could use a RunBeforeJob Shell Script to create the number
> of volumes needed to complete a job. Something like that:
>
> echo "estimate job=BackupClient1 level=${Level}" |bconsole |grep -o -P
> 'bytes.{0,16}'
>
> Then clear the bytes= from the result, divide per 4.4Gb (?) and than create
> the needed volumes:
>
> echo "label pool=${Pool} storage=${Storage} volume=-shell-variable"
> |bconsole
>
> The full solution requires shell script knowledge that I don't have, but I
> think it's the closest thing to the Python script you had.
> Good luck.
That's an interesting suggestion. I was worried the "estimate"
command might be very slow but it seemed quick enough. Perhaps a
potential problem might be a difference between the estimate and
actual bytes, perhaps because a large file was created in the
interim.
Another possibility occurred to me prompted by your idea... again
in a RunBeforeJob script, label a fixed number of volumes (I can
put a fairly accurate upper bound on the backup data size for each
client) and after the job delete the volumes that were not used.
I'm not immediately sure the best way to determine which weren't
used but I think that won't be too hard. I guess the risk here
is that if the after job failed for some reason, the unused volumes
would be left in the pool and would be used the next night.
I'll look into both of these ideas more next week, thanks!
--
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the
conversation now. http://goparallel.sourceforge.net/
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Status of Python api?
> 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 =
> >>> "xxx-${NumVols}.bac" What is xxx? If is the client name you can
> >>> uses ${Client}. You could check all Bacula Variables via Google:
> >>> http://www.bacula.org/5.2.x-manuals/en/misc/misc/Variable_Expansion.html
> >>
> >> Thanks for that suggestion. I read the Variable Expansion
> >> chapter many times but interpreted "current number of Volumes in
> >> the Pool" as being a fixed number for a pool with a large number of
> >> pre-labeled volumes.
> >>
> >> I just tried using NumVols but the number it produced was 5177. I
> >> guess was wrong about the pre-labeled part but it does seem to be
> >> total number of volumes in the pool and not a number for the
> >> volumes used in the current job so far which is what I need.
> >
> > 1. Sorry for misunderstanding it. I really don't see the need of
> > associating volumes names with their jobs and it can be very messy
> > when they are recycled, since a Job can take a variable amount of
> > volumes and Bacula already provide that association (e.g: list
> > jobmedia, restore job..., etc.).
>
> I agree it is messy (I would say unworkable) when recycling is
> used but I don't do recycling.
>
> I backup to smaller-than-DVD sized disk volumes and write those
> to DVD. In such an environment, volume recycling is pointless.
>
> All post-bacula handling (write to DVD, off-siting, moving
> storage locations around to fit varying storage needs/capacities,
> etc) are done by hand or with the help of scripts since Bacula
> provides no support for DVD as a storage medium. I find it
> easier to manage those tasks when I can look at filename and
> be able to determine information about what is in the volume
> than to have to go though a level of indirection for that information,
> either by asking Bacula or querying the catalog database directly.
> And of course the current labeling scheme is baked into the
> scripts that I have to help with the post-bacula volume management.
echo "estimate job=BackupClient1 level=${Level}" |bconsole |grep -o -P
'bytes.{0,16}'
Just an idea: you could use a RunBeforeJob Shell Script to create the number of
volumes needed to complete a job. Something like that:
echo "estimate job=BackupClient1 level=${Level}" |bconsole |grep -o -P
'bytes.{0,16}'
Then clear the bytes= from the result, divide per 4.4Gb (?) and than create the
needed volumes:
echo "label pool=${Pool} storage=${Storage} volume=-shell-variable"
|bconsole
The full solution requires shell script knowledge that I don't have, but I
think it's the closest thing to the Python script you had.
Good luck.
Regards,
==
Heitor Medrado de Faria - LPIC-III | ITIL-F
02 a 13 de Março - Novo Treinamento Telepresencial Bacula:
http://www.bacula.com.br/?p=2174
61 8268-4220
Site: www.bacula.com.br | Facebook: heitor.faria | Gtalk: heitorfa...@gmail.com
===
--
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the
conversation now. http://goparallel.sourceforge.net/
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Status of Python api?
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 =
>>> "xxx-${NumVols}.bac" What is xxx? If is the client name you can
>>> uses ${Client}. You could check all Bacula Variables via Google:
>>> http://www.bacula.org/5.2.x-manuals/en/misc/misc/Variable_Expansion.html
>>
>> Thanks for that suggestion. I read the Variable Expansion
>> chapter many times but interpreted "current number of Volumes in
>> the Pool" as being a fixed number for a pool with a large number of
>> pre-labeled volumes.
>>
>> I just tried using NumVols but the number it produced was 5177. I
>> guess was wrong about the pre-labeled part but it does seem to be
>> total number of volumes in the pool and not a number for the
>> volumes used in the current job so far which is what I need.
>
> 1. Sorry for misunderstanding it. I really don't see the need of
> associating volumes names with their jobs and it can be very messy
> when they are recycled, since a Job can take a variable amount of
> volumes and Bacula already provide that association (e.g: list
> jobmedia, restore job..., etc.).
I agree it is messy (I would say unworkable) when recycling is
used but I don't do recycling.
I backup to smaller-than-DVD sized disk volumes and write those
to DVD. In such an environment, volume recycling is pointless.
All post-bacula handling (write to DVD, off-siting, moving
storage locations around to fit varying storage needs/capacities,
etc) are done by hand or with the help of scripts since Bacula
provides no support for DVD as a storage medium. I find it
easier to manage those tasks when I can look at filename and
be able to determine information about what is in the volume
than to have to go though a level of indirection for that information,
either by asking Bacula or querying the catalog database directly.
And of course the current labeling scheme is baked into the
scripts that I have to help with the post-bacula volume management.
I've been using the current labeling scheme successfully for
5 years, including disaster recovery simulation so I don't see
a strong reason to change now unless I have to.
> 2. Anyway I'm on a deadlock here: if you submit all jobs for a same
> pool you can't guarantee the job will occupy only the volumes with
> respective name on it, and a more secure way would be have them in
> different pools, where ${NumVols} would work if you are recycling
> them.
Yes, I have a separate pool for each client machine.
> 3. You could use variables like ${JobId} plus time (Month, Day, Hour,
> Minute, Second) in order to create unique volume names in a
> chronological order, similar to what you want, providing that you are
> always are creating new volumes for each job.
Yes, that was my fallback plan if I couldn't get a volume number.
My 2nd level fallback was to give up and just use VOL0001, VOL0002,
etc and live with the inconvenience of having the post-bacula
tools query the catalog database for info rather than getting
it from the filenames.
> However the volume
> contains important statistic data like error / mount times, and you
> would be giving up on that if always creating new ones instead of
> recycling them.
Important statistics for tape volumes, meaningless for disk
volumes.
For now, using per-pool counters and restarting the director
each night right before the backups start seems to be a usable
if un-aesthetic work-around. I will think about your comments
and ponder if it might be worthwhile to rethink the way I am
doing backups. Thanks.
--
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the
conversation now. http://goparallel.sourceforge.net/
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Status of Python api?
> >>> [...]
> >>> 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? If is the client name you can uses ${Client}.
> > You could check all Bacula Variables via Google:
> > http://www.bacula.org/5.2.x-manuals/en/misc/misc/Variable_Expansion.html
>
> Thanks for that suggestion. I read the Variable Expansion
> chapter many times but interpreted "current number of Volumes
> in the Pool" as being a fixed number for a pool with a large
> number of pre-labeled volumes.
>
> I just tried using NumVols but the number it produced was 5177.
> I guess was wrong about the pre-labeled part but it does seem
> to be total number of volumes in the pool and not a number for
> the volumes used in the current job so far which is what I
> need.
1. Sorry for misunderstanding it. I really don't see the need of associating
volumes names with their jobs and it can be very messy when they are recycled,
since a Job can take a variable amount of volumes and Bacula already provide
that association (e.g: list jobmedia, restore job..., etc.).
2. Anyway I'm on a deadlock here: if you submit all jobs for a same pool you
can't guarantee the job will occupy only the volumes with respective name on
it, and a more secure way would be have them in different pools, where
${NumVols} would work if you are recycling them.
3. You could use variables like ${JobId} plus time (Month, Day, Hour, Minute,
Second) in order to create unique volume names in a chronological order,
similar to what you want, providing that you are always are creating new
volumes for each job. However the volume contains important statistic data like
error / mount times, and you would be giving up on that if always creating new
ones instead of recycling them.
Regards,
==
Heitor Medrado de Faria - LPIC-III | ITIL-F
02 a 13 de Março - Novo Treinamento Telepresencial Bacula:
http://www.bacula.com.br/?p=2174
61 8268-4220
Site: www.bacula.com.br | Facebook: heitor.faria | Gtalk: heitorfa...@gmail.com
===
--
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the
conversation now. http://goparallel.sourceforge.net/
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Status of Python api?
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. McGraw: you should try LabelFormat = "xxx-${NumVols}.bac"
> What is xxx? If is the client name you can uses ${Client}.
> You could check all Bacula Variables via Google:
> http://www.bacula.org/5.2.x-manuals/en/misc/misc/Variable_Expansion.html
Thanks for that suggestion. I read the Variable Expansion
chapter many times but interpreted "current number of Volumes
in the Pool" as being a fixed number for a pool with a large
number of pre-labeled volumes.
I just tried using NumVols but the number it produced was 5177.
I guess was wrong about the pre-labeled part but it does seem
to be total number of volumes in the pool and not a number for
the volumes used in the current job so far which is what I
need.
Is there anything else which might be suitable?
>> No suggestions or comments at all? I guess I have to take
>> that as meaning Bacula does not provide a way of doing this.
>> Would have been nice to know definitely though.
>
> Please avoiding posting twice and using blackmail. This is not a
> professional paid support list.
I posted first on Feb 17 and after the message did not appear
on the list posted a second time on Feb 20. Both messages
showed up on the list together a day and a half later.
I am well aware that this is not a paid support list, being
a contributor to open source projects myself. I am sorry if
you (or anyone else) saw my post as "blackmail" -- when I ask
a question on a mailing list I generally try to always post
closing message saying what I did to resolve (or not) a
problem so the thread has some closure for others with the
same problem who google it up in the future. I believe I
did that in a factual and neutral way.
Again, thanks for your attempt to help, but what I wrote
still seems true.
--
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the
conversation now. http://goparallel.sourceforge.net/
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Status of Python api?
- 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 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? If is the client name you can uses ${Client}.
You could check all Bacula Variables via Google:
http://www.bacula.org/5.2.x-manuals/en/misc/misc/Variable_Expansion.html
> No suggestions or comments at all? I guess I have to take
> that as meaning Bacula does not provide a way of doing this.
> Would have been nice to know definitely though.
Please avoiding posting twice and using blackmail. This is not a professional
paid support list.
Regards,
==
Heitor Medrado de Faria - LPIC-III | ITIL-F
02 a 13 de Março - Novo Treinamento Telepresencial Bacula:
http://www.bacula.com.br/?p=2174
61 8268-4220
Site: www.bacula.com.br | Facebook: heitor.faria | Gtalk: heitorfa...@gmail.com
===
> Thanks.
>
> --
> Dive into the World of Parallel Programming The Go Parallel Website,
> sponsored
> by Intel and developed in partnership with Slashdot Media, is your hub for
> all
> things parallel software development, from weekly thought leadership blogs to
> news, videos, case studies, tutorials and more. Take a look and join the
> conversation now. http://goparallel.sourceforge.net/
> ___
> Bacula-users mailing list
> Bacula-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bacula-users
>
--
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the
conversation now. http://goparallel.sourceforge.net/
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Status of Python api?
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? >[...] No suggestions or comments at all? I guess I have to take that as meaning Bacula does not provide a way of doing this. Would have been nice to know definitely though. Thanks. -- Dive into the World of Parallel Programming The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Status of Python api?
Thanks for the clarification. One followup question if I could, since I have to go back to using LabelFormat again... My volumes are written to disk and are sized to fit on a DVD so a backup job will often need more than one volume to complete. 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? Counters continue to increment as long as the director is running rather than restarting at 1 for each job. (Right now I am restarting the director in a cron job each night before the backup jobs start but that is a little... uggg... :-) On 02/22/2015 01:39 AM, Kern Sibbald wrote: > The Release Notes are correct. The manual has not been updated > properly. I will see to it. > > I hope to have a much better replacement in a future release. > > On 17.02.2015 23:07, S McGraw wrote: >> [...] >> Could I get a clarification on the status of [the python API]? -- Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Reports and Dashboards with Interactivity, Sharing, Native Excel Exports, App Integration & more Get technology previously reserved for billion-dollar corporations, FREE http://pubads.g.doubleclick.net/gampad/clk?id=190641631&iu=/4140/ostg.clktrk ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Status of Python api?
Hello, The Release Notes are correct. The manual has not been updated properly. I will see to it. I hope to have a much better replacement in a future release. Kern On 17.02.2015 23:07, S McGraw wrote: > Is is true that the python api is no longer supported in Bacula 7? > After upgrading from 5.x and spending 3 days trying to figure out > why my custom volume labeling python script was not working, I > noticed this in the release notes: > >The following features or directives have been removed: >[...] >- Python > > and under detailed changes (dated 24Mar14): > >- Remove FD python and examples >- Remove pythonlib from lib > > But I am not sure because in the Misc manual the Python section > is still there (and dated 31 July 2014), and in the Main manual, > the section on Automatic Volume Labeling still not only mentions > but recommends using the Python api. > > Could I get a clarification on the status of this feature? > > Thanks. > > -- > Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server > from Actuate! Instantly Supercharge Your Business Reports and Dashboards > with Interactivity, Sharing, Native Excel Exports, App Integration & more > Get technology previously reserved for billion-dollar corporations, FREE > http://pubads.g.doubleclick.net/gampad/clk?id=190641631&iu=/4140/ostg.clktrk > ___ > Bacula-users mailing list > Bacula-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bacula-users > -- Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Reports and Dashboards with Interactivity, Sharing, Native Excel Exports, App Integration & more Get technology previously reserved for billion-dollar corporations, FREE http://pubads.g.doubleclick.net/gampad/clk?id=190641631&iu=/4140/ostg.clktrk ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] Status of Python api?
Is is true that the python api is no longer supported in Bacula 7? After upgrading from 5.x and spending 3 days trying to figure out why my custom volume labeling python script was not working, I noticed this in the release notes: The following features or directives have been removed: [...] - Python and under detailed changes (dated 24Mar14): - Remove FD python and examples - Remove pythonlib from lib But I am not sure because in the Misc manual the Python section is still there (and dated 31 July 2014), and in the Main manual, the section on Automatic Volume Labeling still not only mentions but recommends using the Python api. Could I get a clarification on the status of this feature? Thanks. -- Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Reports and Dashboards with Interactivity, Sharing, Native Excel Exports, App Integration & more Get technology previously reserved for billion-dollar corporations, FREE http://pubads.g.doubleclick.net/gampad/clk?id=190641631&iu=/4140/ostg.clktrk ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] Status of Python api?
Is is true that the python api is no longer supported in Bacula 7? After upgrading from 5.x and spending 3 days trying to figure out why my custom volume labeling python script was not working, I noticed this in the release notes: The following features or directives have been removed: [...] - Python and under detailed changes (dated 24Mar14): - Remove FD python and examples - Remove pythonlib from lib But I am not sure because in the Misc manual the Python section is still there (and dated 31 July 2014), and in the Main manual, the section on Automatic Volume Labeling still not only mentions but recommends using the Python api. Could I get a clarification on the status of this feature? Thanks. -- Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Reports and Dashboards with Interactivity, Sharing, Native Excel Exports, App Integration & more Get technology previously reserved for billion-dollar corporations, FREE http://pubads.g.doubleclick.net/gampad/clk?id=190641631&iu=/4140/ostg.clktrk ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
