Host is fedora 19 running bacula version 5.2.13-12. I am attempting restore of
a
Windows client which is no longer active due to severe system problem. The idea
is to restore the client files to a directory on the host, rebuild the windows
system and copy the restored files on to the new
On Thu, Jul 18, 2013 at 01:05:01PM -0500, Christina Murphy wrote:
Hey y'all,
So I'm pretty much at a loss as far as what could be going wrong with my
configurations for my last client I need to set up.
The client's OS is Windows Server 2012, 64 bit. I thought I had everything
configured
Hello,
2013/7/19 Erik P. Olsen epod...@gmail.com
Host is fedora 19 running bacula version 5.2.13-12. I am attempting
restore of a
Windows client which is no longer active due to severe system problem. The
idea
is to restore the client files to a directory on the host, rebuild the
windows
On 19/07/13 10:36, Radosław Korzeniewski wrote:
Hello,
2013/7/19 Erik P. Olsen epod...@gmail.com mailto:epod...@gmail.com
Host is fedora 19 running bacula version 5.2.13-12. I am attempting
restore of a
Windows client which is no longer active due to severe system problem.
The
Hi,
Is there no Idea about this issue?
Regards, I
2013/7/17 Iban Cabrillo cabri...@ifca.unican.es
Dear,
We have a simple bacula configuration.
And autochanger with two tape device (LTO3 and LTO5), for two kind of
different backups. Both work when they run independently. But If a
Hello,
2013/7/19 Iban Cabrillo cabri...@ifca.unican.es
Hi,
Is there no Idea about this issue?
show storage
status director
status storage
send please
best regards
--
Radosław Korzeniewski
rados...@korzeniewski.net
On 2013-01-08 14:26, Dan Langille wrote:
Folks,
We have a change request for Bacula on FreeBSD:
http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/170882
That is: all the Bacula stuff which normally fits in /usr/local/etc/
into /usr/local/etc/bacula
On the first upgrade to this changed
Try setting HeartbeatInterval to 300 (or maybe 600) lots of switches
hang up long before
6000 seconds.
On 07/18/2013 08:05 PM, Christina Murphy wrote:
Hey y'all,
So I'm pretty much at a loss as far as what could be going wrong with
my configurations for my last client I need to set up.
The
You really should be putting everything into /opt/bacula. It is
*much* more backup friendly for disaster recovery situations.
Best regards,
Kern
On 07/19/2013 02:33 PM, Dan Langille wrote:
On 2013-01-08 14:26, Dan Langille wrote:
Folks,
We have a change request for Bacula on FreeBSD:
On Jul 19, 2013, at 3:33 PM, Kern Sibbald wrote:
You really should be putting everything into /opt/bacula. It is
*much* more backup friendly for disaster recovery situations.
Individual sysadmins can do that. But it goes against expected locations in
FreeBSD (indeed, several other OS):
On 07/19/2013 02:47 PM, Marcos Renato da Silva Junior wrote:
Hi,
After upgrade Debian Squeeze to Wheezy, bacula-dir dont start, send this
message :
Starting Bacula Director: /sbin/bacula-dir: error while loading shared
libraries: libmysqlclient_r.so.16: cannot open shared object file: No
On 07/19/2013 02:47 PM, Marcos Renato da Silva Junior wrote:
Hi,
After upgrade Debian Squeeze to Wheezy, bacula-dir dont start, send this
message :
Starting Bacula Director: /sbin/bacula-dir: error while loading shared
libraries: libmysqlclient_r.so.16: cannot open shared object file: No
On 07/19/2013 09:35 PM, Dan Langille wrote:
On Jul 19, 2013, at 3:33 PM, Kern Sibbald wrote:
You really should be putting everything into /opt/bacula. It is
*much* more backup friendly for disaster recovery situations.
Individual sysadmins can do that. But it goes against expected locations
Hi,
After upgrade Debian Squeeze to Wheezy, bacula-dir dont start, send this
message :
Starting Bacula Director: /sbin/bacula-dir: error while loading shared
libraries: libmysqlclient_r.so.16: cannot open shared object file: No
such file or directory
bacula-dir
ls -la /usr/lib | grep
14 matches
Mail list logo
