Restoring from new beta backup function - what about the data not backed up?

[Rune Rasmussen]

Looking at the backup and restore functionality in the admin portal, that is currently in beta, there are some things that are not back up, like automation rules.
full list.

What happens then if you restore from one of these backups?
Do you keep your old automation rules, or are they all just gone?

[Matt]

Sorry to say, they're just gone 😔

[Josh]

@Rune Rasmussen my understanding is that you're not restoring over top of the existing instance. Instead, you'd be restoring to a replacement instance.

In this case, any previous data that you had that is not covered by backups (e.g. automation rules, Confluence databases) would be entirely lost and would need to be rebuilt on your end. Definitely a lot of room for improvement here...

Someone more knowledgeable on the topic is welcome to correct anything I might have misunderstood or missed about this process; documentation is pretty sparse at the moment.

[Mathew Lederman]

@josh I agree with you. This process is not intended to overwrite a Production instance, but instead to create a backup for fallback or recovery purposes. 

[Susan Waldrip]

Hi @Rune Rasmussen , @Josh and @Matt are correct. Atlassian's backup and restore (B/R) capabilities (at least right now) are disaster recovery, not for day-to-day B/R management. There are several excellent B/R apps in the Atlassian Marketplace, these will give you the granular capability you should have as an Admin to run nightly/on-demand backups for configuration and work items, restore only the things you need, identify dependencies so you properly restore items and the things they depend on, and more.

You can start by searching the Atlassian Marketplace, that will give you a good list of B/R apps to research.