Re: [Bacula-users] Feature Requests

2005-04-11 Thread Knut E. Meidal
Ross Boylan wrote:
I have one mundane and one exotic feature request.
 


The exotic request is that one can munge the path of files backed up,
or at least strip off leading parts.  My motivation is that I will be
backing up using snapshots, so if I want /a/b I will actually get
/snapshot/a/b.  It would be handy if this actually appeared as a
backup of /a/b.
I see that on restore one can specify an arbitrary path as the restore
root.  The option I am interested in is the inverse to that operation.
 

The main backup system at my site is CommVault Galaxy, and it has is 
this exact feature. Very handy sometimes. It actually has 2 flavors of 
this "Preserve Source Path" function:
"Preserve x levels from the end of the source path"
"Remove x levels from the beginning of the source path"

The remove function is the one I use the most. Dumps the data exactly 
where needed with no need to mv directories etc.

I was also planning on making this feature request, but Ross beat me to it
It should probably go to the devel list also, but I'm not on that one.
Knut
---
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users


Re: [Bacula-users] Feature Requests

2005-04-11 Thread Ross Boylan
On Mon, Apr 11, 2005 at 08:41:31AM -0700, Knut E. Meidal wrote:
> Ross Boylan wrote:
> 
> >I have one mundane and one exotic feature request.
> >
> > 
> >
> 
> 
> >
> >The exotic request is that one can munge the path of files backed up,
> >or at least strip off leading parts.  My motivation is that I will be
> >backing up using snapshots, so if I want /a/b I will actually get
> >/snapshot/a/b.  It would be handy if this actually appeared as a
> >backup of /a/b.
> >
> >I see that on restore one can specify an arbitrary path as the restore
> >root.  The option I am interested in is the inverse to that operation.
> >
> >
> > 
> >
> The main backup system at my site is CommVault Galaxy, and it has is 
> this exact feature. Very handy sometimes. It actually has 2 flavors of 
> this "Preserve Source Path" function:
> "Preserve x levels from the end of the source path"
> "Remove x levels from the beginning of the source path"
> 
> The remove function is the one I use the most. Dumps the data exactly 
> where needed with no need to mv directories etc.
> 
> I was also planning on making this feature request, but Ross beat me to it
> It should probably go to the devel list also, but I'm not on that one.
> 
> Knut
> 

One of the not straightforward parts of the request is deciding
exactly where it goes.  For example, the client file director could
lie about the true path.  Or the server could know, but strip off the
extra stuff.


---
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users


Re: [Bacula-users] Feature requests?

2012-05-13 Thread Ralf Gross
Roy Sigurd Karlsbakk schrieb:
> 
> I filed a feature request on
> http://bugs.bacula.org/view.php?id=1866, only to have it closed with
> reason "no change required". Is there another preferred way to file
> feature requests than using the bug tracker? If so, can you please
> remove the "feature" level, or at least document the reason for this
> level? As for the feature request, allowing independant upgrade of
> SD and Director, I find this a rather important one in those cases
> where you have multiple SDs (I have four now, two more to come, and
> I've talked with other people having even more).


http://www.bacula.org/en/?page=feature-request

or

http://www.baculasystems.com/support


Ralf

--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users


Re: [Bacula-users] Feature requests?

2012-05-13 Thread John Drescher
> http://www.bacula.org/en/?page=feature-request
>
I do not believe feature requests from open source side are driving
development any more or at least its been quite some time since we
have had a vote on the mailing lists on feature requests would be most
important to the users for in the next version.

John

--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users


Re: [Bacula-users] Feature requests?

2012-05-13 Thread John Drescher
On Sun, May 13, 2012 at 2:14 PM, John Drescher  wrote:
>> http://www.bacula.org/en/?page=feature-request
>>
> I do not believe feature requests from open source side are driving
> development any more or at least its been quite some time since we
> have had a vote on the mailing lists on feature requests would be most
> important to the users for in the next version.
>

I see the link does talk about the change in policy.

John

--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users


Re: [Bacula-users] Feature requests

2005-11-29 Thread Kern Sibbald
On Tuesday 29 November 2005 18:44, Deim Ágoston wrote:
> Hi Kern,
>
> last week we had a displeasing exprience. When we restored a directory
> tree from the console we got the following error message:
>
> Error: block.c:304 Volume data error at 0:2482648813! Block checksum
> mismatch in block 970: calc=fbd73d8f blk=8425024b
>
> So, it means that a block in one of our disk based volumes got damaged. We
> used bextract with -p flag so we were able to get the directory tree back.
> The "bad block" was not in the directory.
>
> So, I would like to request a command available in the console to skip
> errors and continoue the restore process. Second, I would be very happy if
> there would be a parity option in the Options section when I create a
> FileSet. I know that parity bits grow the volumes but I think it would be a
> nice feature. Before I started to use bacula I used dar - dar.linux.free.fr
> - which has this option. They use the parchive - parchive.sf.net - for this
> feature. I think it would greatly improve feature set of bacula.

Try using the -p option on your SD it will do the same thing as -p on 
bextract.

For the parity bit, I think this is equivalent to striping, something that 
maybe someday Bacula will be able to do.   I'll take a look at parchive to 
see what it does ...

>
> thanks in advance,
> Ago
>
>
>
>
> ---
> This SF.net email is sponsored by: Splunk Inc. Do you grep through log
> files for problems?  Stop!  Download the new AJAX search engine that makes
> searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
> http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
> ___
> Bacula-users mailing list
> Bacula-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bacula-users

-- 
Best regards,

Kern

  (">
  /\
  V_V


---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37&alloc_id865&op=click
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users


Re: [Bacula-users] Feature requests

2005-11-30 Thread Deim Ágoston

Kern Sibbald wrote:


So, I would like to request a command available in the console to skip
errors and continoue the restore process. Second, I would be very happy if
there would be a parity option in the Options section when I create a
FileSet. I know that parity bits grow the volumes but I think it would be a
nice feature. Before I started to use bacula I used dar - dar.linux.free.fr
- which has this option. They use the parchive - parchive.sf.net - for this
feature. I think it would greatly improve feature set of bacula.
   



Try using the -p option on your SD it will do the same thing as -p on 
bextract.


 

ok, thanks, I overlooked this flag. Or to be more precise I didn't think 
about it to allow it globally. Usually I would like to use bacula-sd 
without -p flag and use it if I need. But I accept the current solution, 
so if I get this error I will restart bacula-sd with flag -p turned on.


For the parity bit, I think this is equivalent to striping, something that 
maybe someday Bacula will be able to do.   I'll take a look at parchive to 
see what it does ...
 


ok, thanks. And bacula is a great piece of software. Thanks.

bye,
Ago


---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users


Re: [Bacula-users] Feature Requests and Bacula projects

2005-11-24 Thread Alan Brown


Kern,

not in the list, but wanted by me (and several other people):

Daily summarisation of jobs run.

I have management grumbling loudly about receiving perhaps 80 messages 
from Bacula per day when all they want to see is "xyz jobs run, xy 
sucessful, z failed on whatever reason"


Was someone working on this?

AB



---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users


Re: [Bacula-users] Feature Requests and Bacula projects

2005-11-24 Thread Kern Sibbald
On Thursday 24 November 2005 18:05, Alan Brown wrote:
> Kern,
>
> not in the list, but wanted by me (and several other people):
>
> Daily summarisation of jobs run.
>
> I have management grumbling loudly about receiving perhaps 80 messages
> from Bacula per day when all they want to see is "xyz jobs run, xy
> sucessful, z failed on whatever reason"
>
> Was someone working on this?

This has been implemented by a user:  please see 
examples/bacula_mail_summary.sh

-- 
Best regards,

Kern

  (">
  /\
  V_V


---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users


Re: [Bacula-users] feature requests (spool file naming, "stat clients" output)

2006-08-23 Thread Kern Sibbald
On Tuesday 22 August 2006 23:24, [EMAIL PROTECTED] wrote:
> 
> Item 1:   include JobID in spool file name
>   Origin: Mark Bergman <[EMAIL PROTECTED]>
>   Date:  Tue Aug 22 17:13:39 EDT 2006
>   Status:
> 
>   What:   Change the name of the spool file to include the JobID
> 
>   Why:JobIDs are the common key used to refer to jobs, yet the 
>   spoolfile name doesn't include that information. The date/time
>   stamp is useful (and should be retained).

JobIds are not unique.  The full Job name is unique, and that is what is used.  
I don't see any advantage to adding the JobId or changing it, or at least you 
have not explained it enough for me.

> 
> 
> 
> Item 2:   include timestamp of job launch in "stat clients" output
>   Origin: Mark Bergman <[EMAIL PROTECTED]>
>   Date:  Tue Aug 22 17:13:39 EDT 2006
>   Status:
> 
>   What:   The "stat clients" command doesn't include any detail on when
>   the active backup jobs were launched.
> 
>   Why:   Including the timestamp would make it much easier to decide whether
>   a job is running properly. 
> 
>   Notes: It may be helpful to have the output from "stat clients" formatted 
>   more like that from "stat dir" (and other commands), in a column
>   format. The per-client information that's currently shown (level,
>   client name, JobId, Volume, pool, device, Files, etc.) is good, but
>   somewhat hard to parse (both programmatically and visually), 
>   particularly when there are many active clients.

Please present an "explicit" example of what you want, and try to ensure that 
it is not wrapped by the emailer (possibly via an attachment).

> 
> 
> 
> Mark Bergman  [EMAIL PROTECTED]
> System Administrator
> Section of Biomedical Image Analysis 215-662-7310
> Department of Radiology,   University of Pennsylvania
> 
> 
http://pgpkeys.pca.dfn.de:11371/pks/lookup?search=mark.bergman%40.uphs.upenn.edu
> 
> 
> 
> 
> The information contained in this e-mail message is intended only for the 
personal and confidential use of the recipient(s) named above. If the reader 
of this message is not the intended recipient or an agent responsible for 
delivering it to the intended recipient, you are hereby notified that you 
have received this document in error and that any review, dissemination, 
distribution, or copying of this message is strictly prohibited. If you have 
received this communication in error, please notify us immediately by e-mail, 
and delete the original message.
> 
> -
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job 
easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
> ___
> Bacula-users mailing list
> Bacula-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bacula-users
> 

-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users


Re: [Bacula-users] Feature Requests - FileSet Variable & Diff, Inc, Full Run Scripts

2015-05-16 Thread Bill Arlofski
Resend. Originally sent from wrong email address.

On 05/16/2015 08:56 AM, Heitor Faria wrote:
> Dear Bacula Developers / Users,
> 
> I suggested to feature requests today for your evaluation:
> 
> 1. Bacula FileSet Variable
> 
> Implement Bacula FileSet Variable to improve scripting capabilities and maybe
> do a show FileSet during backups, improving log information.

Hi Heitor!  :)

Hmmm, for debugging purposes this might be helpful at times.   But I wonder
what would be in the FileSet variable?

Option 1: Just it's name like:  "LinuxSystemsFileSet"

Having just the name in the job's log is helpful, but a job can be run with a
FileSet, and then someone can edit the FileSet's resource later... Then if you
go back for debugging, you might be comparing a job's outcome (e.g.: the files
backed up) against a fileset name whose current contents can be entirely
different.

Or

Option 2: The Name of the FileSet like above and the actual contents of the
FileSet resource as passed to the FD when the job is started.

If the FileSet name and full FileSet resource (as passed to the FD at job
start time) are logged for every job, you know exactly what the FD was told to
backup, but the job logs may become unnecessarily long, or more of a chore to
read.

Personally, I kind of like the idea though because my backup logs are handled
by my helpdesk software, so I only have to read a log occasionally when
notified of something out of the ordinary. :)


Quick workaround:  Use the bconsole "show job=JobName" as a Run Before Run
Script command. This tells you everything about the job.

However, this is not a great solution because the show job=JobName  command
shows the "configured" job information, not the information handed to the FD
at the start of the job. If the FileSet (or other) is manually modified just
before the job is submitted, you would not know it.


> 2. Different Run Scripts Per Backup level
> 
> Add the keyword full, diff, inc etc. to the Run Script Resource, so the
> administrator can set different scripts per backup job Level.

You can already (manually) implement this feature in your Run Scripts
themselves.   Bacula has the %l variable to indicate the Level. If you use a
shell script or other script as a Run Script command, you can just pass %l and
then test for it in the shell scrip and act on it accordingly..

[snip]
Job {
...
   Run Script {
 RunsWhen = before
 RunsOnClient = no
 Command = "/path/to/script.sh %l"
   }
}
[snip]


/path/to/script.sh:

[snip]
#!/bin/bash
level="$1"
...
case ${level} in

Full )
   Some Full stuff here ;;

Incremental )
   Some Incremental stuff here ;;


Differential )
   Some Differential stuff here ;;

VFull )
   Some Virtual Full stuff here ;;

* )
Some Catch-all stuff here ;;

esac
...
[snip]


Bill



-- 
Bill Arlofski
Reverse Polarity, LLC
http://www.revpol.com/
-- Not responsible for anything below this line --

--
One dashboard for servers and applications across Physical-Virtual-Cloud 
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users


Re: [Bacula-users] Feature Requests - FileSet Variable & Diff, Inc, Full Run Scripts

2015-05-16 Thread Heitor Faria
*it's nice TO have

=== 
Heitor Medrado de Faria - LPIC-III | ITIL-F | Bacula Systems Certified 
Administrator II 
15 a 26 de junho: 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: "Bill Arlofski" 
> Cc: bacula-users@lists.sourceforge.net
> Enviadas: Sábado, 16 de maio de 2015 13:43:20
> Assunto: Re: [Bacula-users] Feature Requests - FileSet Variable & Diff, Inc, 
> Full Run Scripts

> Hey Bill,
> 
> What's up?
> 
>> Hmmm, for debugging purposes this might be helpful at times.   But I wonder
>> what would be in the FileSet variable?
>> 
>> Option 1: Just it's name like:  "LinuxSystemsFileSet"
> 
> Option 1.
> 
>> Having just the name in the job's log is helpful, but a job can be run with a
>> FileSet, and then someone can edit the FileSet's resource later... Then if 
>> you
>> go back for debugging, you might be comparing a job's outcome (e.g.: the 
>> files
>> backed up) against a fileset name whose current contents can be entirely
>> different.
> 
> That's exactly the beauty of having a show fileset every backup job. This is 
> the
> problem I'm trying to solve.
> Not for me, but Bacula newbies. It's easy to forget to set the correct FileSet
> when creating a new Job.
> 
>> If the FileSet name and full FileSet resource (as passed to the FD at job
>> start time) are logged for every job, you know exactly what the FD was told 
>> to
>> backup, but the job logs may become unnecessarily long, or more of a chore to
>> read.
> 
> Yes, but I think it may be important. FileSet can change along the time. Even
> for auditing purposes it's nice two have that information, optionally of
> course. I think it's a crucial information for support.
> I don't think it's too much information. Typical show fileset output brings
> what, 12 lines?
> 
>> Personally, I kind of like the idea though because my backup logs are handled
>> by my helpdesk software, so I only have to read a log occasionally when
>> notified of something out of the ordinary. :)
> 
> It would be optional. You could make a script to show fileset=var every job, 
> or
> not.
> 
>> Quick workaround:  Use the bconsole "show job=JobName" as a Run Before Run
>> Script command. This tells you everything about the job.
> 
> Yes, but this way the output would be huge. =)
> 
>>> 2. Different Run Scripts Per Backup level
>>> 
>>> Add the keyword full, diff, inc etc. to the Run Script Resource, so the
>>> administrator can set different scripts per backup job Level.
>> 
>> You can already (manually) implement this feature in your Run Scripts
>> themselves.   Bacula has the %l variable to indicate the Level. If you use a
>> shell script or other script as a Run Script command, you can just pass %l 
>> and
>> then test for it in the shell scrip and act on it accordingly..
> 
> Yes, it would work nice. I just think it would be easier for people that does
> not know scripting to use it.

--
One dashboard for servers and applications across Physical-Virtual-Cloud 
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users


Re: [Bacula-users] Feature Requests - FileSet Variable & Diff, Inc, Full Run Scripts

2015-05-16 Thread Heitor Faria
Hey Bill,

What's up?

> Hmmm, for debugging purposes this might be helpful at times.   But I wonder
> what would be in the FileSet variable?
> 
> Option 1: Just it's name like:  "LinuxSystemsFileSet"

Option 1.

> Having just the name in the job's log is helpful, but a job can be run with a
> FileSet, and then someone can edit the FileSet's resource later... Then if you
> go back for debugging, you might be comparing a job's outcome (e.g.: the files
> backed up) against a fileset name whose current contents can be entirely
> different.

That's exactly the beauty of having a show fileset every backup job. This is 
the problem I'm trying to solve.
Not for me, but Bacula newbies. It's easy to forget to set the correct FileSet 
when creating a new Job. 

> If the FileSet name and full FileSet resource (as passed to the FD at job
> start time) are logged for every job, you know exactly what the FD was told to
> backup, but the job logs may become unnecessarily long, or more of a chore to
> read.

Yes, but I think it may be important. FileSet can change along the time. Even 
for auditing purposes it's nice two have that information, optionally of 
course. I think it's a crucial information for support. 
I don't think it's too much information. Typical show fileset output brings 
what, 12 lines?
 
> Personally, I kind of like the idea though because my backup logs are handled
> by my helpdesk software, so I only have to read a log occasionally when
> notified of something out of the ordinary. :)

It would be optional. You could make a script to show fileset=var every job, or 
not. 

> Quick workaround:  Use the bconsole "show job=JobName" as a Run Before Run
> Script command. This tells you everything about the job.

Yes, but this way the output would be huge. =)

>> 2. Different Run Scripts Per Backup level
>> 
>> Add the keyword full, diff, inc etc. to the Run Script Resource, so the
>> administrator can set different scripts per backup job Level.
> 
> You can already (manually) implement this feature in your Run Scripts
> themselves.   Bacula has the %l variable to indicate the Level. If you use a
> shell script or other script as a Run Script command, you can just pass %l and
> then test for it in the shell scrip and act on it accordingly..

Yes, it would work nice. I just think it would be easier for people that does 
not know scripting to use it.

--
One dashboard for servers and applications across Physical-Virtual-Cloud 
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users