Hi all,
I am an analyst working on SAS (9.4) in a UNIX environment. We have our datacenter migration scheduled to happen some time soon. I am not into SAS administration, but I have been asked to do some basic testing for the migration. As an analyst, I am looking for a simple checklist to ensure that the migration is smooth from a SAS perspective and that I will be able to resume my programming/modeling activities without any issues once we move our SAS server to the new datacenter.
Thanks,
Krishna.
Theres actually lots of things to consider. I'll name a few that come to mind.
1. actual port of data between boxes - consider using proc copy and creating transport files.
see things like: transport documentation
2. ensure that the data you are porting is at least on a version of sas 8.0 or newer
3. consider GIT to store/back up code and then push/pull code between boxes.
4. track md5 sums between old/new boxes for data, code libs etc. You would probably want md5 sums on things like zips, tars, individual files too just to sample things.
this doesnt even cover sloppy code.
where someone has hard- coded paths specific to 'old box' which will no longer work in 'new box'.
you'd likely have transition issues that will come along with that.
those are my most immediate.
this doesnt cover performance testing and benchmarking between boxes to ensure that SAS is optimal on the new box.
hth
zeke torres
Theres actually lots of things to consider. I'll name a few that come to mind.
1. actual port of data between boxes - consider using proc copy and creating transport files.
see things like: transport documentation
2. ensure that the data you are porting is at least on a version of sas 8.0 or newer
3. consider GIT to store/back up code and then push/pull code between boxes.
4. track md5 sums between old/new boxes for data, code libs etc. You would probably want md5 sums on things like zips, tars, individual files too just to sample things.
this doesnt even cover sloppy code.
where someone has hard- coded paths specific to 'old box' which will no longer work in 'new box'.
you'd likely have transition issues that will come along with that.
those are my most immediate.
this doesnt cover performance testing and benchmarking between boxes to ensure that SAS is optimal on the new box.
hth
zeke torres
I'm assuming no change to your SAS software in this migration - is this correct?
I think you would need to do functional testing of your SAS jobs - confirm they still work without error.
Thank you, SASKiwi.
Yes, there's no change to the SAS software in the migration.
How do you plan to move your SAS server? Will you shut down the computer and physically move it to the new data center?
If not, please note that you need to make sure you do a full backup (clone) of the operating system and SAS deployment/configuration directories in the move.
Margaret
Thanks, MargaretC.
Our SAS admin will take care of the deployment/configuration.
The SAS Users Group for Administrators (SUGA) is open to all SAS administrators and architects who install, update, manage or maintain a SAS deployment.
SAS technical trainer Erin Winters shows you how to explore assets, create new data discovery agents, schedule data discovery agents, and much more.
Find more tutorials on the SAS Users YouTube channel.