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
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 addre
Hello,
Note: btape does not spool -- it writes directly to the tape. When it
is writing random data, you may find that your CPU is maxed out.
The speeds you see are quite reasonable in my opinion. It is unusual
that one will reach the theoretical maximum speed.
I recommend that you stick with
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
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
> 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.
>
>
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
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 clien
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
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.
>
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"
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
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 h
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 iss
>> 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 thos
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 easil
16 matches
Mail list logo
