Using either
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.
In
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
Once decrypted the backup DIST file can then be installed on a new embedded controller, thereby minimizing disruption of operations.