Restore AEM backup | Community
Skip to main content
A
akank_23
Level 2
July 2, 2021

Restore AEM backup

  • July 2, 2021
  • 1 reply
  • 2210 views

Hi All,

 

May I know how can we restore crx-quickstart backup for publish instance.

The instance is hosted on linux server.

 

Any pointers may help .

 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

1 reply

MarkusBullaAdobe
Adobe Employee
MarkusBullaAdobeAdobe Employee
Adobe Employee
July 2, 2021

Hi @akank_23!

The correct procedure to restore an AEM instance backup depends on your backup strategy.

You may want to check the official documentation on backup and restore for AEM.

There are different common approaches to backups in AEM

  • Use operating system tools to take a snapshot of the instance. This can be a snapshot of the AEM directory, of a file system or of a complete server/virtual machine. A restore would be done by replacing the current folder structure/file system/server/vm with the contents of the desired backup.
  • Use AEMs online backup tool. A restore would be done following the documentation by replacing the current contents of the AEM folder on file system level with the contents of the backup (being it a folder-backup or a zip file; the later would have to be extracted).

There is another approach to restores when it comes to publish instances:

Usually, you will have multiple publish instances available. If you only need a restore for one of them, you can also create a clone of one of the others and restore that to the desired host/instance. You would need to adjust certain configs on the clone to reflect the target instance (probably replication agents for dispatcher flush and similar). In my eyes, this is actually the easiest way to restore a single publish instance (or to add additional ones for scaling purposes).

 

Hope that helps!

    MarkusBullaAdobe
    Adobe Employee
    MarkusBullaAdobeAdobe Employee
    Adobe Employee
    July 2, 2021

    Hi @akank_23!

    Without any further knowledge about the situation it's hard to give a clear recommendation.

    There are ways to address and potentially fix a repository corruption. Please refer to the following articles for guidance:

    If you are able to fix the corruption following the described actions, you're fine.

    Of not, you may have to follow one of the restore approaches as outlined in my initial response.

     

    In addition to that, I would also recommend to perform an analysis to see if you can find the root cause for the corruption to avoid similar situations in the future.

     

    Hope that help!

      Terms & ConditionsAccessibility statement

      Loading footer...