JIRA Documentation

JIRA 6.4.x
JIRA 6.0 Documentation
JIRA 5.2 Documentation
JIRA 5.1 Documentation
More...
 

 

Search the Knowledge Base and Documentation Spaces

You're visiting the JIRA Knowledge Base. Visit the JIRA Knowledge Base Home for an overview.

Skip to end of metadata
Go to start of metadata

For production use, it is strongly recommended to use native database-specific tools instead of the XML backup service. XML backups are not guaranteed to be consistent, as the database may be updated during the backup process. Inconsistent backups are created successfully without any warnings or error messages, but fail during the restore process. Database-native tools offer a much more consistent and reliable means of storing data.

These pages describe common problems with XML backups for those who must use them, but it is strongly recommended to use database-native tools instead as outlined in our backup documentation.

  • No labels
Page: 'ORA-01461 can bind a LONG value only for insert into a LONG column' Error Due to Oracle Database Definition Page: Problem while restoring the data for the null plugin Page: 'Timestamp Format Must Be yyyy-mm-dd' while Importing from an External System Page: Backing up JIRA Fails due to Quotes in the Path Page: Error while importing XML - 'NaN' is not a valid numeric or approximate numeric value Page: GenericEntityException 'NaN is not a valid numeric' when Importing an XML Backup Page: GenericEntityException when Restoring XML Backup on MySQL due to Packet Size Limitation Page: Restoring data process fails due to "com.atlassian.crowd.exception.DirectoryInstantiationException: java.lang.NullPointerException" Page: There was an error during import/export with <unknown plugin>:Could not import data Page: Unable to Restore Data Backup due to 'Out of range value for column' Page: XML Import fails due to Unable to find ActiveObjects plugin Page: Could not find entity for entityName: LinkEntity when restoring JIRA from a XML Backup Page: Cannot insert duplicate key row in object 'xxx.userhistoryitem' with unique index 'uh_type_user_entity' when restoring a XML backup Page: "Error importing data: java.lang.NullPointerException" during migration to JIRA 5.2.11 Page: Failed to restore with the following error "Error parsing export file: org.xml.sax.SAXParseException; lineNumber: 1; columnNumber: 1; Content is not allowed in prolog" Page: Unable to Restore XML Backup due to Could not find definition for entity name ApplicationUser Page: Restore into Oracle database fails to import into AO table Page: Unable to Restore XML Backup due to Invalid Byte Sequence for Encoding "UTF8": 0x00 Page: "Could not get unique fields for table" when creating a XML backup Page: XML restore fails with message "The processing instruction target matching "[xX][mM][lL]" is not allowed" Page: Foreign key constraint fails on fk_ao_60db71_boardadmins_rapid_view_id referencing ao_60db71_rapidview when restoring XML backup Page: Invalid Memory Alloc Request Size Page: JIRA Import Fails Due to Character Encoding Page: JIRA backup suddenly decreases in size compared to previous backups after JIRA is restarted Page: Could not find file at this location Error While Restoring Database from Backup XML Page: JIRA throws SQL Exception when trying to restore XML backup

6 Comments

  1. I want to take backup for
    1. Permission scheme
    2. Issue security scheme
    3. Issue type scheme
    4. Workflow scheme

    of particular Project and want to restore with new JIRA instance.

    Please let me know is it possible to take backup for these and restore with new JIRA instance automatically.

      1. Thanks Jermy

        These are to be set manually for new instance if am not wrong.

        1. Permission scheme
        2. Issue security scheme
        3. Issue type scheme
        4. Workflow scheme

        1. Basically that's correct, along with custom fields. It's described in Preparing your target JIRA instance.

          1. Is there any plan for future release to provide these functionality?

            1. You can already export and import workflows by using xml. For the other ones, see Creating a Feature Request.