date:20151001

Re: [Bacula-users] [Bacula-devel] FreeBSD 10.2 & Bacula 7.2 compile errors

2015-10-01 Thread Kern Sibbald


Hello Dan,

That is good news ... thanks.

Best regards,
Kern

On 15-10-01 05:10 AM, Dan Langille wrote:

On Sep 21, 2015, at 10:16 PM, Dan Langille  wrote:

I only just got back to this today, and I saw Kern's post about Eric's work.  I 
am happy to report: no more compile errors.

re: 
http://www.bacula.org/git/cgit.cgi/bacula/commit/?id=26db75ea69d9f097c5de207d180fd58909c4fbec

However, regression tests are not starting.  That will be another post.

Regression testing on FreeBSD is successful: 
http://regress.bacula.org/index.php?project=bacula=2015-09-30

The problem I mentioned above was because I was not on the correct branch.

I'll start work on upgrading the Bacula port next week.

—
Dan Langille
http://langille.org/







--


___
Bacula-devel mailing list
bacula-de...@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-devel


--
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Question about bacula and tls

2015-10-01 Thread Ana Emília M . Arruda

Hello Egoitz,

Is this thread clear? If you have your own dedicated CA, then take care of
her :). This way and having level 4 bacula TLS configured as Josh
explained, then your communication will be "secure" (never say that we are
100% secure...).

Thank you very much Josh.

Best regards,
Ana



On Wed, Sep 30, 2015 at 11:22 AM, Josh Fisher  wrote:

>
>
> On 9/30/2015 3:18 AM, Egoitz Aurrekoetxea wrote:
>
> Hi Ana!!
>
> Really thanks for answering my doubts :)
>
> I do answer in black below...
>
> El 30/9/2015, a las 6:24, Ana Emília M. Arruda 
> escribió:
>
>
> On Mon, Sep 28, 2015 at 6:20 PM, Egoitz Aurrekoetxea <
> ego...@ramattack.net> wrote:
>
>> Good night,
>>
>
>
> Yes, you can have certificates from different CA in each side, you just
> need to inform the CA correctly for peer verification. How did you
> generated your certificates? Do you have a CA and signed them properly?
>
>
> I have an own dedicated CA for Bacula systems. One of the things I was
> trying to get with TLS is the fact that like both sides know the CA public
> key, they to be able to check if the information received in each side
> because of the other side’s sent data in unaltered due to a possible MITM
> issue. I mean, could I with verify peer ensure that if someone tries to do
> a MITM won’t succeed because both sides know the CA allowed to
> be used in signed certs?. So an attacker doing a signed certificate with a
> new CA (CA of the attacker for signing the attacking used certificate)
> won’t be able then to inject content in dir and fd dialogue or fd and sd
> dialogue?.
> Or at least if it does, do each side, the sd, fd or the dir, interrupt the
> connection and stop the job notifying?.
>
>
> Think of it as 5 different security levels.
>
> Level 0:
># Data is transmitted as plain text
> TLS Enable = no
>
> Level 1:
> # This level allows opportunistic encryption if the peer chooses, or
> the peer can communicate in plain text.
> TLS Enable = yes
> TLS Require = no
> TLS Verify Peer = no
> TLS Certificate = /etc/bacula/cert.pem
> TLS Key = /etc/bacula/key.pem
> TLS CA Certificate File = /path/to/system/cafile
>
> Level 2:
> # This level requires encryption of data. Any certificate will do,
> even a self-signed certificate.
> TLS Enable = yes
> TLS Require = yes
> TLS Verify Peer = no
> TLS Certificate = /etc/bacula/cert.pem
> TLS Key = /etc/bacula/key.pem
> TLS CA Certificate File = /path/to/system/cafile
>
> Level 3:
> # This level requires encryption and that the certificate presented by
> the peer be signed by a trusted CA
> TLS Enable = yes
> TLS Require = yes
> TLS Verify Peer = yes
> TLS Certificate = /etc/bacula/cert.pem
> TLS Key = /etc/bacula/key.pem
> TLS CA Certificate File = /path/to/system/cafile
>
> Level 4:
> # This level requires encryption and that the certificate presented by
> the peer be signed by a trusted CA
> # and that the certificate have a specific CN
> TLS Enable = yes
> TLS Require = yes
> TLS Verify Peer = yes
> TLS Allowed CN = "some.client.common.name"
> TLS Certificate = /etc/bacula/cert.pem
> TLS Key = /etc/bacula/key.pem
> TLS CA Certificate File = /path/to/system/cafile
>
>
> As for a MiTM attack, keep in mind that an active attack is harder than a
> passive attack. Even opportunistic encryption with self-signed certs
> protects against passive snooping. Protecting against an active MiTM attack
> requires authentication. Heartbleed bug aside, level 3 means that the
> attacker must somehow acquire certificates signed by a CA in the TLS CA
> Certificate Files of both client and server. Level 4 means that she must
> steal particular certificates. So level 4 makes a MiTM attack very
> difficult.
>
> That said, the real danger is a valid certificate that is stolen or
> compromised. The CA can revoke a certificate, but this does no good
> because, as far as I can tell, Bacula does not check CRLs! Level 3 is not
> very useful without CRL checks. Therefore, always use level 4, at least
> until Bacula supports CRL checks, since then a  can be avoided by removing
> its CN from the TLS Allowed CN list. If you are not wrorried about MiTM
> attacks and just want to prevent snooping, then level 2 will suffice.
>
>
>
>
>
> --
>
> ___
> Bacula-users mailing list
> Bacula-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bacula-users
>
>
--
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] is 7.2 ready for prime time?

2015-10-01 Thread Michael Schwager

Innobackupex is excellent- we use it- but it's not as trivial as a tar copy
of the mysql directory (shut the database down first). For example, you may
end up using the database username/password on the command line in your
scripts (which you should probably avoid). Also, according to the man page,
"After  creating  a  backup,  the  data  is  not  ready to be restored."
...Ehm, in a word: YIKES! RTFM for sure! At least they tell you what you
need to do, and it's not hard, but if you miss it...

Anyway, here's a bash example of how we back up our production database.
Details such as defining LOG_DIR and BACKUP_DIR left as an exercise for the
reader:

cleanup () {
status=$?
rm -f $TMPFILE
exit $status
}

trap cleanup EXIT SIGQUIT SIGHUP SIGINT SIGTERM

TMPFILE=$(mktemp /tmp/dbbkpX)

suffix=$(date +%w)
cp /etc/my.cnf $TMPFILE
cat /var/lib/mysql/defaults.cnf >> $TMPFILE

mkdir -p $LOG_DIR $BACKUP_DIR

innobackupex --defaults-file $TMPFILE $FULL_BACKUP_DIR > $LOG_DIR/$suffix
2>&1
innobackupex --defaults-file $TMPFILE --apply-log $FULL_BACKUP_DIR >>
$LOG_DIR/$suffix 2>&1




*- Mike Schwager*

*  Linux Network Engineer, Mocho Trading LLC*
*  312-646-4783 Phone312-637-0011 Cell312-957-9804 Fax*


On Mon, Sep 28, 2015 at 2:49 AM, Uwe Schuerkamp 
wrote:

> On Fri, Sep 25, 2015 at 09:01:29AM -0700, Stephen Thompson wrote:
> >
> >
> >
> > I run daily backups of my database and had finished my monthly full run
> > for September, so I was technically covered.  However I was not looking
> > forward to restoring a 900+Gb mysql database from a text dump which on
> > my system would take days, if not an entire week.  The last time I had
> > to restore database from backup it was 4 or so years ago and my database
> > was only 300-400Gb back then.
> >
> > Stephen
> >
> >
>
> One word: innobackupex. You'll be up running in a few minutes again as
> opposed to a week when using a text file created by mysqldump (which,
> much like MyISAM tables, should be taken round the back and taken out
> of its misery once and for all ;))
>
> All the best,
>
> Uwe
>
>
>
>
>
>
>
>
>
> --
> ___
> Bacula-users mailing list
> Bacula-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bacula-users
>

-- 
This message is for the named person(s) use only. It may contain 
confidential proprietary or legally privileged information. No 
confidentiality or privilege is waived or lost by any mistransmission. If 
you receive this message in error, please immediately delete it and all 
copies of it from your system, destroy any hard copies of it and notify the 
sender. You must not, directly or indirectly use, disclose, distribute, 
print, or copy any part of this message if you are not the intended 
recipient. Mocho Trading LLC reserves the right to monitor all e-mail 
communications through its networks. Any views expressed in this message 
are those of the individual sender, except where the message states 
otherwise and the sender is authorized to state them to be the views of any 
such entity.
--
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] git status - for regression testing

2015-10-01 Thread Phil Stracchino

On 10/01/15 10:27, Ana Emília M. Arruda wrote:
> The git clone command for bacula repository:
> 
> git clone http://git.bacula.org/bacula localfolder
> 
> If you want to clone a specific branch (the clone without specifying the
> branch will be for the origin/Branch-7.0):
> 
> git clone http://git.bacula.org/bacula --branch Branch-7.2 localfolder
> 
> Best regards,
> Ana


Thanks, Ana.

-- 
  Phil Stracchino
  Babylon Communications
  ph...@caerllewys.net
  p...@co.ordinate.org
  Landline: 603.293.8485

--
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] git status - for regression testing

2015-10-01 Thread Dan Langille


> On Oct 1, 2015, at 3:47 PM, Kern Sibbald  wrote:
> 
> Hello Dan,
> 
> The tests will not work for your nodes that are reporting a difference in 
> commits.  This difference is probably because at one point in the past I 
> rewrote the git history slightly to remove some unwanted commits.
> 
> There are two ways to correct the problem on those nodes:
> 
> 1. Rewind the repo and repull it with the following commands:
> 
>cd 
>git checkout Branch-xxx
>git reset --hard 1ef84681d13d0c35
>git pull
> 
> This should work on any branch ...
> 
> 2. Delete the repo and reclone it.
> 
>  I have tested #1, but my Internet connection is via satellite and is so 
> terribly slow that I cannot lookup the exact command for cloning the database.
> 
> Best regards,
> Kern
> 
> 
> On 15-10-01 05:28 AM, Dan Langille wrote:
>> I am running regression testing on both Bacula 7 and Bacula 5. Both are 
>> still in heavy use so regression testing is still important.
>> 
>> My Bacula 7 tree seems ok, and all nodes report:
>> 
>> $ git status
>> On branch Branch-7.2
>> Your branch is up-to-date with 'origin/Branch-7.2'.
>> nothing to commit, working directory clean
>> 
>> 
>> My 5.x source trees are not consistent.  Most nodes report:
>> 
>> $ git status
>> On branch Branch-5.2
>> Your branch is ahead of 'origin/Branch-5.2' by 1354 commits.
>>   (use "git push" to publish your local commits)
>> nothing to commit, working directory clean
>> 
>> 
>> A few nodes report
>> 
>> $ git status
>> On branch Branch-5.2
>> Your branch is up-to-date with 'origin/Branch-5.2'.
>> nothing to commit, working directory clean


All nodes now report:

$ git status
On branch Branch-5.2
Your branch is up-to-date with 'origin/Branch-5.2'.
nothing to commit, working directory clean


Thank you.

—
Dan Langille
http://langille .org/







signature.asc
Description: Message signed with OpenPGP using GPGMail
--
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

[Bacula-users] Which JobID did my Verify verify?

2015-10-01 Thread Michael Schwager

Hi,
I have a job that, once complete, involves removing a number of backed up
files. How do I make sure the files are complete and on tape?

...With a Verify job, of course. Ok, so let's say my job name is "Log" and
my verify job is "VerifyLog", with a Job entry in the bacula-dir file of:
VerifyJob = "Log". Furthermore, my backup job's schedule is
"SaturdayEvening" and its priority is "40". The Verify job shares the same
schedule but its priority is 41.

So it should verify the very last Log job, and I should be happy.

What I want, though, is to *guarantee* to my manager that I verified the
job that I expected to verify.

I notice that I can do an "llist jobid=" on a backup job and get some
nice details, but this function will not tell me about Verify jobs. I also
notice that the log file tells me that the Verify job knows which job it's
verifying against, eg:

27-Sep 04:34 bacula-dir JobId 1521: Verifying against JobId=1520
Job=Captures.2015-09-27_04.00.00_42

I could grep the logs, but is there a bconsole function that I have yet to
find?

Thanks.


*- Mike Schwager*

*  Linux Network Engineer, Mocho Trading LLC*
*  312-646-4783 Phone312-637-0011 Cell312-957-9804 Fax*

-- 
This message is for the named person(s) use only. It may contain 
confidential proprietary or legally privileged information. No 
confidentiality or privilege is waived or lost by any mistransmission. If 
you receive this message in error, please immediately delete it and all 
copies of it from your system, destroy any hard copies of it and notify the 
sender. You must not, directly or indirectly use, disclose, distribute, 
print, or copy any part of this message if you are not the intended 
recipient. Mocho Trading LLC reserves the right to monitor all e-mail 
communications through its networks. Any views expressed in this message 
are those of the individual sender, except where the message states 
otherwise and the sender is authorized to state them to be the views of any 
such entity.
--
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] git status - for regression testing

2015-10-01 Thread Ana Emília M . Arruda

Hello Kern and Dan,

The git clone command for bacula repository:

git clone http://git.bacula.org/bacula localfolder

If you want to clone a specific branch (the clone without specifying the
branch will be for the origin/Branch-7.0):

git clone http://git.bacula.org/bacula --branch Branch-7.2 localfolder

Best regards,
Ana

On Thu, Oct 1, 2015 at 10:47 AM, Kern Sibbald  wrote:

> Hello Dan,
>
> The tests will not work for your nodes that are reporting a difference in
> commits.  This difference is probably because at one point in the past I
> rewrote the git history slightly to remove some unwanted commits.
>
> There are two ways to correct the problem on those nodes:
>
> 1. Rewind the repo and repull it with the following commands:
>
>cd 
>git checkout Branch-xxx
>git reset --hard 1ef84681d13d0c35
>git pull
>
> This should work on any branch ...
>
> 2. Delete the repo and reclone it.
>
>  I have tested #1, but my Internet connection is via satellite and is so
> terribly slow that I cannot lookup the exact command for cloning the
> database.
>
> Best regards,
> Kern
>
>
>
> On 15-10-01 05:28 AM, Dan Langille wrote:
>
> I am running regression testing on both Bacula 7 and Bacula 5. Both are still 
> in heavy use so regression testing is still important.
>
> My Bacula 7 tree seems ok, and all nodes report:
>
> $ git status
> On branch Branch-7.2
> Your branch is up-to-date with 'origin/Branch-7.2'.
> nothing to commit, working directory clean
>
>
> My 5.x source trees are not consistent.  Most nodes report:
>
> $ git status
> On branch Branch-5.2
> Your branch is ahead of 'origin/Branch-5.2' by 1354 commits.
>   (use "git push" to publish your local commits)
> nothing to commit, working directory clean
>
>
> A few nodes report
>
> $ git status
> On branch Branch-5.2
> Your branch is up-to-date with 'origin/Branch-5.2'.
> nothing to commit, working directory clean
>
> Should I change something to ensure consistency across regression tests?
>
> —
> Dan Langillehttp://langille.org/
>
>
>
>
>
>
> --
>
>
>
> ___
> Bacula-users mailing 
> listBacula-users@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/bacula-users
>
>
>
>
> --
>
> ___
> Bacula-users mailing list
> Bacula-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bacula-users
>
>
--
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] is 7.2 ready for prime time?

2015-10-01 Thread Michael Schwager

On Fri, Sep 25, 2015 at 10:50 AM, Raymond Burns Jr. 
wrote:

> I didn't run a backup of the database because of all the great responses
> from people.


Oh dear Lord man! If running mysql, shut the database down and tar up the
/var/lib/mysql directory (or whatever you have in /etc/my.cnf). It's so
trivial, yet such a tremendous heart attack prevention technique!


*- Mike Schwager*

*  Linux Network Engineer, Mocho Trading LLC*
*  312-646-4783 Phone312-637-0011 Cell312-957-9804 Fax*

-- 
This message is for the named person(s) use only. It may contain 
confidential proprietary or legally privileged information. No 
confidentiality or privilege is waived or lost by any mistransmission. If 
you receive this message in error, please immediately delete it and all 
copies of it from your system, destroy any hard copies of it and notify the 
sender. You must not, directly or indirectly use, disclose, distribute, 
print, or copy any part of this message if you are not the intended 
recipient. Mocho Trading LLC reserves the right to monitor all e-mail 
communications through its networks. Any views expressed in this message 
are those of the individual sender, except where the message states 
otherwise and the sender is authorized to state them to be the views of any 
such entity.
--
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] git status - for regression testing

2015-10-01 Thread Kern Sibbald


Hello Dan,

The tests will not work for your nodes that are reporting a difference 
in commits.  This difference is probably because at one point in the 
past I rewrote the git history slightly to remove some unwanted commits.


There are two ways to correct the problem on those nodes:

1. Rewind the repo and repull it with the following commands:

   cd 
   git checkout Branch-xxx
   git reset --hard 1ef84681d13d0c35
   git pull

This should work on any branch ...

2. Delete the repo and reclone it.

 I have tested #1, but my Internet connection is via satellite and is 
so terribly slow that I cannot lookup the exact command for cloning the 
database.


Best regards,
Kern


On 15-10-01 05:28 AM, Dan Langille wrote:

I am running regression testing on both Bacula 7 and Bacula 5. Both are still 
in heavy use so regression testing is still important.

My Bacula 7 tree seems ok, and all nodes report:

$ git status
On branch Branch-7.2
Your branch is up-to-date with 'origin/Branch-7.2'.
nothing to commit, working directory clean


My 5.x source trees are not consistent.  Most nodes report:

$ git status
On branch Branch-5.2
Your branch is ahead of 'origin/Branch-5.2' by 1354 commits.
   (use "git push" to publish your local commits)
nothing to commit, working directory clean


A few nodes report

$ git status
On branch Branch-5.2
Your branch is up-to-date with 'origin/Branch-5.2'.
nothing to commit, working directory clean

Should I change something to ensure consistency across regression tests?

—
Dan Langille
http://langille.org/







--


___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users


--
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Bacula Verify Jobs

2015-10-01 Thread Michael Schwager

Here is an example where the Verify job uses the same schedule but
different Messages than standard. Pool, Storage, and Schedule entries are
up to you and have not been included; they are not remarkable. The
important thing to note is that the Verify will perform a verify of the
last backup of the job specified in the "VerifyJob" line.  Let me know if
you have any questions.

# Captures
Job {
  Name = "Captures"
  Schedule = "SaturdayEvening"
  Type = Backup
  Client = captures
  Level = Full
  Storage = LTO-3
  FileSet = "Captures"
  Messages = Standard
  Pool = Captures
  Write Bootstrap = "/var/spool/bacula/bootstrap/%c-%n-%i.bsr"
  Priority = 40   # Low priority; this job can take a while to get done.
  ClientRunBeforeJob = "/usr/local/bin/captures_stage"
}

# Verify
# The verifies run at a lower priority compared to the backup job.
Job {
  Name = "CapturesVerify"
  VerifyJob = "Captures"
  Schedule = "SaturdayEvening"
  Type = Verify
  Client = captures
  Level = VolumeToCatalog
  Storage = LTO-3
  Accurate = yes
  FileSet = "Captures"
  Messages = "Verify_Captures"
  Pool = Captures
  Write Bootstrap = "/var/spool/bacula/bootstrap/%c-%n-%i.bsr"
  Priority = 41   # Low priority; this job can take a while to get done.
  ClientRunAfterJob = "/usr/local/bin/captures_post_verify %c-%n-%i"
}

#... FileSet
..
FileSet {
  Name = "Captures"
  Include {
File = /mnt/captures/staging
Options {
  signature = MD5
  noatime = yes
  xattrsupport = yes
  One FS = yes
}
  }
}

# The Client name "captures" allows us to move this job from host to host.
Client {
  Name = captures
  Address = hostname.example.com
  FDPort = 9102
  Catalog = MyCatalog
  Password = "topseekrit" # password for FileDaemon
  File Retention = 2 months
  Job Retention = 2 months
  AutoPrune = yes # Prune expired Jobs/Files
}

# Message delivery for verify messages.
Messages {
  Name = Verify_Captures
  mailcommand = "/usr/local/bin/my_smtp -h mailhub -f \"\(Bacula\) \<
bac...@example.com\>\" -s \"Bacula: %t %e of %c %l\" %r"
  operatorcommand = "/usr/local/bin/my_smtp -h mailhub -f \"\(Bacula\) \<
bac...@example.com\>\" -s \"Bacula: Intervention needed for %j\" %r"
  mail = i...@example.com = all, !skipped
  operator = i...@example.com = mount
  append = "/var/log/bacula/verify.log" = all, !skipped
  catalog = all, !skipped, !saved
}

*- Mike Schwager*

*  Linux Network Engineer, Mocho Trading LLC*
*  312-646-4783 Phone312-637-0011 Cell312-957-9804 Fax*

On Thu, Sep 24, 2015 at 6:54 AM, Wanderlei Huttel  wrote:

> Bacula manual is not so clear about Verify Jobs.
>
> What is the best practice to implement verify jobs for any backup job ?
>
> Can somebody show some example?
>
>

-- 
This message is for the named person(s) use only. It may contain 
confidential proprietary or legally privileged information. No 
confidentiality or privilege is waived or lost by any mistransmission. If 
you receive this message in error, please immediately delete it and all 
copies of it from your system, destroy any hard copies of it and notify the 
sender. You must not, directly or indirectly use, disclose, distribute, 
print, or copy any part of this message if you are not the intended 
recipient. Mocho Trading LLC reserves the right to monitor all e-mail 
communications through its networks. Any views expressed in this message 
are those of the individual sender, except where the message states 
otherwise and the sender is authorized to state them to be the views of any 
such entity.
--
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] getting a full system backup

2015-10-01 Thread Michael Schwager

On Sun, Sep 27, 2015 at 7:07 PM, Thing  wrote:

> I have rebooted the bacula server but when I do a backup it will not pick
> up the "/" still only showing usr/ in the restore window.


When you go into bconsole, do a "list jobs". Choose the latest job for
your backup. Now, do a list files jobid= where  is the JobId of
that job.

How does it look?


*- Mike Schwager*

*  Linux Network Engineer, Mocho Trading LLC*
*  312-646-4783 Phone312-637-0011 Cell312-957-9804 Fax*

-- 
This message is for the named person(s) use only. It may contain 
confidential proprietary or legally privileged information. No 
confidentiality or privilege is waived or lost by any mistransmission. If 
you receive this message in error, please immediately delete it and all 
copies of it from your system, destroy any hard copies of it and notify the 
sender. You must not, directly or indirectly use, disclose, distribute, 
print, or copy any part of this message if you are not the intended 
recipient. Mocho Trading LLC reserves the right to monitor all e-mail 
communications through its networks. Any views expressed in this message 
are those of the individual sender, except where the message states 
otherwise and the sender is authorized to state them to be the views of any 
such entity.
--
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] [Bacula-devel] volume name / label format bug with 7.0.5 after failed job

2015-10-01 Thread John Drescher

> Yes, I know this, but AFAIK this does not apply in a disaster recovery
> situation where you have to scan volumes with bscan.
> In this situation I figure it would be very useful to find the last
> backups of the catalog and the bacula server to feed them to bscan.
> With large volumes bscan will sit there for a long time, scanning all
> volumes.
>

Put the catalog backup (and bacula configs) in its own pool so its
easy to find. Then restore the catalog (and configs) with bscan and
then you should not need to bscan individual volumes.

John

--
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] ERR message

2015-10-01 Thread Michael Schwager

On Sun, Sep 27, 2015 at 7:09 PM, Thing  wrote:

> bconsole: bsock.c:223 Socket open error. proto=10 port=9101. ERR=Address
> family not supported by protocol


What is in your /etc/bacula/bconsole.conf file?

What is the "Director" entry in your /etc/bacula/bacula-dir.conf file?




*- Mike Schwager*

*  Linux Network Engineer, Mocho Trading LLC*
*  312-646-4783 Phone312-637-0011 Cell312-957-9804 Fax*

-- 
This message is for the named person(s) use only. It may contain 
confidential proprietary or legally privileged information. No 
confidentiality or privilege is waived or lost by any mistransmission. If 
you receive this message in error, please immediately delete it and all 
copies of it from your system, destroy any hard copies of it and notify the 
sender. You must not, directly or indirectly use, disclose, distribute, 
print, or copy any part of this message if you are not the intended 
recipient. Mocho Trading LLC reserves the right to monitor all e-mail 
communications through its networks. Any views expressed in this message 
are those of the individual sender, except where the message states 
otherwise and the sender is authorized to state them to be the views of any 
such entity.
--
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

[Bacula-users] git status - for regression testing

2015-10-01 Thread Dan Langille

I am running regression testing on both Bacula 7 and Bacula 5. Both are still 
in heavy use so regression testing is still important.

My Bacula 7 tree seems ok, and all nodes report:

$ git status
On branch Branch-7.2
Your branch is up-to-date with 'origin/Branch-7.2'.
nothing to commit, working directory clean


My 5.x source trees are not consistent.  Most nodes report:

$ git status
On branch Branch-5.2
Your branch is ahead of 'origin/Branch-5.2' by 1354 commits.
  (use "git push" to publish your local commits)
nothing to commit, working directory clean


A few nodes report

$ git status
On branch Branch-5.2
Your branch is up-to-date with 'origin/Branch-5.2'.
nothing to commit, working directory clean

Should I change something to ensure consistency across regression tests?

—
Dan Langille
http://langille.org/







signature.asc
Description: Message signed with OpenPGP using GPGMail
--
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] [Bacula-devel] FreeBSD 10.2 & Bacula 7.2 compile errors

2015-10-01 Thread Dan Langille


> On Sep 21, 2015, at 10:16 PM, Dan Langille  wrote:
> 
> I only just got back to this today, and I saw Kern's post about Eric's work.  
> I am happy to report: no more compile errors.
> 
> re: 
> http://www.bacula.org/git/cgit.cgi/bacula/commit/?id=26db75ea69d9f097c5de207d180fd58909c4fbec
> 
> However, regression tests are not starting.  That will be another post.

Regression testing on FreeBSD is successful: 
http://regress.bacula.org/index.php?project=bacula=2015-09-30

The problem I mentioned above was because I was not on the correct branch.

I'll start work on upgrading the Bacula port next week.

—
Dan Langille
http://langille.org/







signature.asc
Description: Message signed with OpenPGP using GPGMail
--
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] [Bacula-devel] FreeBSD 10.2 & Bacula 7.2 compile errors

Re: [Bacula-users] Question about bacula and tls

Re: [Bacula-users] is 7.2 ready for prime time?

Re: [Bacula-users] git status - for regression testing

Re: [Bacula-users] git status - for regression testing

[Bacula-users] Which JobID did my Verify verify?

Re: [Bacula-users] git status - for regression testing

Re: [Bacula-users] is 7.2 ready for prime time?

Re: [Bacula-users] git status - for regression testing

Re: [Bacula-users] Bacula Verify Jobs

Re: [Bacula-users] getting a full system backup

Re: [Bacula-users] [Bacula-devel] volume name / label format bug with 7.0.5 after failed job

Re: [Bacula-users] ERR message

[Bacula-users] git status - for regression testing

Re: [Bacula-users] [Bacula-devel] FreeBSD 10.2 & Bacula 7.2 compile errors

15 matches

Site Navigation

Mail list logo

Footer information