Archiving changes and use case issues described here do not apply to a AX-3.8 system, but do apply to a system running an
update release (AX-3.7u1 or later, AX-3.6u4 or later, AX-3.5u4 or later). See Station archive portablility improvements in AX-3.8.
Historically, NiagaraAX users have made archives of stations using two basic methods:
-
Using the Station Copier platform tool
This can be used to both save a station to the Workbench PC (including most folders and files under that station’s file space) as well as install (copy) that station to a remote host, typically a JACE.
Such a station copy includes a station folder with a
config.bogfile, and optionally other files. -
Using a station’s BackupService, which provides a Backup Manager view, plus a right-click “Backup Station” command on the station (FoxSession) as it appears in the Workbench Nav tree. Or, a similar backup is available from a Supervisor’s Provisioning extension, or directly from a platform connection to the station’s host. Collectively, these methods are considered “BackupService” tools.
All such station backups are saved as a single backup “
.dist” (distribution) file, which can be restored by using the platform Distribution File Installer tool.
As explained in the section Portability of stored passwords, when running an update release of NiagaraAX, the difference is now a config.bog from a Station Copier save contains some passwords that are not portable (do not work if copied to another host other than the original one).
And although a backup .dist file does contain all portable passwords, in any “replicated station” scenario (if using an update release) this is often undesirable, as a security risk—as all hosts then use identical encryption key files.
Consider these two use cases for archiving and reinstalling a station: