Backup as a Service is compatible with
Always remove the local Backup Service when installing the Cloud Backup Service. The reason for this is that station operation depends upon interacting with a single backup service. The Cloud Backup Service provides all of the behavior of the local Backup Service, including local and provisioned backups, in addition to backing up to the Niagara Cloud. Leaving the local Backup Service in place when installing the Cloud Backup Service may cause confusion for users and yield unintended results when accessing and performing backups.
Your cloud backups are stored in the Microsoft Azure cloud platform, geo-located in the nearest Microsoft data center (either US east coast or US west coast). The data is encrypted at all times and only your authenticated users can see the data.
The data is encrypted end-to-end, which means in transit and at rest. This makes it impossible for anyone other than your authenticated users to view your data. The JACE is connected to the Internet but makes only outgoing connections. The controller will not accept incoming messages from the Internet.
In the
Set up time triggered cloud backups. Using the Trigger Mode dropdown list in the Cloud Backup Manager view you can schedule backups to occur periodically.
The unit must have internet connectivity in order to connect to
The cloud-related modules listed here require an additional 150k disk space on the controller:
The current storage limit for cloud backups is 1GB for JACE controllers, and 5GB for Supervisors, regardless of the number of backups.
Using the FIFO (First In First Out) file rotation method, when the storage limit is reached the first backup made is the first backup to be deleted. This automatically makes space for your most recent backups.