6.3.2 Backup and Restore

Resources must be backed up periodically, in case the system on the CEP Server fails.

The table below lists the resources to be backed up.

Resource name	Content	When to back up
Engine configuration file	File defining the CEP engine configuration	When settings are changed.
Master data	Master data to be stored in the CEP engine	When storing on the CEP Server. When editing on the CEP Server.
Definition information (definition file)	Definition information to be deployed to the CEP engine	When storing on the CEP Server. When editing on the CEP Server.
User-developed Java class	jar file or class file of the user-developed Java class	When storing on the CEP Server.
Setup files for Terracotta collaboration	Files required for Terracotta collaboration	When changing settings
Setup file for RDB collaboration	File required for RDB collaboration	When changing settings

The event log stored on the CEP Server is for checking operation, so it does not need to be backed up or restored.
If the master data is backed up by the data provider, it does not need be backed up.
If the definition information is backed up by the definition information developer, it does not need to be backed up.
If the user-developed Java class has been backed up by the developer, it need not be backed up.
Refer to the manual of the relevant collaboration product for information on the backup and restore of resources in the collaboration system.

6.3.2.1 Backup Procedure

Follow the steps below as a superuser to back up the resources:

Back up the engine configuration file
Back up the master data
Back up the definition information (definition file)
Back up the user-developed Java class
Back up the setup files for Terracotta collaboration
Back up the setup file for RDB collaboration

This explanation uses the following directory to back up the resources:

/backup

Back up the engine configuration file

Back up the engine configuration file specified during execution of cepconfigeng.

Example

When the engine configuration file is "/etc/opt/FJSVcep/Engine.xml".

# cp -p /etc/opt/FJSVcep/Engine.xml /backup/<ENTER>

Back up the master data

Back up the master data stored on the CEP Server.

Example

When the master data is stored in "/masterdata".

# cp -rp /masterdata /backup/<ENTER>

Back up the definition information (definition file)

Back up the definition information (definition file) stored on the CEP Server.

Example

When the definition file is stored in "/application".

# cp -rp /application /backup/<ENTER>

Note

RDB reference definition file

The RDB reference definition file contains the password, so for security reasons you must take measures before backing up the file to ensure that the password cannot be referenced. Do this by deleting the access password from the definition file, or encrypting the entire definition file.

Back up the user-developed Java class

Back up /etc/opt/FJSVcep/config/custom.

Example

When backing up the definition information of the user-developed Java class.

# cp -rp /etc/opt/FJSVcep/config/custom /backup/ <ENTER>

Back up the setup files for Terracotta collaboration

Back up /etc/opt/FJSVcep/config/ehcache.xml and /etc/opt/FJSVcep/config/terracotta_conf.

Example

When backing up the definition information of the setup files for Terracotta collaboration.

# cp -p /etc/opt/FJSVcep/config/ehcache.xml /backup/<ENTER>
# cp -p /etc/opt/FJSVcep/config/terracotta_conf /backup/<ENTER>

Back up the setup file for RDB collaboration

Back up /etc/opt/FJSVcep/config/rdb_conf.

Example

When backing up the definition information of the setup file for RDB collaboration.

# cp -p /etc/opt/FJSVcep/config/rdb_conf /backup/<ENTER>

6.3.2.2 Restore Procedure

Follow the steps below as a superuser to restore the resources:

Restore the engine configuration file
Restore the master data
Restore the definition information
Restore the user-developed Java class
Restore the setup files for Terracotta collaboration
Restore the setup file for RDB collaboration

This section assumes that BDCEP has been installed and set up (refer to "Chapter 4 Installation and Setup" for details).

It also assumes that the following resource backup directory exists:

/backup

Restore the engine configuration file

Restore the engine configuration file (refer to "Chapter 4 Installation and Setup" for information on how to reconfigure a CEP engine using a restored engine configuration file).

Example

When the engine configuration file that is the backup source is in "/etc/opt/FJSVcep/Engine.xml" and the backed up engine configuration file is "/backup/Engine.xml".

# cp -p /backup/Engine.xml /etc/opt/FJSVcep/<ENTER>

Restore the master data

Restore the master data.

Example

When the master data that is the backup source is in "/masterdata" and the backed up master data is "/backup/masterdata".

# cp -rp /backup/masterdata /<ENTER>

Restore the definition information (definition file)

Restore the definition information (definition file) (refer to "6.1.3.1 Deploying Definition Information" for information on how to redeploy restored definition information).

Example

When the definition information (definition file) that is the backup source is in "/application" and the backed up definition information is "/backup/application".

# cp -rp /backup/application /<ENTER>

Restore the user-developed Java class

Restore the user-developed Java class.

Example

When the backed up user-developed Java class is stored in "/backup/custom".

# cp -rp /backup/custom /etc/opt/FJSVcep/config/ <ENTER>

Restore the setup files for Terracotta collaboration

Restore the setup files for Terracotta collaboration.

Example

When the backed up setup file is "/backup/ehcache.xml" or "/backup/terracotta_conf".

# cp -p /backup/ehcache.xml /etc/opt/FJSVcep/config/ <ENTER>
# cp -p /backup/terracotta_conf /etc/opt/FJSVcep/config/ <ENTER>

Restore the setup file for RDB collaboration

Restore the setup file for RDB collaboration.

Example

When the backed up setup file is "/backup/rdb_conf".

# cp -p /backup/rdb_conf /etc/opt/FJSVcep/config/ <ENTER>