Restore Backups for Aternity 12.2

If Aternity is unavailable, the speed of recovery depends on the type of high availability deployment:

Deployment Type of recovery
Single site (cold recovery)

If you backup and deploy high availability servers on a single site, you can restore Aternity within several hours.
Standby site (hot recovery)

If you deployed a standby site for hot recovery, you can expect to recover from a disaster within a few minutes.
Tip

There is a separate article on high availability and backing up.

Before you begin

You must already have a cloned database, as detailed in the Aternity backup strategy.

If you also need to restore the Aternity Management Server, you must first recover the disk image which you backed up after the last upgrade, as detailed in the Aternity backup strategy.

Procedure

  1. Step 1 Use your live backup tool for the Oracle Database Server to convert the cloned server into the primary server.
    Clone the Aternity Oracle Database Server
  2. Step 2 To perform a hot recovery from to a standby site to start working in minutes:
    Deploy a standby site for hot recovery
    1. a Reroute the monitored devices to the load balancer of the Aggregation Servers on the standby site.
    2. b Update the DNS of the URL for accessing Aternity to the Aternity Management Server on the standby site.
  3. Step 3 To perform a cold (offline) recovery from a single-site deployment:
    Deploy high availability on a single site for offline recovery
    1. a On the computer which runs the Aternity Management Server, launch the Configuration Tool from the Start menu, by right-clicking it and selecting Run as administrator to start.

      When you create any Aternity server it adds the Configuration Tool.

    2. b Select Database Configuration to change the address of the Oracle Database Server.
      Configure the database address
    3. c Configure the Management Server to use the address of the clone server as the newOracle Database Server.
    4. d Restart the Management Server.
  4. Step 4 If you backed up the dashboards which users saved, you can restore them.
    1. a Access the Aternity Dashboard Server.
    2. b In a command prompt, navigate to the setup destination directory of the Dashboard Gateway.
    3. c Enter the following command: 
      TableauUtility.cmd restoreSaved -inputFile pathname_of_backup_zip -site Tableau_site
      Restore a backed up package of saved dashboards
      Field Description

      -inputFile

      Enter the full pathname and file to the package containing the dashboards you backed up earlier.

      -site

      Enter the name of the Tableau site. You can find this in Aternity settings, by selecting the Gear Icon > Settings > Advanced Settings > tableau > site.
  5. Step 5 After you backup Vertica database, you can restore it.
    Important

    Remember to create pwdfile each time you run backup or restore commands and to DELETE it after that.

    Restore data from the latest backup file of Aternity Vertica Database Server or return to a specific point in time (to any of the two saved backups).

    Run this command as DBADMIN user.

    1. a Get the list of all backup files by running the following command: 
      $ /opt/vertica/bin/vbr.py -t listbackup --config-file /home/dbadmin/backup_restore_full_local.ini
      For example, you get two backup snapshots:
      • backup_snapshot_20190328_125703
      • backup_snapshot_20190328_125404
    2. b Stop Vertica database using admintools. 
      admintools -t stop_db -F -d <DB_NAME> -p '<DBA_USER_PSWD>'
    3. c Execute the following task to restore the latest backup snapshot. 
      $ /opt/vertica/bin/vbr.py -t restore --config-file /home/dbadmin/backup_restore_full_local.ini
    4. d Alternatively, execute the following task to restore a specific backup snapshot (use its name in the command): $ /opt/vertica/bin/vbr.py -t restore --archive 20190328_125703 --config-file /home/dbadmin/backup_restore_full_local.ini