Troubleshooting SG0083: Unable to Send Backup Details to Server Error

SG0083: Error - Unable to Send Backup Details to Server

KB ID: 115109
Cause:
When performing backup jobs, the error "Unable to send backup details to server" may occur. This error is typically associated with large backup data sizes or unstable network connectivity.
Solution:
To address this issue, please follow the steps below:
1. Check Network Connectivity:
Ensure that the client machine can connect to the backup server on port 32004. You can verify this by executing the 'telnet <Server IP Address> 32004' command from the BDRSuite client system's command prompt. If the telnet command fails, review your firewall settings on the BDRSuite Backup Server machine to allow traffic on port 32004.
 Note: If port 32004 is in the LISTEN state and the telnet command still fails, ensure that port 32004 is open in the server network's NAT/Firewall configuration.
2. Confirm Port Configuration:
Verify that both the client machine and the backup server are configured to use the same backup port, which is, by default, set to 32004. You can check this configuration in the "<vembu home="">/conf/SGConfiguration.conf" file.
3. Test Connectivity:
Check the connectivity between the client and backup server by running the following commands:
  1. Run "ping <server IP address>" command.
  2. Run "telnet <server IP address> 32004" command.
4. Hosts File Configuration:
If the issue persists, add the backup server's IP address to the 'C:/Windows/System32/drivers/etc/hosts' file on Windows or /etc/hosts file on Linux in the Vembu client machine.
5. Modify Configuration:
In both the Vembu Backup Server and Client Machine, follow these steps:
  1. Navigate to the Vembu installation directory >> Conf >> SGConfiguration.conf.
  2. Reduce the 'KeepAliveTime' attribute (located near '<Configuration><Module StartModule') from 60 to 30.
  3. Increase the 'FileAck' and 'BackupAck' attribute values from 120 to 600 seconds under the '<SGTimeOutConfig>' tag.
  4. Increase the attribute values for <ServerReconnectTimeOut> to 3600 and <ClientReconnectTimeOut> to 1800.
  5. After making these changes, restart the Vembu services.
If the issue persists despite following the above steps, please contact vembu-support@vembu.com for further assistance.