And you have an active replication agent? And whatever you publish actually gets replicated?

Not really sure what you mean with "collect and upload individual content" (a package?), but you can use blueprints to have a common base for all microsites and create live copies of it for every microsite. This way, when you edit the blueprint and roll out the changes, all the microsites are update...

Does your parsys allow that specific component to be added as a child component?

A distaster recovery plan can never be "one-fit-for-all". It's specific to the setup of your environment(s). All you can do is gain knowledge on AEM and make a plan of your own to make sure that whenever things could get wrong, you're not the one getting fired because you can't handle the situation ...

A little bit of Google would have brought you to this article:AEM Infrastructure Series: Disaster Recovery Basics | Adobe

Previously, the term "revision cleanup", basically was compaction. The terminology has changed and compaction is now a part of the revision cleanup process. It says this in the documentation for AEM 6.3:The revision cleanup process consists of three phases: estimation, compaction and clean up. Estim...

You should try using the @ChildResource annotation instead of @Inject

Try adding the immediate = true to the @Component annotation of your JobConsumer

Yes, I understand what the case is here. Still, I would recommend to add the components to the template. If you do this, you can call the PageManager to create a page with your specific template for all of the pages on your legacy system. This way, the new created page will have the components avail...