Choose your Backup Strategy for Aternity on-premise

The strategy of backing up Aternity on-premise servers should focus 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.

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

Aternity servers for backup
Component name Contains Backup Frequency

Aternity 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.

Important

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.

The Agent reports data to Aternity once every minute. If its status becomes disconnected and it cannot send data, by default it locally stores up to the last 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.

N/A

Aternity Dashboard Server

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

N/A

Aternity Aggregation Server

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

N/A