Expand my Community achievements bar.

Guidelines for the Responsible Use of Generative AI in the Experience Cloud Community.
SOLVED

Code Deployments for Standby (cold-standby) server on AEM 6.3

Avatar

Level 3

Hi Experts,

We’ve setup the Cold-Standby for AEM 6.3 Author environment. Everything is working well – content segments/binaries synch up, logs are ok etc. Main Author server is in Primary mode, Secondary Author is in Standby mode. Have I’ve below BAU deployments related question and need your experience/feedback -

Use Case: Say there is a Release1 happened on Primary Author, the same needs to be deployed on Standby Author to keep both servers in sync in terms of code as well.

Question: -

  1. We are using some shell scripts (which internally uses curl) to upload and install the packages in AEM from backend. Can we do the code deployment on Author server when it running in Standby mode? 
  2. Cold-Standby syncs the content through TarMK segments which can be content/code – Do we really need to worry about code deployment on Standby or this will also be synced automatically?
  3. If above #1 and #2 doesn’t hold good – Do we need to restart the Standby server in Primary mode and deploy the code build every time and once it is done, the server will be restored in Standby mode?

Any pointer will be a great help, thanks!

1 Accepted Solution

Avatar

Correct answer by
Level 8

Yes, you can deploy code deployment in the primary server, once the deployment is completed it will automatically sync with the standby server.

You do not need to make standby server as the primary server, this we use only in DS

We suggest you take backup of author instance also. because when author instance is corrupted by new package deployment or service pack installation or accidentally deleted some content then it will be immediately replicated to standby instance

View solution in original post

1 Reply

Avatar

Correct answer by
Level 8

Yes, you can deploy code deployment in the primary server, once the deployment is completed it will automatically sync with the standby server.

You do not need to make standby server as the primary server, this we use only in DS

We suggest you take backup of author instance also. because when author instance is corrupted by new package deployment or service pack installation or accidentally deleted some content then it will be immediately replicated to standby instance