You could write one, but it would be a nightmare. Cloud is designed for people to use for collaboration. It's not a backup solution. Your code would need to export your whole Confluence to xml, upload it, deal with all the issues, and you will still end up with issues around users and error handling.
It would be a lot easier the other way around - use Cloud and then replicate to a server, but it's still a vast effort.
Seriously, either swap to using Cloud and don't think about DR because it should be built-in, or forget Cloud as a DR option and do it properly, with your own redundant and remote DR servers.
I just got an email about how you could do it, which seems to have vanished. In case you do read that, the process is good, but as I said, a bit of a pain. And it doesn't cover the point that Cloud will behave very differently - when I said "deal with all the issues", that includes behaviours such as not being able to use user macros and add-ons that are not supported in Crowd. That's where it flips from "a bit of a pain" to "nightmare". It certainly wouldn't be "disaster recovery" as most of the world understands it, because you really wouldn't be restoring to a system the same as the source one.
Hi team, I’m Avinoam, a product manager on Confluence Cloud, and today I’m really excited to let the Community know that all customers can now try out the new editing experience and see some of the ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs