>
> On 2013-11-29 18:37, Tim Dunphy wrote:
> ... (and unfortunately I feel like I'm spinning in circles)
>
> Maybe you should try a different circle, like try stunnel?
>
Not the worst idea I've heard. Or maybe sshuttle. Still would prefer to
work out the Bacula approach, provided it doesn't cause
On 2013-11-29 18:37, Tim Dunphy wrote:
... (and unfortunately I feel like I'm spinning in circles)
Maybe you should try a different circle, like try stunnel?
Dima
--
Rapidly troubleshoot problems before they affect you
Even more info is needed... db backend used, Number of files in backup
job, clientfilesystem type & memory config, bacula director hardware
etc.
Cheers, Uwe
I'm not sure on the DB backend, I'm a bit of a newbie with this stuff.
The number of files being backed up looks to be about 82k, to
On Thu, Nov 28, 2013 at 05:56:42PM -0800, bradbpw wrote:
> More info. I ran a iperf test, it seems oddly high, there is no way these
> can be the actual transfer rates, right?
>
>
> brad@home-server:~$ iperf -c 63.227.74.80 -p 9102 -f Kbytes -i 1 -t 10
Even more info is needed... db backend us
Le 27/11/2013 12:06, bulent a écrit :
> Hi all,
>
> I'm new on bacula and make a test platform.
>
> I try to install my database server (postgresql 9.1) on a different server of
> bacula-director.
> No problem for the PostgreSQL server.
> But when i try to install director on another server, whith
Hi List,
our bacula director (Debian Squeeze, squeeze-backports, Version 5.2.6)
keeps crashing during the nightly backup runs (>400 jobs). I looked at
the traceback from last nights crash and it looks rather strange:
Here is a small excerpt from the traceback:
Attempt to dump current JCRs. njc