Backup as a Service

Niagara Cloud Backup as a Service (BaaS) provides easy, secure, and scalable backups of a device from the JACE station to Niagara Cloud.

Using either Workbench or a browser connection to the JACE station, you can configure automated backups by time or event triggers, or initiate a backup manually, as well as flag backups for data retention. You are able to view, download or delete your cloud backups, as well as add notes to new manually initiated backups.

Backup transmissions are streamed, so there are no block space requirements on the device. The streaming approach means that each segment of a backup is sent immediately and not saved anywhere on the device. The platform only needs to have enough space to hold that one segment, usually much smaller in size than an entire backup. 

By default, backups includes all of the same elements that are included in a local backup (config.bog file, station files, graphics, licenses, and certificates). Note that the alarm and history databases are excluded by default (as in the legacy local Backup Service) mainly because these files can be very large. Cloud backups can be configured for additional exclusions if desired.

 
NOTE: It is possible to remove the default exclusions of history and alarm databases should you wish to include them in your backups. For example, if preparing to migrate a station, you may wish to make a more complete backup that includes the history and alarm databases for that station. For details on how to do this, see cloudBackup_CloudBackupService.
 

In Niagara Cloud, a backup file is chunked, encrypted (in transit and at rest) and posted to the cloud. Once a backup is committed, it must be decrypted using the source station's system passphrase (the one in use at the time the backup was created). All backup files are encrypted so that the data is secure, and stored in Windows Azure in Microsoft’s Data Centers. The encryption means that your data is safe.

 
NOTE: The management of users with admin privileges and access to JACE embedded controllers configured with the CloudBackupService is the sole responsibility of the customer.
 

The backup service is geo-located which means that the CloudBackupService will connect to a “traffic manager” that will automatically route the station’s backup service to a cloud service that is closest to the site, to minimize the latency (i.e. delays) in the communication while uploading the backup. Storage servers are synced in the background.

The current storage limit for cloud backups is 1GB for JACE controllers, and 5GB for Supervisors, regardless of the number of backups. 

Should a hardware failure or corruption occur, any cloud backup (the last known good or historic) can be downloaded at any time (24x7x365) by authorized individuals from a secure cloud login. The backup can be downloaded in encrypted format (EDIST). Or, using the source station's system passphrase (in use at the time the backup was created), it can be downloaded in decrypted format (DIST).

If a backup is downloaded in encrypted format (EDIST), the Workbench File System provides a utility to decrypt the file using the source station's system passphrase (requires the passphrase in use at the time the backup was created).

Once decrypted the backup DIST file can then be installed on a new embedded controller, thereby minimizing disruption of operations.