A Server receives (and stores) backup data from Clients.
The backed up data is stored in the machine which runs the Server – a PC can run server if you plan to store data on that PC.
A machine that has data it wants to back up has to run Client.
The Client backs up its data on to a machine running Server.
(anyone who purchases a paid license of is also a client )
Term used for the process where a backup server sends its backup data to a replication server to create a redundant copy of the backup data.
Replication Server :
A machine that receives replication data from a backup server. In case the backup server crashes, it can be restored from the replicated data in the replication server. A backup server can replicate to only one replication server. A replication server can accept replication from more than one backup servers.
The term specifies the deployment of in a cluster. A number of Servers [Backup & Replication] can be deployed to be run as a single entity and all storing and accessing the metadata in a centralized Database using ODBC. This will enable Server to scale to multiple clients to connect for backup/restore processes simultaneously.
Cluster Node :
This mentions one of the Server instances running inside the Cluster. They get registered to the Cluster configuration as an active node in the cluster at startup.
Server Lookup :
A client looking up to the Master Server in the cluster to determine whom to connect for backup and restore.
Web Console :
This is the browser based user interface from which the backup, restore and administration of servers and clients are done.
Since the user interface is browser based, any Client or Server can be configured and administered from any location.
Remote / Online Backups :
The same as client-server (see above), except that the ‘server’ is outside the clients’ network.
Web Services API :
The ability to access meta information via standard HTTP/HTTPS Requests from the Web Portal.