System components & architecture
System architecture
GitProtect system architecture is presented in the following diagram:
Components
GitProtect product as a platform consists of three main components: management service, worker, and storage.
Management system
The main component required to run GitProtect backup system is called GitProtect Management Service. It allows you to comprehensively manage your backups and related resources using Management Service console with a user-friendly and easy to navigate UI. In on-premise deployment model it can be installed on almost any computer with Windows and Linux operating systems or Docker environment (even popular NAS devices). When it comes to SaaS deployment model, the management service runs on provider's cloud infrastructure.
GitProtect Management Service is divided into separate modules, each of them dedicated to a different aspect of backup management:
Dashboard
DevOps
Plans
Storages
Tasks
Logs
Settings
Worker
The second main component is called GitProtect worker and is an application installed on end devices with Windows, Linux, or Mac operating systems. Worker performs all operations requested by the Management Service including data processing (i.e., encryption, compression), connecting to data storage, sending data directly to the storage, and restoring data.
Storage
The last component on the list is storage— GitProtect, as a multi-storage system, allows you to store your backup data in the cloud (GitProtect Cloud, AWS, and any S3 compatible public cloud), locally (NFS, SMB, iSCSI network shares, local disk resources), or in a hybrid environment.
Last updated