BookmarkSubscribeRSS Feed
maubry
Obsidian | Level 7

Hi,

 

I'm a young SAS Administrator and my mission is to migrate 2 SAS Plateform into one. My design is the following:

  • 1 MetaData Tier
  • 1 Mid-Tier
  • 4 Computer Tier

Each tier is installed on a separate server due to some storage restrictions.

 

On Comp1, there will be libraries L1, L2, & L3 (datasets stored locally)

On Comp2, there will be libraries L4, L5 & L6 (datasets stored locally)

 

  • How the users can connect to a specific Compute? (permissions defined in the Management Console?)
  • If a user is connected to Comp2, is it possible for him to access to libraries on Comp1 ?

Many thanks for your help

 

Michael

4 REPLIES 4
gwootton
SAS Super FREQ
Is the intention for this to be a grid environment where the compute tier hosts have a shared configuration directory, and compute load is balanced among the compute hosts (i.e. connecting to SASApp Workspace Server results in a Workspace Server session starting on host 1, 2 3 or 4)? Or would each compute tier be a separate application server (i.e. SASApp on host 1, SASApp2 on host 2, etc)?
In a grid environment you can control workload placement based on resource requirement settings or queues. If each host has its own application server context, the user could select the context they want and thereby the associated host, but no load balancing would be present.
If a user was connected to one host and needed libraries that were local to another the path would need to be shared between them or some service would need to make them available remotely (i.e. SAS/SHARE, SAS/CONNECT Remote Library).
--
Greg Wootton | Principal Systems Technical Support Engineer
SASKiwi
Opal | Level 21

What OS is your SAS servers running on? Setting up folder shares between your SAS compute servers for the SAS libraries that are being shared is another possible approach as long as they are all running the same OS.

JackHamilton
Lapis Lazuli | Level 10

The same OS, or only compatible data representation?  We can read and write big-endian Solaris data sets from little-endian Windows through a mounted drive, but it uses Cross Environment Data Access and might not be efficient.  

 

In a grid environment, some shared file systems work better than others.  There's a SAS paper about it.  Expensive file systems tend to handle voluminous simultaneous updates from multiple systems better than the cheaper ones do.

Sajid01
Meteorite | Level 14

Hello @maubry 

You have two questions.
Q1 : How the users can connect to a specific Compute? (permissions defined in the Management Console?)

   The users connect through the metadata tier. 
Q2 :If a user is connected to Comp2, is it possible for him to access to libraries on Comp1 ?
Yes.


For a young and up coming administrator, with the questions you have asked in mind, I suggest that you read  the following references. They will server as a good starting point (in addition to the SAS documentation)
https://www.lexjansen.com/nesug/nesug11/ma/ma10.pdf 

https://www.sas.com/store/books/categories/administration/sas-administration-from-the-ground-up-runn... 

suga badge.PNGThe SAS Users Group for Administrators (SUGA) is open to all SAS administrators and architects who install, update, manage or maintain a SAS deployment. 

Join SUGA 

CLI in SAS Viya

Learn how to install the SAS Viya CLI and a few commands you may find useful in this video by SAS’ Darrell Barton.

Find more tutorials on the SAS Users YouTube channel.

Discussion stats
  • 4 replies
  • 544 views
  • 1 like
  • 5 in conversation