Welcome Guest! Log in


Here is the minimal list of what should be backed up, in order to be able to restore / reinstall a Runtime.

Runtime files

The following directories should be backed up regularly, recursively (including their files and subdirectories).

Directory Comments
build/deliveries

Default location of the published deliveries. The subdirectory "wsdl" contains the deliveries published as a webservice.

build/packages

Default location where the Runtime will search for .pck packages.

Useful only when the Runtime is used for building Deliveries from Packages.

lib/addons This is where the jar files for optional connectors are installed (Salesforce connector, SAP connector, Amazon web services, etc.)
lib/jdbc This folder contains the JDBC drivers that the Runtime uses
log The Runtime log files. They can be deleted with no harm, but you may want to keep them for further investigation.
properties The Runtime properties.
scheduler This is where the default H2 Scheduler database is located. If you the Runtime uses an external scheduler database then this folder can be ignored, see below.
sessions This is where the default H2 Log database is located. If the Runtime uses an external log database then this folder can be ignored, see below.

 

Runtime log external database

If the Runtime uses an external log database then a proper backup strategy must be defined and applied on this database.

Note : if for any sad reason the Runtime log database is lost and/or corrupted and cannot be repaired, then the Runtime will be able to start after droping the 15 tables. All session history will be lost.

Runtime scheduler external database

If the Runtime uses an external scheduler database then a proper backup strategy must be defined and applied on this database.

You have no rights to post comments

Articles

Suggest a new Article!