I've searched everywhere and can't seem to find the solution. My current setup
is such that I have bacula-dir, bacula-fd, and bacula-sd installed on one
CentOS 5.5 machine, and just the client (bacula-fd) installed on another CentOS
5.5 machine. iptables is totally off and is not running on
There's no reference to localhost or 127.0.0.1 in the bacula server config
files (bacula-fd.conf, bacula-sd.conf, and bacula-dir.conf) and there isn't any
reference to it in the file daemon in the client config file (bacula-fd.conf),
either. Is there another config file I might look for this?
I was just able to get this to work, thanks to your tip on the localhost bit. I
went back in bacula-dir.conf and indeed, under the storage daemon section, it
was set to localhost for the address. Changing that to the IP of the bacula-sd
fixed it.
The default is to restore to /tmp/bacula-restores on the client...but the
client is down, and I just need the files on a different disk. How do I restore
the files to a different server? Can I just do like this:
Where = linux-server-host-name(or IP address)/restores
?
Can you give me a little more detail? I'm fairly new to Linux and Bacula. Right
now Bacula and the storage device are on the same network as where I want to
put it, so for example we'll say the hostname/domainname is bacula (where the
director and bconsole are), the client that I'm restoring
One last thing...we'll say that the server that contains the backup is
somewhere else also, so the dead client, bacula, file storage, and intended
destination for restore files are all on different machines but same network
+--
Having the fd on the target was the key - thank you.
Can I ask why others use a dedicated restore point, then use SCP? Why not just
have bacula-fd running wherever you need to restore?
+--
|This was sent by rlh1...@gmail.com
I've scoured the universe for others with this problem, and I promise you, only
one other person has posted about this back in 2010 and there was no
resolution, or at least, nothing helpful. I've installed bacula-fd 5.0.2 on
Server 2008 R2. The FD started automatically after installation. I
The bacula registry key has this in it for bacula-fd.exe execution:
C:\Program Files\Bacula\bacula-fd.exe /service -c C:\Program
Files\Bacula\bacula-fd.conf
That is the correct location of bacula-fd.conf. In a command window, this
command seems to work:
PS C:\Program Files\Bacula .\bacula-fd
@Joeseph:
I am using 5.0.2 because that is the version of the director. The config file
is in the same folder as the fd .exe: C:\Program Files\Bacula\
+--
|This was sent by rlh1...@gmail.com via Backup Central.
|Forward SPAM
I can't telnet to that port...I believe the reason is because bacula-fd isn't
running to accept any connections, though. I've completely turned the firewall
off, so I don't think that's the problem
+--
|This was sent by
@Joseph:
Editing the config with a non-ASCII only editor will screw it up...? You've got
to be kidding me...I just used notepad in Windows. What should I use?
+--
|This was sent by rlh1...@gmail.com via Backup Central.
|Forward
Used notepad, the process is not running. It definitely will not start on
Windows.
+--
|This was sent by rlh1...@gmail.com via Backup Central.
|Forward SPAM to ab...@backupcentral.com.
@Joeseph: At your behest, I went back and saved the file as UTF-8, rather than
ANSI, and the bacula-fd.exe works! I never would have thought that. You just
made my day sir. MAY A THOUSAND BEAUTIFUL WOMEN SWOON AT YOUR FEET.
+--
14 matches
Mail list logo
