Navigate
or
Contact Us
Subscribe Download PDF

How to upgrade the current version of ScaleArc to version 3.12

Rajendra Sharma
2017-10-16
0 Comments
in ScaleArc Registered User

 

How To: Upgrade ScaleArc Software Appliance

Release Classification Level DB Platform Categories
3.6.1 + How to

ALL Upgrade

 

QUESTION

How to upgrade the current version of ScaleArc to version 3.12.

ANSWER

This article explains the process to upgrade ScaleArc from a Current version to:

  1. ScaleArc version 3.12 GA for a Standalone machine 

  2. ScaleArc version 3.12 GA for a HA Pair of ScaleArc

 

 Upgrading to ScaleArc version 3.12 for Standalone Machine

 

There are two methods for upgrading ScaleArc from the UI:

  1. Upgrade using an URL file :
    This method is preferred when the ScaleArc server has access to the Upgrade Kit over the Internet or served from a local repository.
  2. Upload the PKG with MD5 Checksum
    This method is preferred when the ScaleArc server does not have direct access to neither the Internet nor a local repository. You must download the upgrade PKG file in prior to the upgrade.

Files necessary for the upgrade process:

You may need the following files in order to upgrade your ScaleArc. If you do not know the location to obtain each file, please contact to support@scalearc.com.

File Extension Purpose
{filename}.pkg This is the package file that should be uploaded to the ScaleArc server for an upgrade.
{filename}.md5 This file contains the MD5 checksum for the above package. This is a requirement for the upgrade process.
{filename} (URL file) This file contains the link to the 2 files listed above and can be used for direct URL upgrade.
 
NOTE: "{filename}" can be varied depending on which version your ScaleArc is upgrading to.
 
 
IMP NOTE: If the ScaleArc instance is launched on Cloud or a VM, please take a Snapshot of the ScaleArc VMs before upgrade. 
 
Before the upgrade process is initiated, please make sure the following settings are in place
 
Session Timeout
 
Session timeout occurring during the upgrade may interrupt your upgrade process. Please increase the Session Timeout Interval to a higher value, preferably 1 hour, while the upgrade process should not take more than 15 minutes to complete. The factors such as network latency can adversely impact the upgrade process.
 

     

 


** Upgrade from URL file

1. Navigate to Settings -> System Settings page.


     
 
2. Click "Update" to select "URL" as the Type and provide the link for URL copy link location and paste it over Enter URL, not the upgrade PKG file.
     
     
 
3. Click the "Upload" button

     
 
4. Uploading the package file is completed.

     
 
 
5. Click the "Apply" button. (ScaleArc instance will restart post upgrade.)
 
     

6. Click "Yes" to start the upgrade process. A pop-up that tails the Installer Logs is displayed during the upgrade process.

     
 
7. Upgrading requires the server to restart. You will see "loading data ..." while the server is rebooting.

     
 
8. After the server comes back, upgrade process is completed.

     
 
9. Click on Ok and ScaleArc login page will appear. Relogin to ScaleArc.

     
 
10. EULA page will appear requesting to enter you personal details, enter the information and read the EULA. Click on "Accept EULA" to proceed further.
 
     
 
11. Go to Settings >> System settings and Verify that the all versions are upgraded successfully. 

     
 
12. Upgrading your ScaleArc is completed

 

** UPGRADE from PKG file on your local computer:

 

1. Make sure the following entries are present in /usr/local/apache/php/php.ini

upload_max_filesize = 2G 

post_max_size = 2G

If the parameters need to be modified, idbweb service needs to be restarted

sudo service idbweb restart

 

2. Navigate to Settings -> System Settings page

     
     


3. Click "Update" to select "File" as the Type
     
     
 
4. Click "Select File" to browse for the downloaded ScaleArc-3.12.0-1892.pkg file on your local machine and type the ScaleArc-3.12.0-1892.md5 of the file.
 
    

5. Open the upgrade PKG file and provide its MD5 checksum values
 
     
 
6. Click the "Upload" button
 
     
 
7. Uploading the package file is completed.
 
     
 
8. Click the "Apply" button. This will require the loadbalancer to restart. Click "Yes" to start the upgrade process.
 
     
 
9. A pop-up that tails the Installer Logs is displayed during the upgrade process.
 
     
 
10. Upgrading requires the server to restart. You will see "loading data ..." while the server is rebooting.
 
     
 
11. After the server comes back, ScaleArc Upgrade is completed.
 
     
 
12. Click on Ok and ScaleArc login page will appear. Relogin to ScaleArc.

     
 
13. EULA page will appear requesting to enter you personal details, enter the information and read the EULA. Click on "Accept EULA" to proceed further.
 
    
     
 
14. Go to Settings >> System settings and Verify that the all versions are upgraded successfully. 

     

15. Upgrading your ScaleArc is completed 

  

IMPORTANT: Due to the larger package size the upgrade time may take an average of 25 minutes.

 

 Upgrading to ScaleArc version 3.12  from version below than 3.11 when machines are in HA

 

With ScaleArc version 3.12, there is a HA technology upgrade from the Linux-HA based heartbeat HA system to a pacemaker + corosync + CMAN based HA system. There is a slight variation in the way upgrades occur in version 3.12 GA when existing systems are configured in HA as compared to previous versions of ScaleArc. 

Prechecks:

The upgrade package checks for the correctness of the VIPs configured. A comparison is made between the network the VIP belongs to with that of the network the interface over which the VIP is configured on. If they do not match, the upgrade would fail at the pre-check stage. If this occurs, it is important the user corrects it before proceeding with the upgrade. 

Prior actions:

ScaleArc has determined that there is a minor problem involving the use of /dev/random during the HA configuration phase of the upgrade, and has developed a workaround. Prior to applying the upgrade, please complete the following procedure to ensure that your upgrade will not appear to hang during this phase. Should you be uncomfortable with Linux command line commands or desire assistance, please don't hesitate to contact ScaleArc support and we will happily assist you.

  1. Install the rng-tools package with YUM: sudo yum install rng-tools Note that this requires open Internet access or a pinhole in your firewall for YUM to access the repositories online. If you are unsure how to proceed with this, the YUM install fails, or you need assistance in evaluating how to configure your firewall to permit this operation, please stop at this point and contact ScaleArc Support for assistance.
  2. Automatically edit the rngd configuration file: sudo perl -p -i -e 's/EXTRAOPTIONS=""/EXTRAOPTIONS="-r \/dev\/urandom"/' /etc/sysconfig/rngd This should create the /etc/sysconfig/rngd file. You may verify this with the ls command.
  3. Enable the rngd daemon for startup in the appropriate init states: sudo chkconfig rngd on This should add rngd to init states 2, 3, 4, and 5. This can be checked with sudo chkconfig --list | grep rngd which should show rngd being on in the appropriate init states as stated.
  4. Start the rngd daemon: sudo service rngd start This can be verified with ps
  5. sudo service rngd stop and disable it: sudo chkconfig rngd off as the service has not yet been fully verified to be compatible with ScaleArc during runtime by our QA team. In a near-term future upgrade we expect to complete this testing and this service will probably become a permanent fixture in the product but for safety's sake, we recommend disabling it for now.

Upgrading a ScaleArc system already configured in HA

Note: Like previous upgrades, it is recommended to upgrade the secondary system first. However, unlike previous upgrades, after the upgrade the secondary machine will automatically assume the role of the primary. Please note that upgrading the secondary first for this release is mandatory. 

To upgrade a ScaleArc system (pre version 3.11) configured in HA:

1. Upgrade the current secondary system using any of the processes mentioned above for the standalone Instance.  Once the upgrade is complete on the Secondary ScaleArc, the machine will reboot.

2. After the reboot, the secondary machine will become the primary and start processing traffic. The original primary machine at this point will appear in a non operational state where HA services are disabled. As a result, the machine will not be capable of handling traffic. 

Note: At this point, HA operations such as "Become Secondary, Force to be Primary" will not be available. 

3. Once the upgrade is successful, repeat the upgrade steps on the old primary machine.

4. After a reboot, the primary will join as a secondary machine into the HA pair.

IMPORTANT: ScaleArc 3.11 introduces fence configuration to resolve split brain situations. This is a mandatory HA configuration which is not automatically configured after an upgrade.

 

Upgrading to ScaleArc version 3.12  from version 3.11 & above when machines are in HA

 Prechecks:

The upgrade package checks for the correctness of the VIPs configured. A comparison is made between the network the VIP belongs to with that of the network the interface over which the VIP is configured on. If they do not match, the upgrade would fail at the pre-check stage. If this occurs, it is important the user corrects it before proceeding with the upgrade. 

Note: It's recommended to upgrade the primary machine immediately after completing the secondary machine upgrade. Without this step, primary machine will not be unable to take over in case secondary machine fails.

To upgrade a ScaleArc system (version 3.11+) configured in HA:

1. Upgrade the current secondary system using any of the processes mentioned above for the standalone Instance.  Once the upgrade is complete on the Secondary ScaleArc, the machine will reboot.

2. After the reboot, the secondary machine will come up as secondary in a non operation state. Perfrom HA Switch to make this machine as Primary and in Operation state to handle traffic.

3. Upgrade the earlier Primary System (Current Secondary) using any of the processes mentioned above for the standalone Instance. Once the upgrade is complete on this the machine will reboot and come up a secondary scalearc machine.

4. If you want the earlier Primary machine to handle traffic perform an another HA Switch to make it primary. (Optional)

For more information on fence configuration refer to the ScaleArc Guide.

 Related links: 

ERROR: NV failure

 

If you are experiencing issues with ScaleArc or with any of it's features, please contact ScaleArc Support. We are available 24x7 by phone at 855 800 7225 or +1 408 412 7315. For general support inquiries, you can also e-mail us at support@scalearc.com.

Copyright ©2017 ScaleArc, Inc. All rights reserved. Contact Support |  Contact ScaleArc |  Feedback

2901 Tasman Drive Santa Clara, CA 95054 | Email:  support@scalearc.com

 

 

 

 Permalink: https://support.scalearc.com/kb/articles/4437