We have accidentally deleted all 2 year old JIRA Tickets. Is there a way to get them back?

[Laxmi Prasanthi Velamakanni]

Please help me understanding the back up policies and also how to find the current back up plans of our accounts. 

[Shannon S · Accepted solution]

Hi Laxmi,

You will need to restore from the latest backup you created. In the case of both Jira Server and Cloud, it is expected that you will make your own backups.

• For Server, if you can confirm you've not made your own backups previously, there's a chance that your server admin set up Automated Backups. If they have, then you can attempt to restore from this. Please note that it will revert all changes that have been made since the backup was created.

• As for Cloud, we do make our own backups, but these aren't supported for use to roll back changes, and only as disaster recovery. Have a look at our Data Storage FAQ:

  How often is data backed up?

  Automated Amazon Relational Database Service (RDS) backups are generated daily and retained for 30 days to allow for point-in-time data restoration. Snapshots of the primary RDS are also taken daily. Copies of the snapshot are sent to a secondary region, where they're kept for 30 days before being deleted. Snapshots and backups are not encrypted.

  Atlassian Cloud sites does not support the use of backup data to roll back changes.

  If you need to make an offline backup, check out the following documentation: 

  • Confluence – Create a site backup

  • Jira products – Exporting issues

Let me know if you have any questions.

Regards,

Shannon

[Laxmi Prasanthi Velamakanni]

Thanks for the insights. 

[andre_mohamed]

Hi, so how are these backups used for disaster recovery? 

How do we get access to the backups and snapshots for disaster recovery?

[Nic Brough -Adaptavist-]

They recover the entire set of systems that were affected by a disaster.  They are NOT suitable for single-service restorations, and you cannot get access to them (even if they were of any use to you, which they're not).

Have another read of Shannon's answer, it does explain it better than I can.

[Shannon S]

André, 

As Nic mentioned, we can use it to restore the system that your Cloud instance resides on, and is not used to roll-back single instances. Unfortunately this is not something you can have access to, and can only be restored to the system we use to host Cloud itself, and not to another instance, for example.

I hope that's clear, but do let us know if you have any other concerns!

Regards,

Shannon

[Moses Thomas · Accepted solution]

@Laxmi Prasanthi Velamakanni You  have  recover it from your Jira  database back up.

[Joe Pitt]

As @Shannon S said, restoring the backup will over write your current data including any workflow, screen, or other changes. Another option is to restore the backup to another instance and export them to a csv file and then import them into your production instance. You'd lose the history data but have the meat of the issue.

This is why many of us 'old timers' strongly discourage deleting issues. If you're trying to clean up a project, which it sounds like you were, create a new project with name-Archive and move them to that project. Then set the permissions on the project so only a limited number or even no one can view it.  I use a resolution of 'Deleted' for individual issues people want deleted. The forum is full of people wanting to recover deleted issues and there really isn't a good way to do it. 

[Vickey Palzor Lepcha]

I would say - restore from backup in a test instance - sort out the deleted issuetypes and reimport it back to your production instance

- that would retain your current data atleast and not override them