There are many answers to this question. Using the build in confluence backup is one approach. Not advisable if the instance is large though.
If its a Confluence instance worth doing backup on I would advice moving your production site to Postgres. Doing that is a pretty straight forward approach.
Atlassian has plenty of documentation regarding this that could be helpful.
Perhaps the easiest way to solve this is doing a complete backup of the server since if the database in conjunction with the confluence data needs to be and exact match. If not you might end up with corrupt DB data and that is a mess to clean up
We're still using a trial edition; that's what we plan to do when we "go live" with an actual licensed edition. So it's a pretty small database as it is.
Do you have a recommendation for backing it up now? Currently we don't have a DBMS like Postgres or MySQL; I just chose defaults when we installed it.
Look at the "system information" page, that will tell you what the database is.
It is probably hsql though. You should migrate to a proper database, as hsql can fail without warning or backup. To do so, see https://confluence.atlassian.com/doc/migrating-confluence-between-servers-184150.html
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