ATLASSIAN CLOUD COPY SPACE CHARGE UPGRADE

This is the default for new Atlassian instances. That being said, I will briefly explain each option and what each’s strengths and weaknesses are. However, not all options are created equal. Server and Data Center products are a bit more complex to set up a good backup routine for – but honestly, it’s because you have options. Then when the time comes, Jenkins/Bamboo/whatever can check out this custom repo and run the latest version of your scripts. This setup will also allow you to change the scripts as needed for your case. I would honestly clone this repo to a local source control management system (think Bitbucket), then work on your repo going forward. It should be said that these scripts are not officially supported and provided “as-is,” so you may find yourself fixing things yourself from time to time. Atlassian thankfully provides some scripts to help with that. If you just want the data, you can take those as often as you should like.Īs noted above, you should automate your backups. To be clear, by complete back up I mean avatars, attachments, logos, and data. Atlassian lets you take a complete backup of your cloud instances once every 48 hours. So, going to start with the more straightforward system to set up. Anything more doesn’t improve your DR standing. In practice, though, two sites are usually sufficient: your primary site and your backup site. I get it’s easy when doing DR Planning to start thinking worse than the worst-case scenario. The idea here is to find a location where it’s difficult for any single event to impact multiple sites.īut how far do you go? It’s easy to get into a rabbit hole of thinking where you would require three sites – no, not good enough, four. For example, if you are in the US, consider something on the opposite coast or another continent.

Ideally, it would be best if you had your systems backed up to a different geographic location. So If you are backing up to the same physical location where systems are, you are opening yourself up to trouble. There is any number of disasters, both man-made and natural, that can cause a site to go down – permanently. If you haven’t guessed it, the answer is no. So question: Can you depend on the site where you are hosting your Jira instance to be there still when you need it? So, this is getting a bit further into Disaster Recovery than I intended to go, but I also feel this is important to talk about. The idea here is to put it somewhere that if something breaks, you are told about it. That being said, if Jenkins isn’t your thing, you can use Gitlab’s CI/CD, Bitbucket Pipelines, or even Bamboo to automate the process. In an emergency, the last thing you want to find is that your backups have been broken for a month. By using Jenkins, if something goes wrong with the backup routine, I can have Jenkins configured to send out a notification to my team. That being said, I prefer to have my backups executed by script, and I like that script to be run by a dedicated Jenkins instance. There are several ways to trigger your backup routine automatically, and how you do so will depend on what your backup routine looks like. This will also guarantee that your backups are happening regularly, meaning you can count on them being there when you need them.

ATLASSIAN CLOUD COPY SPACE CHARGE UPGRADE

You don’t want to be in a situation where you haven’t taken a backup in three weeks because your team has been too busy planning an upgrade that just went wrong. AutomationĪs a rule of thumb, your backups should be happening automatically. So today, we’ll talk about different methods for backing up your data, how often you should back up, and why you should test your backups regularly. Being able to restore your system from almost nothing is going to be critical on these days. This situation is where a good backup routine comes into play. So what is your plan then? How do you get your systems back online quickly and efficiently?

Just saying, some days are going to suck.

Atlassian cloud copy space charge