Hi All, smacdonald2008, Jörg Hoh,
My teammate deleted the DAM asset folder in author environment if possible to recovery / restore the asset?
is that advisable to package the folder from Publish environment ?
Referred Managing the Trash folder
Thanks In Advance!
Please help me to overcome!
-Karthi
Solved! Go to Solution.
If you package the data from publish and re-install it on author, you'll get all the data. On author the asset-update workflow might kick in an try to extract some metadata from the binaries again. You might want to disable this launcher temporarily if this is causing problems.
And when everything is fine on author again, you should consider a tree replication of the assets to bring author and publish back in sync.
(Try that on a test instance first before you go to PROD!)
Have you tried to restore this folder (plus all folders below it)? If your teammate used the regular functions of the AEM authoring env (and not CRXDE) it might create versions before deletion (haven't checked it right now).
Of course packaging the DAM folder von publish and re-install it on authoring is working, but you probably need to fix some metadata (like activation status etc).
Jörg
Thanks for the reply Jörg Hoh !
Yes they used authoring env to delete not in CRDE but we dnt have any version i think we checked based on the permissions which is given to me!If any direction to forward step?
If we are activating/Publishing , the image that will share the image and its property from author to publisher ?.
Hope Will get the metadata which is used in publisher !
Please Correct me if am missing any point!
Views
Replies
Total Likes
If you package the data from publish and re-install it on author, you'll get all the data. On author the asset-update workflow might kick in an try to extract some metadata from the binaries again. You might want to disable this launcher temporarily if this is causing problems.
And when everything is fine on author again, you should consider a tree replication of the assets to bring author and publish back in sync.
(Try that on a test instance first before you go to PROD!)
Views
Likes
Replies