Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

SOLVED

Deleted asset folder possible to restore

Avatar

Level 3

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

1 Accepted Solution

Avatar

Correct answer by
Employee Advisor

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!)

View solution in original post

3 Replies

Avatar

Employee Advisor

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

Avatar

Level 3

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!

Avatar

Correct answer by
Employee Advisor

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!)