Restoring data
System administration
- Finding your Server ID
- Increasing Jira application memory
- Using the database integrity checker
- Precompiling JSP pages
- Logging and profiling
- Backing up data
- Restoring data
- Search indexing
- Using robots.txt to hide from search engines
- Control anonymous user access
- Moderating user group activity with Safeguards
- Licensing your Jira applications
- Viewing your system information
- Monitor application performance
- Monitoring database connection usage
- Monitor your instance with Jira diagnostics plugin
- Viewing Jira application instrumentation statistics
- Generating a thread dump
- Finding your Jira application Support Entitlement Number (SEN)
- Auditing in Jira
- Monitor security threats
- Data pipeline
- Important directories and files
- Integrating Jira applications with a Web server
- Securing Jira applications with Apache HTTP Server
- Changing Jira application TCP ports
- Connecting to SSL services
- Running Jira applications over SSL or HTTPS
- Configuring security in the external environment
- Data collection policy
- Jira Admin Helper
- Raising support requests as an administrator
- Start and Stop Jira applications
- Managing LexoRank
- Jira cluster monitoring
- Scheduler administration
- Secured secrets by default
On this page
In this section
Related content
- OAuth troubleshooting guide
- Troubleshooting most common issues related to the Oauth 2.0 authentication with incoming mail handlers (or the outgoing mail server) in Jira and JSM
- Configuring OAuth throws "An application link from the remote application to this application is required to configure this authentication provider" error
- Application Link (Source tab via OAuth) fails in JIRA after Bitbucket Server upgrade
- Troubleshooting applinks
- Application Link between Bamboo and JIRA doesn't work due to oauth_problem="timestamp_refused"
- Trusting JIRA and Clustered Confluence Fails with 'com.atlassian.security.auth.trustedapps.InvalidCertificateException'
- Missing Attributes (Summary, Resolution, Description) In JIRA Macro
- Cannot Use Basic Authentication to Access Gadgets from Confluence
- Getting a 'Bad Request' When Trying to Use Jira Issues Macro
This process is typically conducted towards the end of migrating Jira applications to another server or splitting Jira applications across multiple servers.
If you wish restore a single project from your backup into an existing Jira instance, refer to these instructions on restoring a project from backup instead.
Restoring Jira from backup is a three stage process:
- (Optional) Disable email sending/receiving
- Restore data to the database
Option 1: Restoring information from a native backup
Option 2: Restoring data from XML to the database - Restore the attachments to the attachments directory (if attachments were backed up).
If you've performed native backup, you also need to copy/restore the/data
folder manually to your new server.
Last modified on Sep 7, 2020
In this section
Related content
- OAuth troubleshooting guide
- Troubleshooting most common issues related to the Oauth 2.0 authentication with incoming mail handlers (or the outgoing mail server) in Jira and JSM
- Configuring OAuth throws "An application link from the remote application to this application is required to configure this authentication provider" error
- Application Link (Source tab via OAuth) fails in JIRA after Bitbucket Server upgrade
- Troubleshooting applinks
- Application Link between Bamboo and JIRA doesn't work due to oauth_problem="timestamp_refused"
- Trusting JIRA and Clustered Confluence Fails with 'com.atlassian.security.auth.trustedapps.InvalidCertificateException'
- Missing Attributes (Summary, Resolution, Description) In JIRA Macro
- Cannot Use Basic Authentication to Access Gadgets from Confluence
- Getting a 'Bad Request' When Trying to Use Jira Issues Macro
Powered by Confluence and Scroll Viewport.