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. |
Definition information (definition file) | Definition information to be deployed to the CEP engine | When storing on the CEP Server. |
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.
Refer to the manual of the relevant collaboration product for information on the backup and restore of resources in the collaboration system.
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)
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>
Follow the steps below as a superuser to restore the resources:
Restore the engine configuration file
Restore the master data
Restore the definition information
This section assumes that this product 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.4.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>