Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Best Practice for back up

Hi, 

My company would like to know the best practice to back up Jira software and Confluence cloud recommended by Atlassian. 

We have seen the following threads about creating offline backup.

https://confluence.atlassian.com/jirakb/automate-backups-for-jira-cloud-779160659.html

https://support.atlassian.com/confluence-cloud/docs/create-a-site-backup/

Seeing that Alassian already makes backups of data for application recovery purposes, what are the planned use of these offline backups? Should we create these backups in specific occasions, like plan upgrade, or on regular basis? Can these offline backups be used to roll back changes?

Please share with us any other points regarding the cloud back if you deem relevant. 

 

Thanks and regards,

Ying

 

1 answer

1 accepted

2 votes
Answer accepted

>Seeing that Alassian already makes backups of data for application recovery purposes,

These backups are not designed for recovering individual systems, they are for recovering blocks of systems in case of server failure.   It can be done of course, they contain everything, but it's a long and slow process, and Atlassian do not offer recovery as part of the service - you can't ask them to recover from a backup if you make a mess of something and feel like rolling back.

>what are the planned use of these offline backups? Should we create these backups in specific occasions, like plan upgrade, or on regular basis? 

You don't have any control over upgrades, Atlassian do them.  Changes of plan/access are not something you would want to take a backup before anyway, changes of plan just affect access to functions and numbers of users, not the data.

You should be taking a backup whenever you think you're about to make config changes that might break things, or if you have a concern about losing access to the service and need to retain a copy of the data for some reason

>Can these offline backups be used to roll back changes?

Yes, but they are totally destructive - if you take a backup at date/time X, then make changes, adding more issues or pages, config change, editing existing data etc for the next 6 hours, then restore the backup, you will lose everything done in those 6 hours.  It's a complete roll-back, not a localised one.

Thank you for the detailed answer! @Nic Brough _Adaptavist_ 

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Jira Service Management

JSM June Challenge #2: Share how your business teams became ITSM rockstars

For JSM June Challenge #2, share how your non-technical teams like HR, legal, marketing, finance, and beyond started using Jira Service Management! Tell us: Did they ask to start using it or...

296 views 9 7
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you