Re: [Bacula-users] Typical tape write performance

[Alan Brown]

On 02/12/15 12:14, Paul Elliott wrote:

>>   Maximum block size = 2M
>
> Have you experienced any issues with that block size?

Only when the drives/tapes are dirty and then you get excess errors on 
all block sizes anyway.

Because entire blocks are rewritten if there is an error, "tape waste" 
goes up, but even with small blocks I've seen 75% of a tape lost to 
rewrites.

You do need to watch those stats and react quickly if they're climbing - 
where react quickly == put a cleaning tape in the drive asap.

Unfortunately Bacula does not lend itself well to such interventions.


We had one major incident where a faulty HP LTO5 tape contaminated a 
drive (beyond the point where a cleaning tape would work). That drive 
then proceeded to contaminate the next 10 tapes loaded into it and those 
tapes then cross-contaminated the other drives before we realised what 
was happening.

Tape manufacturer warranties don't cover consequential damages of this 
type so this can get quite expensive to sort out. (The maintenance 
agreement on the drives covered it, but it was still highly disruptive)

The more general problem is environmental cleanliness. Human skin dust 
(which is almost all dust in a household or office environemnt) is one 
of the worst possible contaminants for tapes because it's slightly greasy.

Neither standalone or library manufacturers pay any attention to this 
issue, with non-filtered inlets and enclosure fans invaribly pulling air 
through the tape mechanisms.

If at all possible, tape drives/libraries should be in heavily filtered 
environments with as few humans around as possible.
I strongly recommend against having them in a server room if you can 
avoid it. A dedicated closet/room is better and ideally your data safe 
should be colocated with the library (less handling, less risk).

I'd recommend active air filtration (scrubbers) and humidity control if 
you can get it too. The cleaner the environment, the fewer problems 
you'll have with the drives.

As an example of this: When building work was performed in the server 
room, despite the library being partitioned off with plastic sheeting, 
every single drive failed within 6 weeks.

>> These are local-specific (my spool has up to 20 jobs feeding into 280GB 
>> of
>> available space) and if you have more space/fewer jobs I'd consider
>> bumping the Job spool size anything up to 100GB
>>   Maximum Spool Size = 120G
>>   Maximum Job Spool Size = 30G
>
> What's the advantage of the maximum job spool size setting?

These are tunables.

Job Spool size is effectively the chunk size of the backups on tape - in 
this case, 30GB.

This allows various jobs to interleave on the tape drive without 
impacting restore speeds badly.

Maximum Spool Size is a device limit. It's set to try and run out of 
spool space. It's not healthy to get up to the limit as jobs will start 
spooling, run out of disk space and them despool. If that chunk is only 
a few tens of MB then you affect overall throughouts.

Setting both is a matter of compromise. I'd prefer to use 50-100GB Job 
spool size but my spool area is too small to allow that without risking 
runing out of disk space.

I've also got a run-before script which tests spool space and holds the 
job if it's over 70% (sleep on failure, then loop and test again). We 
get better overall throughput this way than by letting jobs fight over 
the spool.

The same script checks the number of jobs actually running on the client 
and imposes a hard limit on the number of full backups in progress. On 
the fileservers (200-800TB apiece) it's set to 15 
incremental/differentials and 6 fulls(we backup in 1Tb segments), 
because more than that many fulls start affecting both througput and 
server latencies (again, sleep and loop). Bacula's maximum concurrent 
jobs settings don't provide enough granularity for our needs.





--
Go from Idea to Many App Stores Faster with Intel(R) XDK
Give your users amazing mobile app experiences with Intel(R) XDK.
Use one codebase in this all-in-one HTML5 development environment.
Design, debug & build mobile apps & 2D/3D high-impact games for multiple OSs.
http://pubads.g.doubleclick.net/gampad/clk?id=254741911=/4140
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Typical tape write performance

[Paul Elliott]

On Wed, 02, Dec, 2015 at 03:04:07PM +, Alan Brown spoke thus..
> On 02/12/15 12:14, Paul Elliott wrote:
> >>  Maximum block size = 2M
> >Have you experienced any issues with that block size?
> Only when the drives/tapes are dirty and then you get excess errors on all
> block sizes anyway.
> Because entire blocks are rewritten if there is an error, "tape waste" goes
> up, but even with small blocks I've seen 75% of a tape lost to rewrites.
> You do need to watch those stats and react quickly if they're climbing -
> where react quickly == put a cleaning tape in the drive asap.

How are you currently monitoring the error counts? I've not found a
useful solution on Linux but maybe I'm missing something!

> Unfortunately Bacula does not lend itself well to such interventions.

Agreed. We had to turn off auto cleaning on our tape library as it would
conflict with bacula's operations which is a shame. If we could find a
way to query the drive to see if it requires a cleaning then it should
be possible for us to load a cleaning tape using a pre-job script.
> >What's the advantage of the maximum job spool size setting?

> These are tunables.
 
> I've also got a run-before script which tests spool space and holds the job
> if it's over 70% (sleep on failure, then loop and test again). We get better
> overall throughput this way than by letting jobs fight over the spool.

That's an interesting way of dealing with concurrency issues. Neat.

Thanks, Paul.

-- 
Paul Elliott, UNIX Systems Administrator
York Neuroimaging Centre (YNiC), University of York


--
Go from Idea to Many App Stores Faster with Intel(R) XDK
Give your users amazing mobile app experiences with Intel(R) XDK.
Use one codebase in this all-in-one HTML5 development environment.
Design, debug & build mobile apps & 2D/3D high-impact games for multiple OSs.
http://pubads.g.doubleclick.net/gampad/clk?id=254741911=/4140
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

[Bacula-users] Configuring Bacula File Daemon on High-availability Replicated Servers

[Rich Otero]

Hello,

I have a system where the Bacula File Daemon must run on a
high-availability pair of servers. I have some services managed by
Pacemaker, but I have not configured this yet for the Bacula services. If I
configure bacula-fd identically  and start it on both servers in the HA
pair, will there be a problem? In other words, does bacula-fd attempt to
connect to bacula-dir, or does bacula-dir only connect to bacula-fd when
needed? If it's the former scenario, then it is necessary for me to
configure Pacemaker to start and stop bacula-fd on the HA servers so that
only one has it running at a time. If it is the latter scenario, then I can
setup init to start bacula-fd on both servers and simply configure
bacula-dir to find its clients at the HA "floating" IP address that is
managed by Pacemaker.

Thanks for your help.

Regards,
Rich Otero
Director, Technical Support and Professional Services
EditShare
rot...@editshare.com
617-782-0479
--
Go from Idea to Many App Stores Faster with Intel(R) XDK
Give your users amazing mobile app experiences with Intel(R) XDK.
Use one codebase in this all-in-one HTML5 development environment.
Design, debug & build mobile apps & 2D/3D high-impact games for multiple OSs.
http://pubads.g.doubleclick.net/gampad/clk?id=254741911=/4140___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

[Bacula-users] Bacula Deduplication

[John O'Neill]

Hi All,

I was wondering if you all might be able to give me thoughts on something
we are looking at implementing. We have a windows file server which we
currently backup using bacula.

This runs completely without issue and is generally rock solid. We are
however going to be hitting a bump in the road soon, one of the shares on
the file server is for our design team. The files are all very large and
the versioninig system they use is a little odd, it results in us having
lots of files of very similar nature

They have a lot of historical files from projects which are closed off now
but for business reasons cannot be archived off.

We are coming close to a time now where our monthly full back up will
exceed the window we have available to us.

To this end I am looking at the Bacula de-duplication option to create a
base job for the file server, I would then reference this base job in the
back up of the file server in the hope of achieving 1) some space saving
and 2) an decrease in time it takes to backup

Does any one have any opinions on this as to whether or not it will work
and is it a good idea or not ?

Cheers,
John
--
Go from Idea to Many App Stores Faster with Intel(R) XDK
Give your users amazing mobile app experiences with Intel(R) XDK.
Use one codebase in this all-in-one HTML5 development environment.
Design, debug & build mobile apps & 2D/3D high-impact games for multiple OSs.
http://pubads.g.doubleclick.net/gampad/clk?id=254741911=/4140___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Configuring Bacula File Daemon on High-availability Replicated Servers

[Dimitri Maziuk]

On 12/02/2015 12:22 PM, Rich Otero wrote:
...
> configure Pacemaker to start and stop bacula-fd on the HA servers so that
> only one has it running at a time. If it is the latter scenario, then I can
> setup init to start bacula-fd on both servers and simply configure
> bacula-dir to find its clients at the HA "floating" IP address that is
> managed by Pacemaker.

What are you backing up? I run 3 bacula clients for 2 HA nodes. I have
drbd pairs where I'm backing up /etc on each node *and* the drbd
filesystem on the floating ip.

For the latter, fd runs on a different port and is started by heartbeat.
Bacula-dir looks for it at the floating ip. If you aren't backing up any
shared data, you don't need that.

For the former: stock setup starting from init using fixed ips. If you
aren't backing up any local data you don't need that (but you probably
want to back up your etcs and crontabs).

HTH
-- 
Dimitri Maziuk
Programmer/sysadmin
BioMagResBank, UW-Madison -- http://www.bmrb.wisc.edu



signature.asc
Description: OpenPGP digital signature
--
Go from Idea to Many App Stores Faster with Intel(R) XDK
Give your users amazing mobile app experiences with Intel(R) XDK.
Use one codebase in this all-in-one HTML5 development environment.
Design, debug & build mobile apps & 2D/3D high-impact games for multiple OSs.
http://pubads.g.doubleclick.net/gampad/clk?id=254741911=/4140___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Typical tape write performance

[Dan Langille]

> On Dec 2, 2015, at 10:04 AM, Alan Brown  wrote:
> 
> On 02/12/15 12:14, Paul Elliott wrote:
> 
>>>  Maximum block size = 2M
>> 
>> Have you experienced any issues with that block size?
> 
> Only when the drives/tapes are dirty and then you get excess errors on all 
> block sizes anyway.
> 
> Because entire blocks are rewritten if there is an error, "tape waste" goes 
> up, but even with small blocks I've seen 75% of a tape lost to rewrites.
> 
> You do need to watch those stats and react quickly if they're climbing - 
> where react quickly == put a cleaning tape in the drive asap.
> 
> Unfortunately Bacula does not lend itself well to such interventions.
> 
> 
> We had one major incident where a faulty HP LTO5 tape contaminated a drive 
> (beyond the point where a cleaning tape would work). That drive then 
> proceeded to contaminate the next 10 tapes loaded into it and those tapes 
> then cross-contaminated the other drives before we realised what was 
> happening.
> 
> Tape manufacturer warranties don't cover consequential damages of this type 
> so this can get quite expensive to sort out. (The maintenance agreement on 
> the drives covered it, but it was still highly disruptive)
> 
> The more general problem is environmental cleanliness. Human skin dust (which 
> is almost all dust in a household or office environemnt) is one of the worst 
> possible contaminants for tapes because it's slightly greasy.
> 
> Neither standalone or library manufacturers pay any attention to this issue, 
> with non-filtered inlets and enclosure fans invaribly pulling air through the 
> tape mechanisms.
> 
> If at all possible, tape drives/libraries should be in heavily filtered 
> environments with as few humans around as possible.
> I strongly recommend against having them in a server room if you can avoid 
> it. A dedicated closet/room is better and ideally your data safe should be 
> colocated with the library (less handling, less risk).
> 
> I'd recommend active air filtration (scrubbers) and humidity control if you 
> can get it too. The cleaner the environment, the fewer problems you'll have 
> with the drives.
> 
> As an example of this: When building work was performed in the server room, 
> despite the library being partitioned off with plastic sheeting, every single 
> drive failed within 6 weeks.

The spare bedroom in my apartment does not meet these specifications.

I'll look at adding filters from http://www.demcifilter.com/ before powering it 
up.

— 
Dan Langille
http://langille.org/






--
Go from Idea to Many App Stores Faster with Intel(R) XDK
Give your users amazing mobile app experiences with Intel(R) XDK.
Use one codebase in this all-in-one HTML5 development environment.
Design, debug & build mobile apps & 2D/3D high-impact games for multiple OSs.
http://pubads.g.doubleclick.net/gampad/clk?id=254741911=/4140
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Configuring Bacula File Daemon on High-availability Replicated Servers

[Rich Otero]

Thanks, Dimitri. I am backing up shared data. I've done some testing with
independent bacula-fd instances running at the same time with identical
configuration on both nodes. Bacula-dir is configured to connect to the
client at the floating IP address. It seems to work well. I have failed
over the floating IP address with Pacemaker in both direction and Bacula
seems to keep working as expected. I just wanted to make sure that I'm not
doing something that is bad for Bacula that is going to hurt me later.
Thanks for your input.

Regards,
Rich Otero
Director, Technical Support and Professional Services
EditShare
rot...@editshare.com
617-782-0479

On Wed, Dec 2, 2015 at 1:56 PM, Dimitri Maziuk 
wrote:

> On 12/02/2015 12:22 PM, Rich Otero wrote:
> ...
> > configure Pacemaker to start and stop bacula-fd on the HA servers so that
> > only one has it running at a time. If it is the latter scenario, then I
> can
> > setup init to start bacula-fd on both servers and simply configure
> > bacula-dir to find its clients at the HA "floating" IP address that is
> > managed by Pacemaker.
>
> What are you backing up? I run 3 bacula clients for 2 HA nodes. I have
> drbd pairs where I'm backing up /etc on each node *and* the drbd
> filesystem on the floating ip.
>
> For the latter, fd runs on a different port and is started by heartbeat.
> Bacula-dir looks for it at the floating ip. If you aren't backing up any
> shared data, you don't need that.
>
> For the former: stock setup starting from init using fixed ips. If you
> aren't backing up any local data you don't need that (but you probably
> want to back up your etcs and crontabs).
>
> HTH
> --
> Dimitri Maziuk
> Programmer/sysadmin
> BioMagResBank, UW-Madison -- http://www.bmrb.wisc.edu
>
>
>
> --
> Go from Idea to Many App Stores Faster with Intel(R) XDK
> Give your users amazing mobile app experiences with Intel(R) XDK.
> Use one codebase in this all-in-one HTML5 development environment.
> Design, debug & build mobile apps & 2D/3D high-impact games for multiple
> OSs.
> http://pubads.g.doubleclick.net/gampad/clk?id=254741911=/4140
> ___
> Bacula-users mailing list
> Bacula-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bacula-users
>
>
--
Go from Idea to Many App Stores Faster with Intel(R) XDK
Give your users amazing mobile app experiences with Intel(R) XDK.
Use one codebase in this all-in-one HTML5 development environment.
Design, debug & build mobile apps & 2D/3D high-impact games for multiple OSs.
http://pubads.g.doubleclick.net/gampad/clk?id=254741911=/4140___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Bacula Deduplication

[Silver Salonen]

On 02.12.2015 22:54, John O'Neill wrote:


Hi All,

I was wondering if you all might be able to give me thoughts on 
something we are looking at implementing. We have a windows file 
server which we currently backup using bacula.


This runs completely without issue and is generally rock solid. We are 
however going to be hitting a bump in the road soon, one of the shares 
on the file server is for our design team. The files are all very 
large and the versioninig system they use is a little odd, it results 
in us having lots of files of very similar nature


They have a lot of historical files from projects which are closed off 
now but for business reasons cannot be archived off.


We are coming close to a time now where our monthly full back up will 
exceed the window we have available to us.


To this end I am looking at the Bacula de-duplication option to create 
a base job for the file server, I would then reference this base job 
in the back up of the file server in the hope of achieving 1) some 
space saving and 2) an decrease in time it takes to backup


Does any one have any opinions on this as to whether or not it will 
work and is it a good idea or not ?


Cheers,
John



Hi.

It sounds to me that you should be updating the base image quite often 
in order to avoid all this new data periodically.


Depending on how static the data actually is after it's created I would 
suggest two possible solutions that utilize some smart scripts to 
determine which files to backup and how:


 * Script that finds all "older than something" files and adds them to
   archive-type incremental backup which are stored for a period of
   your retention time
 * Script that finds all duplicates by checksums and backs up only one
   of those files (I haven't try this myself, so wouldn't guess how
   much resources would this solution require)

--
Silver
--
Go from Idea to Many App Stores Faster with Intel(R) XDK
Give your users amazing mobile app experiences with Intel(R) XDK.
Use one codebase in this all-in-one HTML5 development environment.
Design, debug & build mobile apps & 2D/3D high-impact games for multiple OSs.
http://pubads.g.doubleclick.net/gampad/clk?id=254741911=/4140___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Configuring Bacula File Daemon on High-availability Replicated Servers

[Dimitri Maziuk]

On 12/02/2015 03:08 PM, Rich Otero wrote:
> Thanks, Dimitri. I am backing up shared data. I've done some testing with
> independent bacula-fd instances running at the same time with identical
> configuration on both nodes. Bacula-dir is configured to connect to the
> client at the floating IP address. It seems to work well. I have failed
> over the floating IP address with Pacemaker in both direction and Bacula
> seems to keep working as expected. I just wanted to make sure that I'm not
> doing something that is bad for Bacula that is going to hurt me later.

Well I think linux kernel may/did sometimes send reply packets with the
actual rather than floating source ip -- but even if it does I don't see
why that would be a problem for bacula.

-- 
Dimitri Maziuk
Programmer/sysadmin
BioMagResBank, UW-Madison -- http://www.bmrb.wisc.edu



signature.asc
Description: OpenPGP digital signature
--
Go from Idea to Many App Stores Faster with Intel(R) XDK
Give your users amazing mobile app experiences with Intel(R) XDK.
Use one codebase in this all-in-one HTML5 development environment.
Design, debug & build mobile apps & 2D/3D high-impact games for multiple OSs.
http://pubads.g.doubleclick.net/gampad/clk?id=254741911=/4140___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Typical tape write performance

[Dan Langille]

On Nov 30, 2015, at 12:18 PM, Alan Brown  wrote:
> 
>> On 30/11/15 16:57, Christoph Litauer wrote:
>> Hi Alan,
>> 
>> maybe this is an important hint …
>> I thought btape doesn't use a disk at all. Instead it uses on-the-fly 
>> generation of test data … does it?
> 
> If it does, that could easily be your bottleneck. /dev/random isn't 
> normally very fast.
> 
>> If btape uses the configured spool directory I have to take a look at that 
>> point.
> 
> For LTO, the Spool disk MUST be at least least one SSD, preferably a 
> stripe of them on as fast a controller as you can afford. Standard disks 
> simply can't keep up with tape drives.

I had not considered that. In my case, I backup to local HDD (ZFS array) for 
long term storage.  Right after those jobs finish, I copy to tape. Sounds like 
I need to implement spooling now. Fortunately, my full backups are only about 
400GB. I think I can get away with one SSD feeding my LTO-4. 
--
Go from Idea to Many App Stores Faster with Intel(R) XDK
Give your users amazing mobile app experiences with Intel(R) XDK.
Use one codebase in this all-in-one HTML5 development environment.
Design, debug & build mobile apps & 2D/3D high-impact games for multiple OSs.
http://pubads.g.doubleclick.net/gampad/clk?id=254741911=/4140
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Typical tape write performance

[Alan Brown]

>> For LTO, the Spool disk MUST be at least least one SSD, preferably a
stripe of them on as fast a controller as you can afford. Standard disks
simply can't keep up with tape drives.

> I had not considered that. In my case, I backup to local HDD (ZFS
array) for long term storage. Right after those jobs finish, I copy to
tape. Sounds like I need to implement spooling now. Fortunately, my full
backups are only about 400GB. I think I can get away with one SSD
feeding my LTO-4.
You should also consider doing the following in bacula-sd tape drive stanzas

  Maximum File Size = 16G
  Maximum Network Buffer Size = 262144
  Maximum block size = 2M

The tape drive stops every time it writes a file marker, and the default
1G size is far too small for LTO. The constant start/stop drop average
throughput dramatically

I would make the block size larger, but 2MB is the maximum supported by
Bacula.
(LTO supports up to 16MB - Kern - Big hint here!)

These are local-specific (my spool has up to 20 jobs feeding into 280GB
of available space) and if you have more space/fewer jobs I'd consider
bumping the Job spool size anything up to 100GB

  Maximum Spool Size = 120G
  Maximum Job Spool Size = 30G

The current spool area is a stripe of 5 Intel X25E drives on an adaptec
51245 raid controller. These are old but being SLC are still extremely
fast and despite having handled several PB of throughput are still only
a couple percent worn. The controller itself is the limiting factor and
I'm looking at dumping it in favour of linux raid0 on an 8 port 12GB/s HBA.

Whatever you use, you _MUST_ benchmark them and pay particular attention
to the "steady state" write speeds - this is where you write/delete
several times the SSD capacity without using "trim" commands to
precondition it and then benchmark how fast it continues to write
without using trim.

What this tests is how well the drive works out that data blocks need to
be reallocated, rearranges data, erases the underlaying flash chunks and
makes them available. In a lot of MLC drives you can see a 95-98%
dropoff in write speed under such conditions.

The worst case I've seen so far is 500MB Samsung 840Pros, which go from
300-500MB/s steady state write speeds down to 5-10 second pauses with
7-8MB write bursts (or worse). I was using these as the database drives
on another Adaptec 51245 controller (which don't support trim commands)
and it completely trashed backup performance because despooling
attributes to the database ended up taking an hour for 2-3 million file
full backups (1TB data). Moving those same drives off the raid
controller into trim-supporting interfaces dropped despooling time down
to 15 seconds.

By contrast, the X25Es - which on paper look bad against "modern" drives
at only 3000 write IOPs - simply don't slow down at all (they don't
support trim anyway) and keep on writing at 200-300MB/s apiece. More
importantly for my use, when there are 10 write and 5 read streams going
on, they don't slow down in either direction.

If I was speccing a machine now, I'd use a PCIe SSD such as an Intel DC
P3700 for spool or even consider using a ramdisk if I could get enough
memory past management (it's a lot cheaper than it used to be).


Dan - in your case (ZFS), you need to pay attention to steady-state
write speeds because ZFS on most platforms doesn't trim (yet - it's in
OpenZFS devel trees) and because of that I've found that similar
problems apply to L2ARC/SLOG drives which can severely hobble ZFS
performance.




--
Go from Idea to Many App Stores Faster with Intel(R) XDK
Give your users amazing mobile app experiences with Intel(R) XDK.
Use one codebase in this all-in-one HTML5 development environment.
Design, debug & build mobile apps & 2D/3D high-impact games for multiple OSs.
http://pubads.g.doubleclick.net/gampad/clk?id=254741911=/4140___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Typical tape write performance

[Paul Elliott]

Hi Alan,

On Wed, 02, Dec, 2015 at 11:46:40AM +, Alan Brown spoke thus..
>You should also consider doing the following in bacula-sd tape drive
>stanzas
>  Maximum File Size = 16G
>  Maximum Network Buffer Size = 262144
>  Maximum block size = 2M

Have you experienced any issues with that block size? We're using LTO5
and will be moving to LTO6 in the next few weeks but we're still using a
256k block size based on this (possibly outdated) advice from Kern:

https://adsm.org/lists/html/Bacula-users/2013-09/msg00104.html

I would be interested to hear what block sizes other LTO5/6 users are
using?

>These are local-specific (my spool has up to 20 jobs feeding into 280GB of
>available space) and if you have more space/fewer jobs I'd consider
>bumping the Job spool size anything up to 100GB
>  Maximum Spool Size = 120G
>  Maximum Job Spool Size = 30G

What's the advantage of the maximum job spool size setting? We're not
using any spooling at the moment so I'm interesting in what parameters
would be best for our setup. (if any..)

Thanks, Paul.

-- 
Paul Elliott, UNIX Systems Administrator
York Neuroimaging Centre (YNiC), University of York


--
Go from Idea to Many App Stores Faster with Intel(R) XDK
Give your users amazing mobile app experiences with Intel(R) XDK.
Use one codebase in this all-in-one HTML5 development environment.
Design, debug & build mobile apps & 2D/3D high-impact games for multiple OSs.
http://pubads.g.doubleclick.net/gampad/clk?id=254741911=/4140
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Restoring Files backed up on Windows Client to FreeBSD Client, files all wrong size.

[Uwe Schuerkamp]

On Tue, Dec 01, 2015 at 12:29:53PM -0600, dweimer wrote:
> 
> I will do some more test restores to the client now that its up, to see 
> if its only when restoring to the freebsd client. I have verified 
> restores to the FreeBSD client of itself restore correctly. just curious 
> if someone else has seen this?
> 

Yep, we've seen the exact same issue on a few windows servers on one
bacula instance. At first I thought the tape was corrupt, but
restoring a Linux client from the same volume worked fine.

We discovered the issue by pure chance, client used on the windows box
is 5.2.13, but we've also seen the issue on a client running a
licensed Enterprise 7 version.

Cheers, Uwe









--
Go from Idea to Many App Stores Faster with Intel(R) XDK
Give your users amazing mobile app experiences with Intel(R) XDK.
Use one codebase in this all-in-one HTML5 development environment.
Design, debug & build mobile apps & 2D/3D high-impact games for multiple OSs.
http://pubads.g.doubleclick.net/gampad/clk?id=254741911=/4140
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] SPAM: Re: Restoring Files backed up on Windows Client to FreeBSD Client, files all wrong size.

[dweimer]

On 2015-12-02 7:25 am, Uwe Schuerkamp wrote:
> On Tue, Dec 01, 2015 at 12:29:53PM -0600, dweimer wrote:
>> 
>> I will do some more test restores to the client now that its up, to 
>> see
>> if its only when restoring to the freebsd client. I have verified
>> restores to the FreeBSD client of itself restore correctly. just 
>> curious
>> if someone else has seen this?
>> 
> 
> Yep, we've seen the exact same issue on a few windows servers on one
> bacula instance. At first I thought the tape was corrupt, but
> restoring a Linux client from the same volume worked fine.
> 
> We discovered the issue by pure chance, client used on the windows box
> is 5.2.13, but we've also seen the issue on a client running a
> licensed Enterprise 7 version.
> 
> Cheers, Uwe

The issue doesn't seem to appear on older versions of Bacula server, 
verified that I can restore to one we have running at work on a remote 
site. I was reviewing the documentation. In my case I am not worried 
about permissions, single user on the windows machine, however it seems 
to me that turning the portable=yes option on will disable the use of 
VSS. if I am reading that correctly? I don't care about permissions, but 
I do want to make sure I use VSS.

If that is the case I will stick with it the way it is. I only have a 
single windows system and would prefer to be able to restore files if 
needed in event that it goes down, without waiting to get it back 
online. Not that I have had much downtime on it, recent versions of 
windows have definitely been more stable. The last rebuild was simply 
done to upgrade from a 120GB to 480GB SSD drive for the system disk, I 
put it off until the 1511 update came out so I could reinstall straight 
to windows 10 instead of installing 8 and updating to windows 10

-- 
Thanks,
Dean E. Weimer
http://www.dweimer.net/

--
Go from Idea to Many App Stores Faster with Intel(R) XDK
Give your users amazing mobile app experiences with Intel(R) XDK.
Use one codebase in this all-in-one HTML5 development environment.
Design, debug & build mobile apps & 2D/3D high-impact games for multiple OSs.
http://pubads.g.doubleclick.net/gampad/clk?id=254741911=/4140
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Configuring Bacula File Daemon on High-availability Replicated Servers

[Josh Fisher]

On 12/2/2015 1:22 PM, Rich Otero wrote:

Hello,

I have a system where the Bacula File Daemon must run on a 
high-availability pair of servers. I have some services managed by 
Pacemaker, but I have not configured this yet for the Bacula services. 
If I configure bacula-fd identically  and start it on both servers in 
the HA pair, will there be a problem? In other words, does bacula-fd 
attempt to connect to bacula-dir, or does bacula-dir only connect to 
bacula-fd when needed? If it's the former scenario, then it is 
necessary for me to configure Pacemaker to start and stop bacula-fd on 
the HA servers so that only one has it running at a time. If it is the 
latter scenario, then I can setup init to start bacula-fd on both 
servers and simply configure bacula-dir to find its clients at the HA 
"floating" IP address that is managed by Pacemaker


It depends on what needs to be backed up. If only the shared storage on 
DRBD, etc. is to be backed up, then configure pacemaker to start/stop 
bacula-fd with a colocation constraint to force bacula-fd to run only on 
the machine having the floating IP, which will also be the machine where 
the shared storage is mounted.


If the HA nodes themselves are also to be backed up, then there will be 
3 instances of bacula-fd. Each node should run bacula-fd listening only 
at its internal LAN IP, and those bacula-fd instances will have FileSets 
that backup everything BUT shared storage. The bacula-fd listening only 
on the floating IP will still be controlled by pacemaker and will backup 
shared storage only. So there will be 3 FileSets, one for node-1 
non-shared storage, one for node-2 non-shared storage, and one for the 
shared storage only.


Remember that a one node failure will result in the shared storage being 
taken over by the surviving node. You need to be able to restore the 
failed node without affecting the shared storage, since the surviving 
node will be live and actively using the shared storage. The FileSets 
for the nodes MUST not specify any shared storage.



.

Thanks for your help.

Regards,
Rich Otero
Director, Technical Support and Professional Services
EditShare
rot...@editshare.com 
617-782-0479


--
Go from Idea to Many App Stores Faster with Intel(R) XDK
Give your users amazing mobile app experiences with Intel(R) XDK.
Use one codebase in this all-in-one HTML5 development environment.
Design, debug & build mobile apps & 2D/3D high-impact games for multiple OSs.
http://pubads.g.doubleclick.net/gampad/clk?id=254741911=/4140


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


--
Go from Idea to Many App Stores Faster with Intel(R) XDK
Give your users amazing mobile app experiences with Intel(R) XDK.
Use one codebase in this all-in-one HTML5 development environment.
Design, debug & build mobile apps & 2D/3D high-impact games for multiple OSs.
http://pubads.g.doubleclick.net/gampad/clk?id=254741911=/4140___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users