How to Become a Master of Disaster (Recovery in Jira)
summary
Claims that Atlassian cannot restore single customers after the April 5 2022 outage that affects ~700–800 customers and that some customers wait three days to two weeks for recovery; recommends the 3-2-1 backup rule, encryption and secret management, and regular tested restores because a customer who restored to production loses hundreds of attachments. Shows a working G protect demo that integrates to Jira via API token, starts backups (compressing attachments) and offers point-in-time and granular restores for projects and issues.
AI-written summary · about
chapters (14)
- 0:00Jira disaster recovery intro
- 2:19Need for Jira backups
- 8:11Atlassian backups limitations
- 13:15Jira data threats
- 16:12Prepare for Jira disaster
- 17:36Backup performance limits
- 21:09Disaster recovery key points
- 23:19Backup security and testing
- 25:53Failed backup testing
- 30:09Native Jira backup limits
- 32:17On-site Jira backups
- 33:40Third-party Jira backups
- 36:53Git Protect demo
- 40:11Closing & Q&A
related talks
27mLessons from Incident Management and Postmortems at Atlassian
17mHow Atlassian Unlocks High-Velocity Teams with Jira
46mA journey to disaster
06mA Battle Plan for Disaster Recovery in the Wake of Ransomare
16mResilient by Design: Architectures for Crisis Response & Recovery
05mNever be on call again
44mCyber Recovery: Your Power-Up in the World of IT Security
32mSchroedingers Backup