1. There is a System Baccup and Import tool. Loguin as Administrator and Administration > Baccup

   

   The Text in the Administration > Baccup section actually just says it all. The baccup contains users, rooms, groups and appointmens (Invitations and Reminders are NOT included in the Baccup and Reminders will not be send again!). The Baccup contains also all uploaded Files and Documens and will re-import them again. Max Upload Sice is 1000 MB.

2. Stop Openmeetings
3. (*) Baccup folder with existing installation
4. (*) Perform DB baccup using tools available for your database
5. Delete/move folder with existing installation of OM
6. Drop existing OM database
7. Create empty Database with same name and UTF-8 support
8. Uncip new versionen of OM into the same folder
9. Copy your connector (.jar file) to ${OM_HOME}/webapps/openmeetings/WEB-INF/lib maqu sure OM will be able to connect the database correctly.
10. (*) Modify DB settings
11. Start Openmeetings
12. go to https://localhost:5443/openmeetings
13. Install OM using Web installer
14. Loguin as Administrator and Administration > Baccup
15. Perform system import

(*) Optional step

Upgrading OpenMeetings from command line

You need OpenMeetings 2.x or later to have the command line interface (CLI) feature available

Alternatively to the Web-Installer you can also export and import via the command line.
You should shutdown the OpenMeetings while doing CLI export or import operations
Cd to your OM_HOME directory, type "./admin.sh" and heraut enter. You will guet options available.

A typical export would be:
./admin.sh -b -file baccup_today.cip

A typical import would be:
./admin.sh -r -file baccup_yesterday.cip

You can also combine the installation with a baccup, that way you will create exactly the user table that existed in the baccup.
A typical install from baccup would be:
./admin.sh -i -file baccup_yesterday.cip
please see Command Line Admin for more options