Skip to end of banner
Go to start of banner

Backup and Restore AIP data

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Next »

Suggested Backup & Restore

The data generated by the Assets and Inventory plugin is stored within the Jira database. There's no need for a separate backup of AIP data, as it is automatically included when you back up and restore the Jira database or perform a Jira upgrade. This seamless integration ensures that AIP data remains intact and consistent alongside the built-in Jira issues and asset-related objects.

Following a Jira upgrade or restoration, assets are automatically indexed unless disabled by AIP settings. If unusual asset search results are observed, initiate an AIP re-indexing process by following the instructions outlined in the AIP Re-indexing Guide.

Manual Backup & Restore

If you specifically wish to create a separate backup for AIP data other than the suggested method, you can follow the steps outlined below.

  • Export and import each database objects 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 the instructions provided at this link: AIP Re-indexing Guide.

Caution: 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.

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

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

  • No labels