Backup and restore AIP data

Owned by Tolga Tunca
Last updated: Apr 17, 2024 by Derya Özdemir
2 min read

This page is about Assets & Inventory Plugin for Jira DC. Using Cloud? Click here.

This guide details the process for backing up and restoring data associated with the Assets and Inventory (AIP) plugin for Jira.

Suggested Backup & Restore

The data generated by AIP is stored within the Jira database. This means you don't need a separate backup for your AIP data. It's automatically included whenever you perform a standard Jira backup or restore, or during a Jira upgrade. This ensures your AIP data remains consistent and unharmed alongside your standard Jira issues and asset-related objects.

Following a Jira upgrade or restore:

  • Assets are typically indexed automatically after a Jira upgrade or restoration, unless disabled by AIP settings.

  • If you encounter unusual asset search results, initiate an AIP re-indexing process (refer to the Indexing documentation for instructions).

Manual Backup & Restore

If a separate backup of AIP data is required, separate from the standard Jira database backup, follow the detailed steps below.

  • Export and import each database object beginning with the identifier AO_23ADAF in the specified order as listed at the end of the document.

    • Sequences

    • Tables

  • Order of tables is important while restoring, you may get errors if the order is not correct due to foreign key constraints.

  • It's important to be aware that various database versions, like MySQL, might not support sequences.

  • Following any manual modifications to the database, initiate an AIP re-indexing process by referring to these instructions.

Important:

The IDs of the database objects maintain the relationship between AIP objects and Jira integration. Modifying these IDs can result in data loss. CSV export and import will change IDs, so do not use them as backup/restore.

1. Sequences

AO_23ADAF_AIP_ASSET_FILTER_FAV_ID_seq AO_23ADAF_AIP_ASSET_FILTER_ID_seq AO_23ADAF_AIP_ASSET_LINK_TYPE_ID_seq AO_23ADAF_AIP_ASSET_TYPE_MAP_ID_seq AO_23ADAF_AIP_ASSET_UNIQUENESS_ID_seq AO_23ADAF_AIP_DB_SYNC_ID_seq AO_23ADAF_AIP_DB_SYNC_JOB_LOG_ID_seq AO_23ADAF_AIP_DB_SYNC_LOG_ID_seq AO_23ADAF_AIP_FIELD_MAPPING_ID_seq AO_23ADAF_AIP_FILTER_SUBS_ID_seq AO_23ADAF_AIP_JOB_STAT_DTL_ID_seq AO_23ADAF_AIP_JOB_STATUS_ID_seq AO_23ADAF_AIP_LINKED_ASSET_ID_seq AO_23ADAF_AIP_LOCATION_ID_seq AO_23ADAF_AIP_OBJECT_SCHEMA_ID_seq AO_23ADAF_AIP_PERM_MAPPING_ID_seq AO_23ADAF_AIP_PERMISS_SCHEME_ID_seq AO_23ADAF_AIP_SETTING_ID_seq AO_23ADAF_AIP_STATUS_ID_seq AO_23ADAF_AIP_SYS_FLD_MAP_ID_seq AO_23ADAF_AIP_SYS_FLD_SCHM_ID_seq AO_23ADAF_AIP_TEMP_CATEGORY_ID_seq AO_23ADAF_AIP_TEMPLATE_ID_seq AO_23ADAF_JIP_ACCESS_ID_seq AO_23ADAF_JIP_ATTRIBUTE_ID_seq AO_23ADAF_JIP_ATTRIBUTE_VALUE_ID_seq AO_23ADAF_JIP_FORM_ATTRIBUTE_ID_seq AO_23ADAF_JIP_FORM_ID_seq AO_23ADAF_JIP_HISTORY_ID_seq AO_23ADAF_JIP_INVENTORY_ID_seq AO_23ADAF_JIP_INVENTORY_ITEM_ID_seq AO_23ADAF_JIP_MIGRATION_LOG_ID_seq AO_23ADAF_JIP_PARAMETER_ID_seq AO_23ADAF_JIP_USER_PREF_LONG_ID_seq AO_23ADAF_JIP_USER_PREFERENCE_ID_seq AO_23ADAF_VENDOR_LICENSE_ID_seq

2. Tables

AO_23ADAF_AIP_ASSET_FILTER AO_23ADAF_AIP_ASSET_FILTER_FAV AO_23ADAF_AIP_ASSET_LINK_TYPE AO_23ADAF_AIP_ASSET_UNIQUENESS AO_23ADAF_AIP_DB_SYNC AO_23ADAF_AIP_DB_SYNC_JOB_LOG AO_23ADAF_AIP_DB_SYNC_LOG AO_23ADAF_AIP_ASSET_TYPE_MAP AO_23ADAF_AIP_FIELD_MAPPING AO_23ADAF_AIP_FILTER_SUBS AO_23ADAF_AIP_JOB_STAT_DTL AO_23ADAF_AIP_JOB_STATUS AO_23ADAF_AIP_LOCATION AO_23ADAF_AIP_OBJECT_SCHEMA AO_23ADAF_AIP_PERMISS_SCHEME AO_23ADAF_AIP_PERM_MAPPING AO_23ADAF_AIP_SETTING AO_23ADAF_AIP_STATUS AO_23ADAF_AIP_SYS_FLD_SCHM AO_23ADAF_AIP_SYS_FLD_MAP AO_23ADAF_AIP_TEMP_CATEGORY AO_23ADAF_AIP_TEMPLATE AO_23ADAF_JIP_ACCESS AO_23ADAF_JIP_ATTRIBUTE AO_23ADAF_JIP_ATTRIBUTE_VALUE AO_23ADAF_JIP_FORM AO_23ADAF_JIP_FORM_ATTRIBUTE AO_23ADAF_JIP_HISTORY AO_23ADAF_JIP_INVENTORY AO_23ADAF_JIP_INVENTORY_ITEM AO_23ADAF_JIP_MIGRATION_LOG AO_23ADAF_JIP_PARAMETER AO_23ADAF_JIP_USER_PREF_LONG AO_23ADAF_JIP_USER_PREFERENCE AO_23ADAF_VENDOR_LICENSE AO_23ADAF_AIP_LINKED_ASSET

Table’s Foreign Key Diagram

The following illustrates the foreign-key relationships among the tables. Not every table is linked by a foreign key relationship. When importing a table, it is crucial to import the parent table first. For instance, AO_23ADAF_AIP_OBJECT_SCHEMA must be imported before AO_23ADAF_JIP_FORM.

aip tables diagram.png