|
Note: If your LiveCycle implementation stores additional custom
data in a different database, you must implement a strategy to back
up this data ensuring that it remains in sync with the LiveCycle
data. Also, the application must be designed so that it is robust
enough to handle a scenario where the additional databases get out of
sync. It is highly recommended that any database operation that
is performed is done in the context of a transaction to help maintain
a consistent state.
You need to back up the following parts of the LiveCycle system
to recover from any error:
Database used by LiveCycle
GDS that has long lived data and other persistent documents
AEM database (crx-repository)
Note: You need to backup any other data that is being used by your
LiveCycle setup, such as customer fonts, connecters data, and so
on.
|
|
|
