Updating the Server OS of the SAS servers

[abhisheksircar]

I have a distributed deplyoment if SAS (production environment) installed on Windows server 2008, now the organization requires to update the OS to 2012. What is the best way to do it without affecting the existing deployment?

[Kurt_Bremser · Accepted solution]

Set up new servers, install the latest SAS release/maintenance level available, and transfer the content. Once the new environment is tested, switch your users over.

That is the basic pattern I always follow. I only do SAS maintenance levels and OS hot fixes "in place". And I have a very stable operating system (AIX), where hotfix updates tend to be a breeze and rarely require a reboot.

[abhisheksircar]

Thanks Kurt.
I understand that it is the best way to do it, but due to infrastructure limitations, I will not get the new servers as long as I have the existing ones.

[SASKiwi]

I suggest you track this question to SAS Tech Support. They are in the best position to give you a definitive answer. I would be very surprised if this would work without any problems.  

[Kurt_Bremser]

What you want to do will mean complete downtime of SAS services while the systems and software are installed. Especially with Windows, the environment undergoes a deep-rooted change, so you can't expect that a simple update-in-place works.

Make your "IT people" aware that not providing you with proper new hardware might mean a service disruption of weeks in the worst case, or at least a very busy weekend, with no guarantee that you're up and running on Monday. 

[abhisheksircar]

Thank you for the replies.
As these are production servers, we cannot afford to have a service disruption bof multiple days. So instead I am pushing for new servers and once I am done with Installation and Configuration the "IT people" will decommission the old servers.

Also, I was wondering if SAS Migration Utility will be helpful in moving the configuration?

[jklaverstijn]

Hi @abhisheksircar,

The SAS Migration Utility (SMU) can certainly help. But is a mixed bag. As a rule it is only effective if you are migrating to a same platform and topology. I would assume that going from eg Windows Server 2012 to 2016 that would count as "the same platform". The SMU has a prepare/analyze function that will tell you if there are any pittfalls in your current deployment that would prevent the SMU from being effective. I would start there.

If you also take the opportunity to bump your SAS version or product mix there are also possible limitations. I would check with SAS Support to discuss your specific environment for the nitty gritty details.

All migrations I've done (and there were a few) were changes in topology or platform, either Windows to Linux or 32bits to 64 bits and SMU would be a big help. Your case likely has a better chance.

Regards,

-- Jan.

[Kurt_Bremser]

I have never used the migration utility myself.

I always set up a completely new environment and used the opportunity to correct design mistakes I had made in the previous metadata setup.

Where it was possible, I used a simple export/import of packages to move parts of the metadata.