Restoring a single node

  1. Stop the corrupted node.

    Note: If the corrupted node is an AEM master node, shut down the entire cluster node.

  2. Re-create the physical system from a system image.

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

  4. (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.

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

    1. Delete the repository, shared, version, and workspaces directories in the clusterNode directory of the node.

    2. Restore the backup of the cluster node (including subdirectories) to the node.

    3. Delete the file clusterNode/revision.log on the node.

    4. Delete the .lock on the node, if exists.

    5. Delete the repository/system.id on the node, if exists.

    6. Delete the files **/listener.properties on the node, if exist.

    7. 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 (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.

// Ethnio survey code removed