Hi,for cloning an instance most of that page is not valid, in the page it specifically mentions cq5. If you clone an AEM 6.2 instance, you should delete the file "sling.id.file" and also reset the cluster id, you can find out how in this page [0] in the "Configuring a Shared Data Store"The following...

There is only a single workspace in OAK, please slide 18 of this presentation from engineering [0]. There is also mention of it in the Oak documentation[1]. It wasn't a commonly used feature.Regards,Opkar [0]https://docs.adobe.com/content/ddc/en/gems/technical-deep-dive-of-the-aem-6-platform/_jcr_co...

What version of AEM are you using? Details on the differences and future direction from a previous answer[0]. There are also quite a few other questions on this topic in the forum.Regards,Opkar[0]http://help-forums.adobe.com/content/adobeforums/en/experience-manager-forum/adobe-experience-manager.to...

Did you create a package with the workflow model from /etc/workflow/models/dam/update_asset from a good server and install on it on the other server?

Hi Umesh,clustering is not possible with TarMK, you would have to use MongoMK. Please see [0] for the requirements for clustering and deployment options. Why do you want to use clustering? For high availability or to scale? For HA, you could use Cold Standby. Regards,Opkar[0]https://docs.adobe.com/d...

How did you get on Lakshmi?

Hi Kyle,it seams the behaviour you have seen is the OOTB behaviour as defined at[0]Just thinking out loud here but, what if you used a run mode that does not include the period character, such as "/etc/replication/agents.agentsprodauthor/repAgentName" and "/etc/replication/agents.agentsprodpublish/r...

Hi,just delete the attached files in your previous post as they have your ip addresses in them. You should really contact daycare about this or have someone with more experience of AEM help you, the following steps are not for an inexperienced person to carry out. IF you have two nodes in your clust...

Hi,It is the repository which needs to be unique, like I said it's nothing to do with the actual workflow, your repository is not configured properly.I have seen this issue when customers have cloned/copied an instance to create a new instance in the mongo cluster, have you done this recently?Is thi...

I have seen something similar before and it's not an issue with the workflow. You need to check the cluster topology, as this is used to distribute jobs in a cluster and if both of your author instances are not uniquely identified, then each author instance is behaving like a separate cluster, so ea...