I will try and answer your questions to the best of my knowledge. This oculd become a long post. There is so much detail involved in a solid grid implementation that you may consider to call in the troops (from SAS or otherwise) to iron out the last wrinkles. There is a good chance my answers will give rise to even more questions. Please understand that this platform may not be the place for an in-depth grid implementation workshop. But I will give it a shot.
Is the SAS servers stop and start order is correct which I mentioned in my previous email?
There is a chapter in the SAS docs that recommends a certain order. Yours looks fine. Some servers can be started at the same time (the grid nodes) but that's a minor detail. Actually the grid nodes do not run more than a tiny LSF service and the environment manager agent; no spawners live here. The evmgr agent can be stopped/started at will.
Do I need to take backup of all files including SASHome, platform(gmsinstall, Sharedgrid, lsf,pminstall...etc) along with config files of all servers(Metadataserver,Grid master & Midtier) (or) just grid master is enough since am running setup file on SAS grid master.
Taking a backup is (almost) always a good idea. In your specific case, adding a server context, You could limit yourself to a metadata backup taken from SAS Management Console (smc) just before lanching sdw. It's just so much easier to roll back in case of mistakes.
And when it asks for option in the windows clicking Next during my configuration do I need to select existing config lev1 which is in our current grid master location
Never just click next. Always check what's there. And yes, you use the same config/Lev{n} as before. I just commented on this casually as I think most screens prompt you for info that you have seen before and are not special in the context of your case. The screens are pre-filled from previous sdw runs and will usually make sense, just don't count on it.
and also in my requirement am supposed to setup the saswork and sasutil files for the new Appserver,where do i need to setup these,do i need to setup in SMC or in Server.
Usually (not always! You can do it at SASHome which many frown upon) work/util locations are defined in the sasv9_usermods.cfg at server context level (eg. SASConfig/Lev1/SASApp). You will have to redo that for the new server. Up to you if you need a new location or reuse the same. It largely depends on why you need a new server context if you want to separate these.
You mentioned in your previous email saying that "We work according to the best practice of sharing the SASConfig between all grid nodes, in which case this would the only time you need to run the SDW". (so what exactly you mean when you are saying I need to run SDW)....For your information our Grid Master and Nodes are in NFS for Install and config directories
We also use NFS for that. And we mount the same SASConfig location on each and every grid node including the master. This works very well but the devil is in the details. Eg. the env mgr agent writes a file called .pid at startup so each node overwrites that file fro the previous one. The environment manager will loose track of the status of the agents. That can be helped by splitting the config directory in one for each node. SAS Support should be able to provide a a script to help. Another consequence is that you can't run SDW to configure every grid node separately. So there is no way to add the workspace servers to the metadata but manually. Unless you use grid launched wss exclusively there is no escape. By the way NFS proves very problematic for us. We are in the process of implementing GPFS for that.
Do I need to select OLAP and connect server also as part of the this new app server context configuration (or) I can use the previous OLAP and connect server components for the new SASApp server.
and coming to port numbers I think for OLAP and Connect server i should use unique port numbers not the same port numbers which we used in our default application server and port numbers for workspace servers and pooled wss and stored process sever I believe we can use the same previous port numbers or new port numbers if am not wrong.
but in case If i have to use new port numbers for all the server components of new SASApp Server,do I need to use the next sequence number of the existing port numbers of server components in default application server or it's something different.
You can use the existing ones. Normally the sdw will propose new port numbers that increment in the last or one-but-last digit. Some planning upfront will never hurt but the minimal requirement is to keep them unique.
and to Save a response file for later reference I believe below is the command right for the response file to
./setup.sh -deploy -record -responsefile /path to response file/respfile.txt
Yes that's how it's done. The filename should (on Unix/Linux at least) be an absolute path name.
I hope this helps you on your way. The grid architecture can be a bit daunting in the beginning but the rewards are many. Good luck.
Regards,
- Jan.
... View more
