Restoring the entire cluster

  1. Stop all the cluster nodes.

  2. Recreate the physical system from a system image.

  3. Apply patches or updates to LiveCycle ES that were applied since the image was made. This information was recorded in step 1 of the backup procedure. LiveCycle ES must be recovered to the same patch level as it was when the system was backed up.

  4. Restore the database, GDS, and Connectors.

  5. Do the following to recover the AEM repository offline:

    Note: If a zipped crx-repository backup was taken online, unzip it at any location and follow the offline restoration process.

    1. On all cluster nodes, delete the repository, shared, version, and workspaces directories in the clusterNode directory.

    2. Delete all files and directories in the shared directory.

    3. Restore the backup of the cluster node (including subdirectories) to one cluster nodes.

    4. Copy all files of the restored cluster node to all other cluster nodes. Once done, each cluster node contains the same data.

    5. Delete the file clusterNode/revision.log on all cluster nodes.

    6. Delete the .lock on all cluster nodes, if exists.

    7. Delete the repository/system.id all cluster nodes, if exists.

    8. Delete the files **/listener.properties on all cluster nodes, if exist.

    9. Restore repository/cluster_node.id for individual cluster nodes.

Note: 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.

// Ethnio survey code removed