At the heart of Protector is the Master; a software component installed on a dedicated server that acts as a central hub, communicating with users via a REST interface and web based UI. The Master monitors and controls the activity of a set of Clients; software components installed on servers in the protected environment. Normally, the Master does not actively take part in data protection data flows; Clients do this themselves according to rules distributed from the Master.
-
A Master that controls the UI and the actions of all other nodes on the environment.
Master nodes can coexist on the same network, allowing multiple Protector environments to coexist.
Passive standby master nodes can be installed on a Windows failover cluster so that the standby can be brought online in the event that the active master fails.Note: It is recommended that the Master server not be assigned any other roles. -
Multiple Clients that participate directly in data protection data flows, acting as sources of data to be protected (e.g. database servers) and destinations capable of receiving backup data (e.g. repositories).
Clients implement various different roles within a data flow and must be configured to perform these roles. This consists of ensuring the appropriate prerequisites are installed, and configuration via the UI.
Client nodes can be installed on application clusters such as Oracle RAC.
Each Client can only be authorized and controlled by one master.
The figure below shows a possible installation scenario where two completely independent Protector environments coexist on one network.