Choose your Backup Strategy for Aternity 10

The strategy of backing up Aternity on-premise servers focuses on keeping only the dynamic data which is valuable to you and hard to replace. For most Aternity servers, their data is easily repopulated after a restore, and therefore do not need a backup.


There is a separate article on high availability.

For details of restoring from backups, see Restore Backups for Aternity 10 (Disaster Recovery).

We recommend backing up only the following Aternity on-premise servers:

Aternity servers for backup
Component name Contains Backup Frequency

Aternity Oracle Database Server

  • Historical performance data from (at least) the past year.

  • Local usernames and passwords (encrypted).

  • User privileges, roles, and preferences.

  • System settings.

Perform incremental backup daily plus a full backup every week.


You must enable the archive log by switching on the Oracle FORCE_LOGGING setting.

Aternity Management Server

  • Several crucial static files required for database disaster recovery, which must be backed up.

  • Aternity quickly repopulates the performance baselines after a restore.

After every Aternity upgrade, backup the disk image.

Aternity Dashboard Server

If users saved their own custom dashboards, you can create a backup (see below).

Create a scheduled execution of the command line regularly (daily or weekly according to your requirement).

The Aternity Agent reports data to Aternity once every minute. If its status becomes disconnected and it cannot send data after trying for five minutes, it locally stores up to 50 minutes of retention data in offline mode, and then sends it when it renews its connection.

The following servers are NOT recommended for backup:

Component name Contains Backup Frequency

Aternity Data Warehouse Server

Detailed recent performance data (up to seven days) is quickly repopulated after restore.

No need

Aternity Dashboard Server

Programs and settings to display the data in dashboards, fully restored with a standard installation.

No need

Aternity Aggregation Server

Programs and settings to condense data for passing on to other Aternity servers, fully restored with a standard installation.

No need

Aternity Vertica Database Server, Aternity ETL Server

Stores a subset of the data in Aternity Oracle Database Server, therefore does not need its own backup.

No need

Create Backup of Saved Dashboards

You can save and share a customized dashboard, to revisit it any time in the My Dashboards menu. To save, share and subscribe, you first view a dashboard, customize it, then save it, and finally subscribe someone to regular email updates. (Learn more)

Subscribe and share a dashboard

To create a backup of saved dashboards, create a scheduled running of a command line utility on the Dashboard Server. Navigate to the setup destination directory of the Dashboard Gateway.

Enter the following command:

TableauUtility.cmd backupSaved -outputFolder target_dir -site Tableau_site
Backup saved dashboards with a scheduled command line
Field Description


Enter the target directory to place the backup package (zip file) containing the saved dashboards. For example, c:\temp.


Enter the name of the Tableau site. You can find this in Aternity settings, by selecting the Gear Icon > Settings > Advanced Settings > tableau > site.