none
How to Perform a Rollback in FAST ESP 5.3 ? RRS feed

  • Question

  • Hi All,

    Has anyone worked on FAST ESP 5.3 Rollback feature ?

    Let's say there is a build or deployment of the latest solutions and this build does not work properly for some reasons.

    At this time, how can we Rollback to its previous build or deployment in FAST ESP 5.3 ?

    Please guide on this issue soon.

    Thanks,

    Ajay Shivarathri

    Friday, July 15, 2011 6:37 AM

Answers

  • Hi Ajay,

     

    The Update Installer Guide describes the rollback feature.  One thing to keep in mind about the rollback feature is that it will only uninstall the most recently applied patch.  I have copied the pertinent details from the guide:

     

    Rolling back

    This topic describes the steps required to roll back a patch or service pack to a previous state using the ESP Update Installer.

    Important: Make sure that ESP is not running before you start to roll back a patch or service pack.

    1. Run the ESP Update Installer executable. The installer runs in GUI mode by default. To run the installer in console mode, add the -console command line option.

    a) Windows: In Windows Explorer, navigate to the folder where you unzipped the patch/service pack, and double click setup.exe.

    b) Linux/Solaris: Open a (bash)shell on the server and run these commands:

    $ cd $FASTSEARCH/bin

    $. setupenv.sh

    • Navigate to the directory where you unzipped the patch/service pack, for example:

    $ cd /home/fast_patch/

    $ setup_Linux.bin

    2. When prompted, select Rollback patch.

    3. Provide the path to your ESP installation.

    4. Select single node rollback or multi node rollback.

    • For a single node rollback, the Update Installer will find which patch or service pack (if any) was the latest one installed, and select this as the rollback candidate.

    • On a multi node installation, the Update Installer finds the latest installed pack or service pack on all hosts and selects the latest installed as the rollback candidate. It will then attempt to rollback the patch or service pack candidate only on those hosts where this patch or service pack was the latest installed patch or service pack. For multi node rollback, an approval screen will appear displaying which patch or service pack was found to be the latest one installed, and on which hosts this will be rolled back.  Click Next to continue the rollback.

    5. The Update Installer will first pre-check (on all hosts it will perform a rollback on) that there have been no modifications to the files that are to be patched. If any of the files have been modified, a new screen will appear with a notification. Click Next to approve modified files to be overwritten.

    Note: Modified files: The installer will always check to see that the state of the ESP installation is consistent with its current patch or service pack level. The update tries to roll back the latest installed patch or service pack. If successful, a confirmation will be given. If not, the cause of why the patch or service pack could not be rolled back, will be displayed. In case of an error, your ESP state will be the same as it was before you started the rollback, regardless of when the rollback failed.

     

    On multi node rollback, the rollback status on each node will be displayed. If some nodes fail, check the fastinstall.log on the individual node to try and solve the problem. It is possible to do another multi node rollback after the problem is solved. In this case, the patch or service pack will only be attempted rolled back on those nodes where it is not yet uninstalled.  For further verification, check FASTSEARCH\var\installer\patch-history.xml.

     

    You can rollback a patch, or a service pack, one at a time, all the way to the base version release that was installed in the environment.  Let us know if you have questions.

     

    Thanks!  

    Rob Vazzana | Microsoft | Enterprise Search Group | Sr Support Escalation Engineer |  http://www.microsoft.com/enterprisesearch 

     

     

    Monday, July 25, 2011 9:26 PM
    Moderator

All replies

  • Hi Ajay,

     

    The Update Installer Guide describes the rollback feature.  One thing to keep in mind about the rollback feature is that it will only uninstall the most recently applied patch.  I have copied the pertinent details from the guide:

     

    Rolling back

    This topic describes the steps required to roll back a patch or service pack to a previous state using the ESP Update Installer.

    Important: Make sure that ESP is not running before you start to roll back a patch or service pack.

    1. Run the ESP Update Installer executable. The installer runs in GUI mode by default. To run the installer in console mode, add the -console command line option.

    a) Windows: In Windows Explorer, navigate to the folder where you unzipped the patch/service pack, and double click setup.exe.

    b) Linux/Solaris: Open a (bash)shell on the server and run these commands:

    $ cd $FASTSEARCH/bin

    $. setupenv.sh

    • Navigate to the directory where you unzipped the patch/service pack, for example:

    $ cd /home/fast_patch/

    $ setup_Linux.bin

    2. When prompted, select Rollback patch.

    3. Provide the path to your ESP installation.

    4. Select single node rollback or multi node rollback.

    • For a single node rollback, the Update Installer will find which patch or service pack (if any) was the latest one installed, and select this as the rollback candidate.

    • On a multi node installation, the Update Installer finds the latest installed pack or service pack on all hosts and selects the latest installed as the rollback candidate. It will then attempt to rollback the patch or service pack candidate only on those hosts where this patch or service pack was the latest installed patch or service pack. For multi node rollback, an approval screen will appear displaying which patch or service pack was found to be the latest one installed, and on which hosts this will be rolled back.  Click Next to continue the rollback.

    5. The Update Installer will first pre-check (on all hosts it will perform a rollback on) that there have been no modifications to the files that are to be patched. If any of the files have been modified, a new screen will appear with a notification. Click Next to approve modified files to be overwritten.

    Note: Modified files: The installer will always check to see that the state of the ESP installation is consistent with its current patch or service pack level. The update tries to roll back the latest installed patch or service pack. If successful, a confirmation will be given. If not, the cause of why the patch or service pack could not be rolled back, will be displayed. In case of an error, your ESP state will be the same as it was before you started the rollback, regardless of when the rollback failed.

     

    On multi node rollback, the rollback status on each node will be displayed. If some nodes fail, check the fastinstall.log on the individual node to try and solve the problem. It is possible to do another multi node rollback after the problem is solved. In this case, the patch or service pack will only be attempted rolled back on those nodes where it is not yet uninstalled.  For further verification, check FASTSEARCH\var\installer\patch-history.xml.

     

    You can rollback a patch, or a service pack, one at a time, all the way to the base version release that was installed in the environment.  Let us know if you have questions.

     

    Thanks!  

    Rob Vazzana | Microsoft | Enterprise Search Group | Sr Support Escalation Engineer |  http://www.microsoft.com/enterprisesearch 

     

     

    Monday, July 25, 2011 9:26 PM
    Moderator
  • Hi Rob,

    Thank you for all help. Found this information very useful.

    Regards,

    Ajay

     

     

    Tuesday, July 26, 2011 6:15 AM