Home › Technical articles

Đọc bằng tiếng Việt

AVEVA Galaxy backup and restore: the .cab file, .aaPKG and CSV exports, InTouch applications and Historian

TDL Industrial Automation · Last updated:

From AVEVA's System Platform 2026 documentation: backing up a Galaxy to a .cab with the Galaxy Database Manager, restoring into an existing or a new Galaxy, version and migration rules, why .aaPKG and CSV exports are not backups, and backing up standalone InTouch applications, Historian, driver configuration sets and virtual machines.

An AVEVA System Platform system is not backed up with one file. The Galaxy goes into a .cab made with the Galaxy Database Manager, a standalone InTouch HMI application is a folder, AVEVA Historian is backed up through SQL Server and its history blocks, and each communication driver keeps configuration sets. This article follows AVEVA's System Platform 2026 documentation: what each node needs, how a restore works and which version rules apply. Standalone and managed InTouch applications are explained in InTouch HMI or System Platform.

What to back up on each System Platform nodeFive rows, one per node type. Galaxy Repository: the Galaxy backup .cab made with the Galaxy Database Manager in the OCMC, holding all Galaxy information including security; managed InTouch applications sit in the Galaxy file repository; .aaPKG or CSV files are extra exports, not backups. Standalone InTouch node: copy the application folder, keep a DBDump CSV and an Export as Template .aapkg. Historian node: SQL Server backups of Runtime, master and msdb at least weekly, history blocks with Windows Backup or a VSS-aware tool, a configuration text file from aahDBDump.exe. Driver node: archive the configuration set while the driver is deactivated. Virtual machines: VM-level backups with the VM shut down, stored off the host; snapshots do not replace backups. Based on AVEVA System Platform 2026 documentation.What to back up on each System Platform nodeGalaxy RepositoryGalaxy DatabaseManager (OCMC)Galaxy backup .cab: all Galaxy information, security includedmanaged InTouch applications sit in the Galaxy file repository.aaPKG or CSV exports are extra copies, not backupsStandalone InTouchApplication Managercopy the whole application folderTagname Dictionary CSV with DBDump.aapkg of the graphics with Export as TemplateHistorianSQL Server and storage foldersRuntime, master, msdb: SQL Server backups, at least weeklyhistory blocks: Windows Backup or a VSS-aware toolconfiguration text file from aahDBDump.exeDriver nodeOI Server Managerarchive the configuration set while the driver is deactivatedVirtual machinesany nodeVM-level backup with the VM shut down, stored off the hostsnapshots do not replace backupsBased on AVEVA, System Platform 2026, Application Server 2026, InTouch HMI 2026, Historian 2026 andCommunication Drivers Pack 2026 documentation (read 15 November 2026). Figure: drawn by TDL.
Figure 1: What to back up on each System Platform node. On a phone, swipe sideways to see the whole figure.

1. The Galaxy backup (.cab)

The Galaxy Database Manager is installed on every Galaxy Repository (GR) node and opens from the Operations Control Management Console (OCMC). It backs each Galaxy up to a .cab file, which can restore a corrupted Galaxy or create a copy of it on another computer, on the local or a remote node.

In 2026 the .cab records the node that made the backup and carries a CSV listing every node and service configured for the Galaxy, which the restore uses to recreate them. Galaxy pairing information is not included.

AVEVA's best practice is to back up with the Galaxy Database Manager: that backup holds all Galaxy information, security included, while an export of objects holds only the object structure and template toolsets. AVEVA also asks for a Galaxy backup before every upgrade, and a deleted Galaxy comes back only from a backup.

2. Restoring: into an existing Galaxy or as a new one

A .cab can be restored in two ways:

  • Into an existing Galaxy. The restore is aborted if clients are connected or a platform is deployed. The service nodes and instances of the existing Galaxy are replaced by those in the .cab, and the GR node of the backup replaces the target's GR node; the Galaxy keeps its name.
  • As a new Galaxy. In the Galaxy Database Manager you pick the .cab and give a Galaxy name; the result is a new Galaxy.

To rename a Galaxy, AVEVA uses another route: undeploy and back it up, place the .cab in the BackupGalaxies folder under Program Files (x86)\ArchestrA\Framework\Bin, and create a new Galaxy from it as a template, not a new Galaxy followed by a restore.

A Galaxy name has up to 32 characters (letters, digits, _, $, #), starts with a letter and has no spaces; the GR computer and domain names should use only English letters and digits.

3. A new GR node and the version rules

A Galaxy can only be created on a computer with the Bootstrap and Galaxy Repository installed, TCP/IP enabled on SQL Server and a valid development licence active before the IDE opens (see AVEVA licensing). A Galaxy created with an older Application Server may need a different SQL Server permission level, set with aaConfigSQL.

The version rules AVEVA gives for System Platform 2026:

Case What the 2026 documentation says
Upgrade in place direct from System Platform 2020 R2 SP1 or later; not from 2020 R2 CR1, 2020 R2 CR2 or Enterprise 2023; 2023 R2 SP2 cannot be upgraded to 2026
Galaxy migration supported from Application Server 4.5 onward, including System Platform 2012 and later
How it migrates when the current IDE connects to an older Galaxy; the GR node must already be upgraded and all connections to the Galaxy database closed
Very large Galaxies migration can fail when the database transaction log reaches its size limit; AVEVA describes lifting the limit for the migration and restoring it afterwards

The upgrade order is covered in Upgrading InTouch and System Platform troubleshooting.

4. Export and import: .aaPKG and CSV are not backups

File What it holds What it leaves out
Galaxy backup .cab all Galaxy information, including security Galaxy pairing information
All objects .aaPKG templates, instances, graphics, faceplates, libraries and their configuration deployment, installed software, runtime and historical data
Instances as CSV unlocked attributes writable at configuration time, one column each script libraries, non-text attributes, I/O auto-assignment

On import, an object with the same tagname and codebase can be skipped, overwritten only if the imported configuration version is higher (the default), or always overwritten. Objects whose security group, area or host does not exist go to the Default security group, the Unassigned Area or the Unassigned Host. Upload runtime changes before importing a new version of a base template with deployed instances.

AVEVA intends the Blank Galaxy template mainly for recreating a damaged Galaxy: create it, then import objects from .aaPKG files. AVEVA's pages differ on editing the CSV: the export page allows Microsoft Excel, the Galaxy dump page does not recommend it, and the import page warns that an Excel comment line can create an unintended object. From 2026, graphics can be exported as XML for storage in Git.

5. Standalone and managed InTouch applications

A standalone InTouch application is a set of files in a folder. AVEVA says it can be copied from one node to another and found with Find Applications in the Application Manager, without import or export. Single window files are different: moving them other than by WindowMaker's import and export can corrupt the Tagname Dictionary.

Two exports are useful next to the folder copy:

  • DBDump writes the Tagname Dictionary to CSV and DBLoad reads it back, with WindowMaker stopped and the application converted to the current version; from a command prompt, for example DBDump C:\MyInTouchApps\App001,C:\TagDumps\App001.csv,1,1,0.
  • Export as Template writes an .aapkg with the graphic content (symbols, client controls, script library, language, styles) that can create new standalone or managed applications.

A managed application is stored in the Galaxy file repository on the GR node, one folder for the checked-in and one for the checked-out version. Its tags export from the IDE with Selected as CSV, interchangeable with standalone DBDump files. A published application cannot be imported into a Galaxy again. Applications from InTouch 7.11 P07 or later migrate to InTouch HMI 2026.

6. AVEVA Historian: SQL Server and history blocks

The Historian's Runtime database is a SQL Server database holding configuration such as tag and I/O Server definitions, not plant data. Plant data sits in history blocks, folders one day long by default.

  • Runtime database. AVEVA recommends backing up all Historian and SQL databases before any change and at least once a week, automated in SQL Server Management Studio, with master and msdb on the same schedule (the 2026 page writes "primary" for master). A restore overwrites everything saved since that backup.
  • History blocks. Back them up to long-term media with Windows Backup or another tool; the current block only with a VSS-aware tool. VSS-aware backups run while the Historian keeps running, but it must be shut down before blocks are restored, and an alternate storage location on a network share is not covered.
  • Configuration. The Historian Database Export/Import Utility (aahDBDump.exe) writes tags, IDASs, I/O Servers, topics and storage locations to a text file for the same or another Historian.

Faults on a running Historian: Historian troubleshooting.

7. Driver nodes, virtual machines and scheduling

A Communication Driver configuration set holds the global parameters, channels, devices, device groups and items, and is archived while the driver is deactivated. The 2026 release notes list a known issue: an upgrade from 2023 R2 SP1 resets drivers to the default set; the fix is Use Another Configuration Set. Driver details: AVEVA ABCIP driver.

For virtual machines, System Platform 2026 recommends VM-level backups for long-term archive, with the VM shut down, stored off the host or off site. Checkpoints and snapshots should be made with the VM shut down, because AppEngines hold transient data at runtime; AVEVA advises one per VM and says they do not replace backups.

On scheduling, only the Historian pages give a rate. For the Galaxy, the 2026 page asks for application backups as needed, while the 2023 page advised scheduling them with AVEVA's built-in tools. The GRAccess toolkit, for programs that automate Galaxy configuration, has a Backup method that writes a .cab; given a folder name, it first deletes that folder's contents.

What we check first

This is TDL's practice, not an AVEVA requirement.

  • The version and patch level of every node, the GR node name and the Galaxy names.
  • The date of the last .cab, and whether it restores: we restore it as a new Galaxy on a test GR node, not into the running one.
  • Every standalone InTouch folder on every node, with a DBDump CSV next to it.
  • The SQL Server backup jobs on the Historian, their last successful run, and how the history blocks are copied.
  • Archived configuration sets on the driver nodes, and whether VM "backups" are really snapshots.
  • That copies are kept off the node they came from.

How TDL approaches it

TDL Industrial Automation is a System Integrator member of the AVEVA Partner Ecosystem. At the SEHC facility and power monitoring systems, built on AVEVA System Platform, we maintain the servers on a six- or twelve-month plan that includes backups with restore tests. At P&G Vietnam Dong An, where the systems include AVEVA System Platform and InTouch, we keep controller, HMI and SCADA backups for the plant. How we set up backups and version history: PLC and HMI backup and version control.

Frequently asked questions

Is an .aaPKG export a full Galaxy backup?

No. AVEVA states that an .aaPKG is not a complete Galaxy backup: importing it does not deploy objects, install software or bring back runtime or historical data. The Galaxy Database Manager backup (.cab) holds all Galaxy information, including security.

Can a Galaxy backup be restored on a new computer?

Yes. AVEVA says a backup can create a copy of a Galaxy on another computer. The new computer needs the Bootstrap and Galaxy Repository software and SQL Server with TCP/IP enabled; in the Galaxy Database Manager you pick the .cab and give the new Galaxy a name.

How do I back up a standalone InTouch application?

Copy its application folder: AVEVA says standalone applications can be copied between nodes without import or export. Keep a DBDump CSV of the Tagname Dictionary as well, and never move single window files outside WindowMaker's import and export.

How often should the AVEVA Historian database be backed up?

AVEVA recommends at least once a week and before any change, with automatic backups in SQL Server Management Studio, and the master and msdb databases on the same schedule. History blocks are backed up separately with Windows Backup or another tool.

Can a Galaxy from an old System Platform version be opened in 2026?

AVEVA supports Galaxy migration from Application Server 4.5 onward. The migration starts when the current IDE connects to the older Galaxy, after the GR node has been upgraded. An in-place upgrade to 2026 is direct only from System Platform 2020 R2 SP1 or later.

Sources

Read 15 November 2026. This article paraphrases the sources and does not quote them; read the original documents before designing or working on a system.

Related services:
AVEVA (Wonderware) AVEVA InTouch (Wonderware) support and upgrades