Deployment on your Premises
There are 2 models of architecture for using FAB for your On Premises data (or in another Cloud provider). In both cases it’s required to make sure your agents can access FAB for initiation of the FAB configuration. The 2 models are described below, please also refer to the FAB Network flow reference for detail on the communication matrix to setup:
Using the FAB storage
FAB provides the possibility to protect your On-Premise data and to store it directly in built-in Flexible Engine dedicated object storage buckets.
The On-Prem agents contact directly the Central FAB infrastructure and a tunnel is built by the central FAB proxy to secure both control and data flows from the agent to FAB libraries in Flexible Engine.
The below diagram represents the flow for the FAB service, depending on your local architecture:
Using a local storage (Bring-Your-Own-Storage)
FAB also provides the possibility to protect your On-Premise / Cloud instances data by storing them onto local storage or to another cloud provider object storage.
The On-Prem agents contact directly the Central FAB infrastructure for control flows (required for configuration, backup and restore operations, while the data flow stays within your infrastructure, as managed by the FAB MediaAgent to deploy close to the Storage library.
The below diagram represents the flow for the FAB service using local storage, depending on your infrastructure:
