AEM Cloning

Cloning for author and publish instances is relatively simple. The steps below assume that the system getting the cloned instance has already had the AEM installation steps done which is normally the case.

• ●  Shutdown the instance being cloned
  
• ●  Make a backup of the instance (not the shared external datastore)
  
• ●  Start the original instance
  
• ●  Copy backup to new location
  
• ●  Remove old logs, thread dumps and any other junk left in the instance that is not needed
  
• ●  Remove the sling.id.file which contains the identity of the AEM instance. This step is v​ ery important!
  
  • ○  cd INSTANCE-DIRECTORY
    
  • ○  find crx-quickstart/launchpad/felix -name sling.id.file
    
  • ○  remove the above file once found
    
• ●  ensure /etc/sysconfig file for new instance is correct
  
• ●  ensure new instance directories and files has correct ownership of dam.damgrp
  Author Instance No special steps
  

0. Publish Instance
   Pause the replication agent from the author to the publish instances b​ efore starting the cloning procedure and ensure the queue is empty.
   If cloning when multiple publish instances already running and one does not want to stop all of the publish instances, choose one publish instance - but do not choose the publish instance doing the chained replication!
   
• ●  pause the replication agent for the chosen publish instance
  
• ●  create a new replication agent for the new publish instance being created and ensure paused
  
• ●  shutdown the chosen publish instance
  
• ●  clone as normal