Prezeráte obsah pomocníka verzie:
- 6.4
- 6.3
- 6.2
- Staršie verzie
Poznámka:
If your AEM forms 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 AEM forms 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.
Database used by AEM forms
GDS that has long lived data and other persistent documents
AEM database (crx-repository)
Poznámka:
You need to backup any other data that is being used by your AEM forms setup, such as customer fonts, connecters data, and so on.
Offline backup with downtime
Offline backup with no downtime (backup of a slave node which is shutdown)
Online Backup with no downtime but delay in response
Back up the Bootstrap properties file
-
Shut down the entire cluster and related services. (see Starting and stopping services)
-
On any node, back up the database, GDS, and Connectors. (see Files to back up and recover)
-
For detailed steps, see Backup and Restore.
-
Enter the rolling backup mode. (see Entering the backup modes)
Note that we need to leave the rolling backup mode after a recovery.
-
Shut down any of the slave nodes of the cluster with respect to AEM. (see Starting and stopping services)
-
On any node, back up the database, GDS, and Connectors. (see Files to back up and recover)
-
For detailed steps, see Backup and Restore.
-
Enter the rolling backup mode. (see Entering the backup modes)
Note that you need to leave the rolling backup mode after a recovery.
-
Shut down any of the slave nodes of the cluster with respect to AEM. (see Starting and stopping services)
-
On any node, back up the database, GDS, and Connectors. (see Files to back up and recover)
When we create an AEM cluster, a properties file is created in the application server for all slave nodes. It is recommended to back up the Bootstrap properties file. You can find the file at the following location on your application server:
You need to back up the file for disaster recovery scenario of AEM slave node and replace it at the specified location on the application server, if restored.
In case of any failure of the entire cluster or a single node, you need to restore it using the backup.
For a single node recovery, you just need to shut down the single node and run the single node recovery procedure.
In case the entire cluster fails due to failures like database crash, you need to perform the following steps. Restoration depends on the method of backup used.
-
(Optional) If all other nodes are working fine, it is possible that the AEM repository is alsocorrupted. In this case, you will see a repository unsync message in the error.log file of the AEM repository.
To restore the repository, perform the following steps.
Poznámka:
If a zipped crx-repository backup was taken online, unzip it at any location and follow the offline restoration process.
Poznámka:
Consider the following points:
If the failed node was an AEM master node, copy all the content from the slave repository folder (crx-repository\crx.0000 where 0000 can be any digits) to the crx-repository\ repository folder and delete the slave repository folder.
Before restarting any cluster node, ensure that you delete the repository /clustered.txt from the master node.
Ensure that the master node is started first and once it is completely up, start other nodes.
-
Poznámka:
If a zipped crx-repository backup was taken online, unzip it at any location and follow the offline restoration process.
Poznámka:
Consider the following points:
If the failed node was an AEM master node, copy all the content from the slave repository folder (it looks like crx-repository\crx.0000 where 0000 can be any digits) to the crx-repository\ repository folder.
Before restarting any cluster node, ensure that you delete the repository /clustered.txt from the master node.
Ensure that the master node is started first and once it is completely up, start other nodes.
The publisher node does not have any master-slave relationship in a clustered environment. You can take backup of any Publisher node by following Backup and Restore.
-
Restore the Publish node using Restoring the Backup.
-
Restore the Publish node using Restoring the Backup.