AEM 6.4 | Restore Tree option deleting all content from AUTHOR and PUBLISHER

[rohitp23277067]

Hi all,

Hope everyone doing fine. 

Has anyone experienced this DELETION issue related to "Restore Tree" feature.

We are on AEM 6.4 . We were using "Restore Tree" (Tools > Restore > Restore Tree) option from "Classic UI" since "Touch UI" still does not have this feature yet. 

https://docs.adobe.com/content/help/en/experience-manager-64/classic-ui/siteandpage/classic-page-aut...

1) What we noticed was when we used "Restore Tree" option and selected a hierarchy which we wanted to restore - This process deleted all our other content pages (everything it deleted except the one which we selected for restore).

2) Then we saw that even everything was deleted from Publisher Instance too. To troubleshoot this further we looked at replication log and clearly we could see DELETE replication messages there in replication log. See sample replication log below

2020-04-19 20:32:03 - INFO - publish : Creating content for path /content/xyz/banner
2020-04-19 20:32:03 - INFO - publish : Sending POST request to http://localhost:4503/bin/receive?sling:authRequestLogin=1
2020-04-19 20:32:03 - INFO - publish : sent. Response: 200 OK
2020-04-19 20:32:03 - INFO - publish : ------------------------------------------------
2020-04-19 20:32:03 - INFO - publish : Sending message to localhost:4503
2020-04-19 20:32:03 - INFO - publish : >> POST /bin/receive HTTP/1.0
2020-04-19 20:32:03 - INFO - publish : >> Action: Delete
2020-04-19 20:32:03 - INFO - publish : >> Path: /content/xyz/banner
2020-04-19 20:32:03 - INFO - publish : >> Handle: /content/xyz/banner
2020-04-19 20:32:03 - INFO - publish : >> Referer: about:blank
2020-04-19 20:32:03 - INFO - publish : >> Content-Length: 0
2020-04-19 20:32:03 - INFO - publish : >> Content-Type: application/octet-stream
2020-04-19 20:32:03 - INFO - publish : --
2020-04-19 20:32:03 - INFO - publish : << HTTP/1.1 200 OK
2020-04-19 20:32:03 - INFO - publish : << Date: Mon, 20 Apr 2020 00:32:03 GMT
2020-04-19 20:32:03 - INFO - publish : << X-Content-Type-Options: nosniff
2020-04-19 20:32:03 - INFO - publish : << Content-Type: text/plain;charset=utf-8
2020-04-19 20:32:03 - INFO - publish : << Content-Length: 28
2020-04-19 20:32:03 - INFO - publish : <<
2020-04-19 20:32:03 - INFO - publish : << ReplicationAction DELETE ok.
2020-04-19 20:32:03 - INFO - publish : Message sent.
2020-04-19 20:32:03 - INFO - publish : ------------------------------------------------
2020-04-19 20:32:03 - INFO - publish : Replication (DELETE) of /content/xyz/banner successful.

Has anyone else faced same problem of DELETION while using "Restore Tree" - Is this default behavior of AEM. Seems like a bug.

[arunpatidar]

Hi,

Check below at https://helpx.adobe.com/experience-manager/6-2/sites/authoring/using/working-with-page-versions.html

Restoring a Tree from the Console - Classic UI

This method can be used to restore a page version. It can also be used to restore pages that have been previously deleted:In the Websites console, navigate to the folder you want to restore and select it.

From the top menu select Tools, then Restore.

Selecting Restore Tree... opens the dialog to let you select the tree you want to restore:

2. delete event get trigger activation if page are already activated.

[rohitp23277067]

Hi Arun, Thanks for quick reply on this. Wondering why entire content was deleted from author and publisher and then it did not restored. AS you know all the pages will be published to publisher so this restore should preserve or revert to that version. Can this be AEM bug where it deletes everything ? Is there more documentation to this Restore Tree as current AEM site does not have much documentations other than what you pasted.

[arunpatidar]

Hi,

Not sure if this is a known issue , @Vish_dhaliwal  do you have any idea?

Unfortunately I am not able to find more documentation. @kautuk_sahni could you please support?

[rohitp23277067]

Hi @Vish_dhaliwal - Can you help here - can u confirm if its AEM bug which deleted all content when we use Restore Tree option.