If you work in a production environment, Adobe recommends that to take regular backup of your repository. The backup allows you to restore content and minimize data loss in the event of a disaster.
A simple Correspondence Management setup includes an author instance and a publish instance on the same machine or on different machines. The backup is performed while the repository is running. It is available for use while the backup is being performed. It is known as hot backup.
To back up the Correspondence Management environment, perform the steps on the author and publish instances as described in this article.
Consider the following points when backing up the author and publish instances:
- It's necessary that backup for author and publish instances are synchronized to start at the same time.
- Although you can continue to use author and publish instances while the backup is being performed, Adobe recommends not to publish any asset during the backup. If you do, the changes sometimes aren't captured. Wait for the backup of both author and publish instances to end before publishing new assets.
If a disaster occurs, you can restore the repository to the last backed up state by performing the steps described in this article.
Correspondence Management interacts with Forms, Output, and Assembler services of the Adobe Document Server. These services are stateless, and therefore you need not back up the Adobe Document Server in a simple Correspondence Management setup. If the Adobe Document Server fails, you can replace it with another running Adobe Document Server without any loss of data or functionality.
Note: Back up the Adobe Document Server If it is configured to perform post processings for advance document handling of Correspondence Management assets. For information on how to back up and recover the Adobe Document Server data, see this article.
This section describes the procedure to take hot backup of an instance of Customer Communications-Interactive Statements 10.0 Solution. The backup allows you to restore content and minimize data loss in the event of a disaster.
Interactive Statement provides regular communication, which includes statements and other media-rich information, for your customers. Interactive Statements Solution runs on Adobe Digital Enterprise Platform and leverages the platform’s development environment and capabilities. A typical instance includes the following:
- Processes to generate the statements. They reside in the Document Server.
- Assets used in statements. They reside in the Experience Server.
- A repository of customer data and mechanisms to distribute these statements. These are available at an implementation-specific location.
This sequence ensures that Experience Server is functional and the data source is available, before any tasks are triggered by Document Server.
You can continue to use the Solution and generate statements while a backup is being taken. Do not add, remove, or modify any assets, processes or database item, till the backup operation is finished for the involved entities like, Experience Server, Document Server, and other databases or servers.
Workbench developers can continue to work on their processes locally. They should not deploy any new processes during the backup phase.