Restoring the database from remote backup

Last Updated : Apr 26, 2021 |
Prolog information
You can restore a full backup of the database from the remote server using the Avaya Analytics™ Administration script.
Note:
Restoring backup is only supported when the backup is taken on the same Avaya Analytics™ release as a target for the restore. For example, a backup taken on Avaya Analytics™ 4.1.1.0 can only be restored on the Avaya Analytics™ 4.1.1.0.
Before you begin
Other:
You must restore backups only during maintenance window periods. To prevent data loss, ensure that no other activities occur in the database during the backup process.
Do not restore a database backup of the previous Avaya Analytics™ release version.
  • Stop all events coming to the Avaya Analytics™ database from Avaya Oceana® and stop interval data being written to the Avaya Analytics™ database. Run the following commands:
    • To stop data flow to the cluster, run the following command:
      kubectl scale --replicas=0 deployment orca-ref-input-adaptor
    • To stop interval data, run the following command:
      kubectl scale --replicas=0 deployment orca-interval-controller
  • Check your backup file permissions.
  1. Log in to the Cluster Control Manager (CCM) console as the customer user.
  2. Switch to being the root user by entering the command su.
  3. To run the Analytics Administration script, use the following command:
    ADDITIONAL INFORMATION:
    ccm release orca analytics
  4. Select Database by pressing the corresponding number.
  5. To select the Database Restore option, enter the corresponding number.
  6. To select the Restore from remote backup option, enter the corresponding number.
  7. In the Proceed to restore a remote backup field, type y.
    ADDITIONAL INFORMATION:
    Entering n cancels the operation.
  8. The details of the remote server is displayed. In Confirm server details [y/n] field, type y.
  9. In the Enter the name of the backup file on the Remote server field, enter the backup file that you need to restore.
    ADDITIONAL INFORMATION:
    The file extension should be in .gz format, and the file naming convention is full_backup_yyyy-mm-dd_hh-mm.bkp.gz.
    STEP RESULT:
    The script restores the latest database backup from the remote server to the desired location on CCM.
  10. Return to the previous page by entering b.
  11. Quit the current page by entering q.
  12. Return to the main menu by entering m.
Next steps
After the database backup is restored, enable the events coming to the Avaya Analytics™ database from Avaya Oceana® using the following commands:
  • To start data flow to the cluster, run the following command:
    kubectl scale --replicas=2 deployment orca-ref-input-adaptor
  • To start interval data, run the following command:
    kubectl scale --replicas=2 deployment orca-interval-controller
    Note:
    For non-HA systems, the replica count is 1 instead of 2.