The server data backup process inspects all of the tables in the database, collecting and then exporting all table data to a ZipEntry. For certain tables, such as the catalog version table, report set version table, and report set result version table, the data also includes relational real files from the history directory. All server data is compressed to a single Zip file, and all table data and every relational real file is stored as a ZipEntry in this single file.
You have two alternatives for exporting the server data: through the server user interface or through command line.
Note: The Profiling DB tab is not shown by default. To show this tab, set the server.profiling.enable property to true in the server.properties file in the <install_root>\bin directory.
A tool is provided to backup the server data. It is DBMaintain.bat/DBMaintian.sh in <install_root>\bin. It has two parameters:
To export the server data from the command line on Windows or on UNIX/Linux:
<install_root>\bin folder.DBMaintain command (DBMaintain.sh on UNIX/Linux) and -Bsystables/-Bprofiling or -B0systables/-B0profiling parameter. For example:
C:\JReport\Server\bin>DBMaintain -Bsystables:C:\TEMP\cmd_b_systables.dat -Bprofiling:C:\TEMP\cmd_b_profiling.dat
The server data restore process picks up all table data from the backup file and inserts it into the corresponding table in the database. You can only restore server data using the DBMaintain tool with the -Rsystables/-Rprofiling or -R0systables/-R0profiling parameter.
To import server data using the command line:
<install_root>\bin folder.C:\JReport\Server\bin>DBMaintain -Rsystables:C:\TEMP\cmd_b_systables.dat -Rprofiling:C:\TEMP\cmd_b_profiling.dat
The backup/restore feature does not support cross-platform operation. The backup and restore operations must be done on the same operating system. For example, if you backup the server data to a zip file on a Windows platform, you will then not be able to restore it on a UNIX system.