Architecting, installing and maintaining your SAS environment

Upgrade in Place Steps

Posts: 25

Upgrade in Place Steps

Hello All,


We are currently running SAS 9.4 M3 (SAS Studio 3.5) and have received software order for SAS 9.4 M5 (SAS Studio 3.71) from SAS. We would like to do an upgrade in place. Can you please let us know what are the steps involved? I tried checking the Tech notes but it does not tell me if I have to upgrade the depot or how to begin with?


Just the basic high level points should allow me to start with the upgrade.


Thanks in advance.

SAS Employee
Posts: 22

Re: Upgrade in Place Steps

Posted in reply to shirishkamath

Instructions for updating SAS 9.4 to a later maintenance release are in the SAS® 9.4 Guide to Software Updates document. Not all sections may apply to your type of installation, but it's best to review the whole document so you can determine the best approach for updating SAS software at your site.


Here's a broad overview of the process:

  1. Download the new SAS 9.4M5 order. You can download it to the existing SAS Software Depot (containing the 9.4M3 order) or you can create a new depot. The benefit of downloading it to the existing depot is that only updated files will need to be downloaded - any depot files that did not change between M3 and M5 will not need to be downloaded, meaning that the download time can be reduced.
  2. Make sure you have prepared the environment as outlined in SAS® 9.4 Guide to Software Updates, including creating usable backups in order to restore customization after the update has been applied. This is essential for planned deployments.
  3. Follow this page of instructions to apply the update.
SAS Employee
Posts: 61

Re: Upgrade in Place Steps

[ Edited ]
Posted in reply to shirishkamath

Here are some quick tips that are not explicitly written into the documentation that I've seen trip users (including myself) up -


1- Backups backups backups.... Make sure you have a bullet proof roll back strategy before you start in case anything goes wrong.

I've seen first hand cases where things like power outages occurign midway through an upgrade in places leave the system in an unsalvageable state. Ensure you have a way of getting all hosts in the deployment back to the state they were in before the update started.


2- Test everything you need have working is working before you start the upgrade.  You need to be confident you have a health environment before you start the upgrade. Often we'll see users identify major issues after an upgrade, we roll the system back to the backups before the upgrade was applied only to find the issue was still present before the update took place.


3 - Consider if there are any post-installation configuration updates that might impact the upgrade. eg. Was TLS/SSL manually configured after the SDW finished. Changes like this should be reverted so that the state of the system is what the SDW expects.


- Test : Make sure everything you need to have work is working

- Backup : Put a safety net into place. Should anything go wrong you will always be able to get back to working state

- Take stock of your deployment : Revert changes that were manually introduced that might stop the SDW performing updates

- Follow the docuemntation : Go through the docuemtnation and follow it to actaulyl perform the update

- Test... again... : Make sure everything you need to have working is still working

- Make a go/no-go decision : if everything is working you can keep the current setup and remove backups, ifs not working you need to decide if you troubleshoot or rollback

Ask a Question
Discussion stats
  • 2 replies
  • 3 in conversation