Hi Ana,
My bacula installation is version 5.2.13.
Matthew
On 09/09/2015 02:04 PM, Ana Emília M. Arruda wrote:
> Hello Matthew,
>
> Which version are you using? :: worked for me in 7.2.0.
>
> Director {
> Name = x-dir
> DirAddresses = {
> ipv6 = { addr=::; port=9101 }
> }
>
> xx
Hello Matthew,
Which version are you using? :: worked for me in 7.2.0.
Director {
Name = x-dir
DirAddresses = {
ipv6 = { addr=::; port=9101 }
}
x-dir: bnet_server.c:87-0 Addresses [::]:9101
tcp0 0 :::9101 :::*LISTEN
Best rega
It says "Config error: Can't add hostname(::/0) and port(9103) to addrlist".
Matthew
On 09/09/2015 12:55 PM, Josh Fisher wrote:
>
> On 9/9/2015 2:54 PM, Matthew Voss wrote:
>> Hi All,
>>
>> I'm trying to make the Storage Daemon visible via IPv6. I've followed
>> this[1] guide without success. I'v
On 9/9/2015 2:54 PM, Matthew Voss wrote:
> Hi All,
>
> I'm trying to make the Storage Daemon visible via IPv6. I've followed
> this[1] guide without success. I've also attempted to use the
> SDAddresses directive like this:
>
> SDAddresses = {
> ip = {
> addr = ::
> port =
Hi All,
I'm trying to make the Storage Daemon visible via IPv6. I've followed
this[1] guide without success. I've also attempted to use the
SDAddresses directive like this:
SDAddresses = {
ip = {
addr = ::
port = 9103
}
}
The storage daemon seemed to go silent when I used
The log file!
08-Set 22:00 bacula-dir JobId 1609: Start Backup JobId 1609,
Job=Backup_VM_Servidor_Intranet.2015-09-08_22.00.00_02
08-Set 22:00 bacula-dir JobId 1609: Using Device "DiscoLocal2" to write.
08-Set 22:01 srv_hyperv-fd JobId 1609: shell command: run
ClientRunBeforeJob "powershell C:/'Pr
Good Mornig
Yesterday I've made my first backup of virtual machines (after a lot of
tests).
I'm using a script to shutdown the machines, bacula copy the .vhd and .vhdx
files,
and after copy, start vm's again.
I have 3 vm's (2 Windows Server 2012 R2 and 1 Linux Debian 7.7) and the vm
host is Windo
Actually it was not a tape problem it seems, when the server rebooted
after the power failure the device names nst0 and nst1 switched which
physical device they linked to. Using persistent names with udev rules
fixed the problem and backups are running again.
Thanks
Kevin
On Thu, 2015-09-03 at 0