A backup fails with the following errors in the binary log:
Background 2008/05/19 22:04:08 0 System BAKBONE Machine 'NETVAULT' has gone down
Error 2008/05/19 22:04:08 001 Jobs BAKBONE Child Process died unexpectedly
The Machine 'NETVAULT' has gone down leads to the job 001 failing with 'Child Process died unexpectedly'.
The message "machine gone down" suggests that the backup server lost a network connection with the client.
There are some settings that can be changed within NetVault that aid network communication in idle states of backups:
1) On the backup server and launch the NetVault Configurator and go to the "Job Manager" tab:
Change the value of "Job Keep alive rate in minutes" to '1' .
2) On the backup server and client launch the NetVault Configurator and go to the "Network Manager" tab:
Change "Time wait before dropping inactive connection" from 300 to 600.
Change “Keep Alive Rate” from 15 to 7.
Change “Time in second to complete connection” from 30 to 60.
Change “Time between availability broadcasts” from 300 to 600.
Change “Time between security broadcasts” from 300 to 600.
If this does not make any difference, then please look into the following likely causes of network connection issues with NetVault:
A) Does forward and reverse DNS lookup work between the client and server?
To check this, please perform the following commands on both client and server and send the output to Quest Technical Support.
nslookup "nodename"
nslookup "ipaddress"
Where "nodename" is the hostname of the NetVault client and/or NetVault server
And "ipaddress" is the IP address of the NetVault client and/or NetVault server
For example:
On the Server enter:
nslookup client_name
nslookup client_IP
nslookup server_name
nslookup server_IP
telnet client_IP 20031
On the Client enter:
nslookup client_name
nslookup client_IP
nslookup server_name
nslookup server_IP
telnet server_IP 20031
B) Does the client have more than 1 NIC on the system and is it teamed?
If there is more than 1 NIC and it is not teamed, determine which one is to be used for backups, then set this as "Preferred Address" and any others as "Barred Address" on the NetVault Configurator on the "Network Manager | Connections" tab.
If the NICs are teamed, ensure that both NICs are connected to the same switch and the ports on the switch are configured correctly for teaming. An easy way of check if there is a problem with the teaming is to disconnect one of the cables from a NIC and run the backup.
C) Is there a firewall between the NetVault server and the client? If so, are there enough ports open and are the correct ports open? Are the relevant clients configured as "Outside Firewall" on the Client Management screen of NetVault Console?
D) If there is no Firewall between the NetVault Server and Client, then make sure that the Firewall is disabled on all Windows machines.
BakBone SFDC Solution Number: 00003657
