Database Restore

This section allows you to restore the configuration settings of AD360 and all the integrated components. You can restore the built-in or external PostgreSQL database and MS SQL databases configured in the product.

You can view the following information on the Database Restore page.

  1. Component name
  2. Number of backups available for each component
  3. Last backup that was restored
  4. Size of the previous successful backup
  5. Last time a backup was restored
  6. Restoration status

To restore a database from the available backups, perform the following steps.

Caution: Make sure the version of the backed up and target PostgreSQL database are the same. A mismatch between the versions may cause the database to crash. If the database versions are different, please use the database migration feature.

  1. Navigate to Admin tab → General Settings → Database Settings → Database Restore.
  2. To restore the backup of a component, click on the number under the Backups Available column.
  3. In the page that appears, select the type of repository where the backup is stored from the available options:
    1. Local: Provide the path where the backups are stored.
    2. Shared: Provide the shared path to the repository where the backups are stored. If the repository requires authentication to read stored data, enable the Authentication Required checkbox and provide the credentials of a user who can read the files in the repository.
  4. The list of backups available backups for the particular component are displayed. You can also search for a particular backup file using the icon.
  5. Click the Restore button against the backup file you wish to restore.
  6. Click the Restore button in the confirmation pop-up.
  7. The component will shut down during the restoration process and will restart once the restoration is complete. If you used a password different from the default or the current encryption password, provide the encryption password which was in use at the time the backup was taken.
  8. You can check the status of the restoration process in the Database Restore screen under the Restoration Status column.

Troubleshooting steps

The database restoration could have failed due to any of the following reasons.

Cause 1: The restoration could have failed because the backup file was corrupted. A backup file could get corrupted due to the following reasons:

  • There was a failure during the database backup process and the backup file which was being generated is incomplete.
  • The backup file was edited manually after it was generated successfully.


  • Ensure the backup file is not corrupted.
    • If the backup was taken as a result of the scheduler or via the product user interface, navigate to Admin tab → General Settings → Database Settings → Database Backup and verify the status of the backup to ensure the backup operation was completed without any issues.
    • If the backup was triggered manually by executing the backupDB.bat file, the status of the backup would have been displayed after the completion of the backup process.
  • If you had edited the backup file manually, use a backup file that has not been modified for the restoration process.

Cause 2: The restoration could have failed due to a database failure or network connection failure during the restoration process


Ensure the database is in optimal working condition and the connection between the database and the AD360 server is stable.

Cause 3: Insufficient privileges to perform the restoration.

Resolution: Ensure the user account used to perform the restore operation has permission to read and write data on the database that is to be restored.

Cause 4: There was an interruption during the restoration.

Resolution: Avoid performing the following activities when the restoration is in progress:

  • Access or modify the database that is being restored.
  • Access the backup file.

Cause 5: Insufficient disk space while performing the restoration operation

Resolution: Ensure there is sufficient disk space where the database is located.

If you are unable to perform the database restoration, contact