Skip to content

AEM Refresh Procedure

What: Process to refresh a development AEM instance from production

When: Performed at the request of the front-end team, as frequently as possible. More frequent refreshes lead to less content to sync between instances, therefore less time to complete.

Prerequisites

This guide uses the terms SOURCE and TARGET.

TARGET : The instance we are updating. When complete, this instance will look just like SOURCE.

SOURCE : The instance we want to clone. No changes are made to the SOURCE instance.

Overview

Refreshing involves both the TarMk database, and application files.

Author

  1. {Author datastore} Sync NFS volumes using sync_datastores script.
  2. {Author crx-quickstart} Restore from latest SOURCE backup.

Author Step-by-step Procedure

Publisher

  1. {Publisher datastore} Use rsync to copy from prod publisher.
  2. {Publisher crx-quickstart} Save datastore.
  3. {Publisher crx-quickstart} Restore from latest SOURCE backup.
  4. {Publisher crx-quickstart} Put saved datastore into restored repository.

Publisher Step-by-step Procedure