[Manual] System - Setting up backup server

Last Updated: Sep 18, 2017 11:50PM CEST


A backup server accepts data from backup clients and writes the data to disk media pools or tape media pools.


The system you want to use for the backup server must be listed as a node. Systems cannot be listed unless they have a NovaBackup DataCenter client installation.

How to proceed

1. Go to System > Nodes Management.
⇨ The Nodes Management window opens.
After the first initialization of the program, only the command server itself is displayed in the work pane. The relevant data from the selected system are displayed in the upper window. If multiple clients have been installed, they will automatically be listed here.
1. Double-click on the node you want to use as a backup server.
1. Right-click on the node and left-click on Edit Node in the context menu.
⇨ The Edit Node xxxx dialog box for setting up the server opens.
2. Click on [Create] under Backup Server to set up a backup server.
⇨ The confirmation prompt appears:
3. Are you sure you want to make this node act as backup server? Click on [Yes] and then on [OK] to close the window.


The backup server has been created. The node attribute Backup Server is set to Yes.

Return to Top

Test network address



When the backup server has been created, the network address (IP address) must be tested to ensure that it is correct. The network address is determined from the node itself and can be the IP of an iSCSI connection, for example. The IP address must be the network address of the node so that other systems can access this system.

How to proceed

Test IP address

Test the IP address as described below to make sure it is correct.
1. Go to System > Nodes Management.
2. Right-click on the node line and left-click on Update > SyncNodeInfo.
⇨ This function contacts the client which in turn tests the connection and indicates whether the connection is problem-free or not.

Change IP address

If the address is not correct, change the IP address as described below:
1. Go to System > Nodes Management.
2. Right-click on the node line and left-click on Edit Node.
⇨ The dialog box Edit Node xxxx opens.
3. Click on [Edit] under Configure Address.
⇨ The Configure Address window with the IP address opens.
4. Change the IP address a needed.
5. Click on [OK] to accept the entry.
6. Click on [OK] again to close all of the previous windows.


The corrected IP address has been assigned to the node and will be used from now on for communication with the system.

Return to Top

Addressing backup clients on the network



This chapter describes how to test communications between the client and the backup server. A ping probe is used to test communications.
The ping probe checks:
  • Whether the central management recognizes the client name.
  • Whether the central management is connected to the client.
  • Whether the client data transfer is working.
  • Whether the client recognizes the backup server name.
  • Whether the client is connected to the backup server.
  • Configuration of the backup server media pool and availability.

How to proceed

1. Go to Backup/Restore > Backup Jobs.
⇨ The window containing the list of the current backup jobs is displayed.
2. Right-click on any backup job and left-click on Ping from the context menu.
⇨ The ping utility is launched and checks the connections.


If all of the settings are correct and all of the selected systems are accessible, the functioning connections are displayed with a green checkmark in the Ping Job window.

Results containing errors

If a connection is not correct, it will be marked with a red checkmark in the Ping Job window.


Reasons for errors in the results:
  • Central management cannot recognize the client name.
  • The client port is blocked by a firewall.
  • The client cannot recognize the backup server name.

Central management cannot recognize the client name.

If the central management did not recognize the client name, an error message and the client's default ID address will be issued in a window after running the ping utility.
The Error in Socket API call error message means it was not possible to connect this ID address with the TCP connection (stream socket).

Possible causes:

Possible causes


The client IP address has been changed.

Correct the IP address in Nodes Management.
A firewall (including the Windows firewall) is blocking the client port from central management to the client.
Disable the firewall on the client side or create a rule for connections to the client at port 32334.
The client service is not running.
Initiate NBK DC Remote Executor Service/service on the client.

The client is blocked by a firewall.

If the client port is blocked by a firewall, a DOS window containing a command and the results is briefly displayed after the ping utility is run:
Command: netstat –ano | findstr SYN
Results: TCP | | | SYN_SENT | 2904
Sender port (Sender ID) 
Client port (Receive ID)
TCP status
SYN_SENT is the typical indicator for the existence of a firewall on the client side blocking the client port.
Start ID for the connection to the client.

The client cannot recognize the backup server name.

The failure of the client to recognize the backup server name is displayed in the test window after running the ping probe.

Return to Top
seconds ago
a minute ago
minutes ago
an hour ago
hours ago
a day ago
days ago
Invalid characters found