A backup file can be configured to contain the Sedona virtual machine (SVM), the app.sab and kits.scode, as well as all of the Sedona dependencies (kits, manifests, and par files). The latter is one of the major enhancements in Sedona Framework TXS 1.2. This added ability of the Niagara station backup to include Sedona Framework device files, ensures the presence of all of the files that your application requires to run if deployed on another device. In this sense, the backup tool provides a true “backup”. Once you have created a backup of a device, if the device fails you can quickly get operations running again by restoring the backup to a replacement device.
Three backup options are available:
Backup Sedona VM
This option backs-up the virtual machine.
This option is device-specific. If not supported by your device, selecting the option will cause the backup operation to fail.
Refer to your device documentation for information on backing up the virtual machine.
Backup app.sab and kits.scode
This option is selected by default. It provides a minimal backup containing the app.sab and kits.scode.
Backup Sedona dependencies (kits, manifests, pars)
This option includes all additional files needed for the Workbench or JACE to connect to and provision the device.
This option requires the backup of the app.sab and kits.scode as well.
When using the Backup and Restore operations, the save (backup) and source (restore) locations differ slightly depending on the method used to connect to the device. You can use either of the connection methods described here:
For a Sox session connection
When provisioning through Sedona Workbench or Niagara Workbench via a direct Sox connection (or through Niagara Workbench via a tunneled-Sox connection), the save/source location is:
local│file:!sedona/store/backups
You can make a “direct Sox connection” to a Sedona Device in either Niagara Workbench or Sedona Workbench by selecting -> . You can make a “tunneled Sox connection” through the JACE only in Niagara Workbench by right-clicking a Sedona Device in
an opened station and selecting (this requires the SoxTunnelService in the station’s Services folder).
You can change the save/source location only when provisioning through a Sox session connection (direct Sox or Sox-tunneled). In this case, you can use either of the controls on the right side of the dialog box to select another save/source location.
For a Fox connection to a JACE station
When provisioning a networked device via a Fox connection to a JACE station the save/source location is:
ip:<IpAddress>│fox:│file:^sedona/store/<SedonaNetwork_Name>/<SedonaDevice_Name>/backups
The terms “IpAddress”, “
SedonaNetwork_Name
” and “SedonaDevice_Name
” shown here are not fixed values, they are placeholders for the actual IP number of your JACE as well as whatever you have
named your Sedona Network and Sedona Device.
You cannot change the save/source location if you are provisioning via a networked device on the JACE station. The save/source location
is the /backups
folder in the dedicated file space for the connected device on the JACE. However, you can transfer files to this location
and manage files there by using the available controls at the far right side of the dialog box to open a Directory view of
the /backups
folder. For more details, refer to Niagara Users Guide.
For more details on using the Backup and Restore operations, refer to Common Tasks.
Copyright © 2000-2014 Tridium Inc. All rights reserved.