This feature is a high-availability setting that allows you to establish a trusted, pre-authenticated connection between two separate Jira Cloud sites. It provides a dashboard to activate and manage these links, which authorize a "destination site" to pull data from a "source site" in an emergency.
What is the use case?
The use case is for a "cold-standby" disaster recovery strategy. An administrator uses this to link their primary Jira instance to a secondary, standby instance. If the primary site becomes completely inaccessible due to a major outage, this trusted connection allows the admin to log into the standby site and initiate a "pull" to recover critical data and restore operations.
This feature is applicable to:
command center for jiraconfig manager for jiraassets data manager for jira
Disaster Recovery Connections
This page is the central hub for managing the connections between your primary Jira Cloud
site and another site for the purpose disaster recovery.
The goal is to establish a secure link between this site and another Jira Cloud site. This ensures that in the event of an outage, you can pull data from the source site to the connected site.
Connection Types
We offer two primary methods for connecting your sites: Cross-Site Connection and Disaster Recovery (DR) Connection, each designed for a specific purpose.
1. Cross-site connection:
This feature sets up a connection between two sites and is primarily designed to facilitate the migration of projects.
It is especially useful when you need to move or clone projects, workflows, issues, and configurations from one site to another (e.g., from a staging site to a production site).
Mechanism: Uses a Push Mechanism where you push changes from a source site to a destination site.
Purpose: Primarily used for moving or cloning things across sites.
Use Case: Ideal for deploying configurations, moving things, or practicing in a sandbox environment
2. Disaster recovery connection:
This feature is designed specifically to provide a backup solution in case of an unexpected outage or failure on your source site.
If the source Jira instance becomes unavailable due to server issues, data corruption, or any other disruption, this connection allows the organization to access and recover critical data by pulling it from the source site to the connected standby site.
You use this feature during disaster recovery. If the source data instance becomes unavailable, this connection allows the organization to access and recover critical data by pulling it from the source.
Mechanism: Uses a Pull Mechanism. You go to the destination (standby) site and pull the required data from the affected (source) site
Available Actions
At the top right of the screen, you will find two main actions:
1. + Add recovery connection
Click this button to begin the process of setting up a new disaster recovery connection to another Jira Cloud site.
2. Activate connection
This button is used to activate an existing, pre-configured connection, typically during a migration event or a disaster recovery scenario.
Disaster Recovery Setup
A proactive setup is a mandatory step to ensure the Disaster Recovery feature works when a disaster occurs.
1. Proactive Setup (Before an Outage)
Establishing a connection before an emergency occurs is highly recommended to minimize downtime.
Step 1: Access Settings
Log into the Revyz Command Center for Jira.
Navigate to Settings and then select Disaster Recovery Connections.
Step 2: Generate a Connection Token
Click + Add recovery connection.
Enter a Connection name (3–65 characters; alphanumeric, spaces, _, or - are allowed).
Click Add connection to generate your unique recovery token.
Step 3: Secure Your Token
Copy the token immediately.
Crucial: This token will no longer be accessible once you close the window.
Store the token in a secure location (e.g., a password manager) according to your organization's security policies.
2. Activating the Connection
Option A: Immediate Setup (Recommended)
If you have a standby site ready, navigate to that site’s Revyz app, click Activate connection, and enter the Source Site URL and the Recovery Token.
Option B: Activation During an Outage
If you do not have a fallback site ready, store the token safely. You will perform the activation steps below on your fallback site only when a disaster occurs.
To Activate:
On the standby/fallback site, navigate to Disaster Recovery Connections.
Click Activate connection.
Provide the Source Site URL (the URL of the affected site) and paste the Recovery Token.
Click Activate.
3. Mandatory Security Verification
To protect your data from unauthorized access, a proactive connection is not immediately usable for recovery.
Verfication process
To protect your data from unauthorized access, a proactive connection is not immediately usable for recovery.
Support Activation Required: For security, the "Recover site" feature must be manually enabled by the Revyz support team.
Verification Process: Once the connection is established and active, you must Contact Support.
Checks: The support team will verify email addresses and other details to ensure the recovery request is legitimate before unlocking the feature.
Steps to take when the site is down:
Case 1: Proactive Setup (Connection Established)
Use this flow if you already linked your standby site to your production site before the outage.
Step 1: Log in to your pre-configured Standby Site.
Step 2: Check if the connection is already Active in the Disaster Recovery dashboard.
Step 3: Reach out to Revyz Support to perform the mandatory security verification (verifying email addresses and site ownership).
Step 4: Once support enables the feature, click the three-dot menu on your connection and select Recover site.
Even after you establish the connection and it appears active, you must reach out to us. The support team will confirm your email addresses, verify details, and perform checks before allowing the connection to be used. Once this check is complete, you will be able to proceed with the recovery process.
Case 2: Reactive Setup (Token Stored Only)
Use this flow if you only have the token saved and have not yet linked it to a standby site.
Step 1: Retrieve the Connection Token you stored during the initial setup.
Step 2: Access your Fallback/Standby Site.
Step 3: Navigate to Disaster Recovery Connections and click Activate.
Step 4: Provide the Source Site URL and paste your Token.
Step 5:Contact Support immediately for identity verification; the "Recover site" button will remain locked until they verify your request.