Certain folders in the persistent volumes must be replicated to the disaster recovery
site.
Gateway Server
With the introduction of dynamic persistent volumes, the names of the persistent volumes cannot be
predetermined. To identify the persistent volumes, see the persistent volume claims that show the
corresponding persistent volumes.
Replicate the folders used by
Gateway Server. Include the following folders in the replication
to the disaster recovery site.
Table 1. Gateway Server folders
| Persistent volume claim |
Folders |
<ftm-instance>-application |
applications/gateway-server/lib |
<ftm-instance>-gateway |
runtime-processing |
Business Rules Server and Business Rules Manager
The
Business Rules Server and
Business Rules Manager have common user data and intermediate
folders that need to be replicated.
Table 2. Business Rules Manager persistent volumes
| Persistent volume claim |
Folders |
<ftm-instance>-application |
- applications/business-rules/userdata
- applications/business-rules/intermediate
|
Distribution engine
The Distribution engine has a working folder that must be replicated to the disaster recovery
site.
Table 3. Distribution engine persistent volumes
| Persistent volume claim |
Folders |
<ftm-instance>-application |
applications/distribution-engine/working |
Image data
The image files must be replicated to the disaster recovery site.
Table 4. Image data persistent volumes
| Persistent volume claim |
Folders |
<ftm-instance>-image-data |
image-data/hsimages |
IBM App Connect
Data that might need to be replicated can be delivered into the following folders. Any customized folders
that were added for
IBM® App Connect flows also need to be replicated.
Table 5. IBM App Connect persistent volumes
| Persistent volume claim |
Folders |
<ftm-instance>-ace |
|