Record Protection—11​.10 (c)

"(c) Protection of records to enable their accurate and ready retrieval throughout the records retention period."

Protection of records includes performing scheduled backups of data. Typically backups should made and maintained for InTouch applications, System Platform Galaxy, Historian history blocks and SQL Server tables, WWALMDB and A2ALMDB alarm and event databases and any other system databases.

InTouch Applications Backup

In architectures where InTouch applications are based on tags defined in the tag database (as opposed to using a plant model in System Platform), InTouch applications can be either Stand-Alone or Managed. Backups for Stand-Alone InTouch applications must be made and maintained manually by selecting and copying the application directory.

Managed InTouch applications are maintained using the System Platform Integrated Development Environment (IDE) if it is installed on the same computer as the InTouch HMI. Unlike stand-alone InTouch applications that are managed entirely by Application Manager, managed applications are more integrated into the System Platform environment. Managed InTouch applications appear in the Application Manager as "Managed" and can be edited only by starting WindowMaker from within the IDE. Backups for managed InTouch applications are maintained in the System Platform Galaxy and are backed up with all of the other Application Server objects.

Managed InTouch applications are preferred where they will be deployed into regulated environments. A Managed InTouch application uses the InTouchViewApp object to manage the synchronization and delivery of files required by the associated InTouch application. The advantages of this managed application choice are all changes are recorded and comments are allowed when changes are made. For more information, see "Managed InTouch Applications" in the InTouch HMI online help.

An AVEVA OMI ViewApp uses a ViewApp object to manage the synchronization and delivery of files required to run a ViewApp. As with a managed application, all ViewApp events are records.

InTouch includes an application version feature - a system tag that increments each time something is changed in the InTouch application configuration. This tag is called $ApplicationVersion. $ApplicationVersion can be a valuable asset in the validation process because it can be recorded in the validation protocols to ensure validated application has not been changed or altered.

Historian Backup

Historian consists of two entities requiring backup: the SQL Server runtime database, and history blocks. Each of these entities has a separate backup procedure. For runtime database and history block backups see, "Managing the AVEVA Historian Runtime Database" and "Managing Partitions and History Blocks" under "Managing Data Storage" in the AVEVA Historian Help, AVEVA Historian Administration Guide. .

Redundant Historian

Historian may be configured to have a symmetrical "partner" Historian that can be used as a backup if the primary, or main, historian is not available. This is known as a "redundant historian" setup. No control configuration is required to take advantage of a redundant historian.

When the primary historian is unavailable, the Alarm Control automatically switches over to the configured partner historian. The control remains connected to the partner historian, even when the primary historian becomes available again. The Alarm Control switches back to an available primary historian if it fails to connect to the partner or during a new attempt to connect to the primary historian, such as when restarting Trend.

Alarm and Event Backup

Management of the alarm database is performed using two InTouch utilities. The Alarm DB Purge-Archive utility is used to remove records from the database permanently or archive them to files. If the database becomes corrupt, use the Alarm DB Restore utility to restore archived records. For instructions on using these utilities see, "Maintaining the Alarm Database" in the AVEVA InTouch HMI online help. .

System Platform Galaxy Backup

The configuration model of a System Platform application is stored in the Galaxy Repository, which is an MS SQL Server database. The backup function of the Galaxy Database Manager archives all files and configuration data required to recreate the selected Galaxy in an empty Galaxy Repository. For procedures on backing up a Galaxy see, "Using the Galaxy Database Manager", "Backing Up a Galaxy", in the the AVEVA System Platform IDE online help.

System Databases Backup

For backup of data stored in other system databases, in your case Microsoft SQL Server, see your Microsoft Documentation.