Skip to main content
This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Surabhi_Katiyar
Surabhi_KatiyarAccepted solution
Adobe Employee
April 12, 2022

Hi,

 

If this is AEM as a Cloud Service environment, then you can raise a support ticket to get the production environment rolled back. For more information you can follow the below document:

 

https://experienceleague.adobe.com/docs/experience-manager-cloud-service/content/operations/backup.html?lang=en

 

One more option is you can revert your branch to a stable code version and then deploy the pipeline again.

View in thread

5 replies

Anish-Sinha
Adobe Employee
Anish-SinhaAdobe Employee
Adobe Employee
April 12, 2022

HI @aem-enthu27 ,

Are you referring to AEM as cloud service?

If so, there is no rollback needed if the deployment fails. If the deployment is successful, then only your newly created AEM instance is exposed and replaced with the old one, If the build fails, you system is already in place which is the previous stable version. No need to do anything to stabilize the instance. About the code, you will have to revert the changes to prod branch in order to have environment and code in sync.

Translate
    aem-enthu27Author
    Level 4
    April 12, 2022

    So if build fails bcz of any reason, site will not be down as it is not yet deployed. But after successfull deployment if you feel build is not stable and some of the functionalities are not working propeerly then we can go for rollback. Is my understanding correct?

    Translate
      Anish-Sinha
      Adobe Employee
      Anish-SinhaAdobe Employee
      Adobe Employee
      April 12, 2022

      Yes. That is the exact use case here. However, stage and prod are identical servers, so if any changes are pushed, you can keep it on stage verify it completely and then promote. If you still need to roll back, you have to raise Adobe ticket. Please find the details here - https://experienceleague.adobe.com/docs/experience-manager-cloud-service/content/operations/backup.html?lang=en#

       

       

        

      Translate
        Surabhi_Katiyar
        Adobe Employee
        Surabhi_KatiyarAdobe EmployeeAccepted solution
        Adobe Employee
        April 12, 2022

        Hi,

         

        If this is AEM as a Cloud Service environment, then you can raise a support ticket to get the production environment rolled back. For more information you can follow the below document:

         

        https://experienceleague.adobe.com/docs/experience-manager-cloud-service/content/operations/backup.html?lang=en

         

        One more option is you can revert your branch to a stable code version and then deploy the pipeline again.

        Translate
          PhaniRajuTanneru
          PhaniRajuTanneru
          Level 2
          April 12, 2022

          Hi,

          If you are doing deployment manually or CM pipeline there is no automate to revert the code. Usually as part of deployment plan , will take the back up. if you are through CM Pipeline back up will took by pipeline automatically.

          If the build is failed. Have to roll back the backup package to reinstall.

          Translate
            Terms & ConditionsAccessibility statement

            Loading footer...