Our Environment: Windows, 3 application servers total - Enterprise Guide 2 VM's, one Metadata Server, one Web server 1 Physical server - Compute / App server - 278GB RAM C drive: 15gb free of 100GB D drive: 162GB free of 179GB <--- This is where the app is installed SASWORK points to E drive, which is 5TB of SAN DISK Users log into Enterprise Guide via Citrix to access SAS   Our hardware group contacted me the other day to let me know that the C drive of the Compute server had a 55GB pagefile. C drive is normally at about 50-70% free. I realize our C drive is small, but since we were directing all SASWORK to the E drive, we were told by SAS that our configuration worked.   A few questions - What is using the C drive if the SAS Application is installed on D, users access it via Citrix and SASWORK points to E (SAN disk)? Why is the application paging if RAM is so high on the server, but heavily unused? Though the recommendation for the Page File is usually 1.5X RAM, in our case, our C drive can't handle that since RAM is very high at 278GB yet the C drive is very small. The idea was that we wouldn't use C at all. How should we set our Page File size? Or should we still set the Page File to 1.5X RAM, but put it on the SANDISK? Keep in mind that our configuration, though not ideal, was approved by SAS, so at this point, we can't just get a new server or add space to C - this server can't be expanded anymore, so if there are any other ideas on what we can configure or look at, I'd be glad to hear it! ... View more

We recently migrated from SAS on Linux to SAS on Windows.  We're currently working with a contractor to try to track down potential issues (we see large differences in Total CPU to User + System CPU, but nothing pointing to actual bottlenecks with storage).    Users are indicating that jobs that took 20-30 minutes on Linux take upwards of 45 minutes on Windows.  That seems logical to me, considering we went from an extremely high powered Linux server where storage and jobs, Metadata, Compute and Web were all running on the single server.  We now have SAS spread across 3 servers (2 are VM's) with SAN storage. The pro's are the users ability to more easily work with windows aspects (actual paths, login with their windows ID's, etc).  Con's are performance hits.    We are using SAS Enterprise Guide from Citrix servers and the users are reading from large Excel files. Their datasets are anywhere from 50GB to 200GB.   What expectations could we set for them logically in terms of moving from Linux to Windows?  We've told them "it WILL be slower", but how much is too much?    ... View more

My environment: Suse Linux Backend, Windows user tools (EG)   Question:  I want to set up a nightly script on our Linux server to do maintenance.  I'm going to include running the cleanwork utility to get rid of rogue saswork sessions, along with some general housekeeping.  I have a list of all the common logging directories, and I'm going through each one to inventory the files that are there, in addition to deciding on a reasonable rule for each directory (ie: delete all old log files over 60 days, etc).     I can tell what I'm looking at with the SAS Server Logs (object spawner, etc) and I feel comfortable making that decision. There are some logs that I am not familiar with and I don't want to "rip the rug" out from under the process, so to speak, if that log is in some way needed.  I am mostly wondering about any logging related to Environment Manager, Perf and Audit Logs.  Are there any logs that I absolutely shouldn't touch and let them continue to accumulate?   Here are a few specific examples that I'm wondering about: Lev1/ObjectSpawner/AuditLogs Lev1/WorkspaceServer/PerfLogs /Lev1/Web/SASEnvironmentManager/emi-framework/Logs/ acm*, getMetricData*, masterAPMETL*, /Lev1/Web/SASEnvironmentManager/emi-framework/Archive/logs_processed_date.zip Lev1/Web/SASEnvironmentManager/emi-client/Logs logDiscovery*, logCollect*,  /Lev1/Web/SASEnvironmentManager/agent-5.8.0-EE/log/agentstats agentstats*.csv.gz I could keep going with this, but I think you get the picture.  I'm only worried about the locations where there isn't a built-in log cleanup and I'm not sure if it's safe to delete some things.  Generally I wouldn't even think to delete anything that obviously didn't have a recurring log with several months of existing old files.  I'm not talking about anything current - just old stuff that could free up space.     We are a newer SAS site and I have not used these boards as much as I should, so I hope this is the appropriate place to post this and I hope I am not duplicating an already asked question.  I've done several searches and found a few articles, but nothing that answers my specific question.     Thank you! ... View more

We have our SAS client apps (Environment Manager, Management Console, Personal Login Manager) on Citrix servers so users from all over our organization can access them.  With Environment Manager and Management Console, we created a single default profile that includes the SAS Server name in it so users don't have to enter it each time. Otherwise, they enter it and then it gets deleted upon logout because of the way our Citrix settings purge local workspaces.    I have been unable to figure out how to set up a shared default profile for the Personal Login Manager.  With Environment Manager, we were have an actual share and can update it as needed (if we add additional servers, etc).  We point the SDSControl.xml file on the local server to the shared location where the profile exists.  With Management Console, we don't exactly have a share, but the profile is stored on each server under  C:\ProgramData\SAS\SharedSettings and we added a Java Argument into the sasmc.ini to point to that location ( JavaArgs_17=-Dsas.appdatapath="C:\ProgramData\SAS\SharedSettings).   For Personal Login Manager, that doesn't seem to work.  The default place where the app is looking is the c:\users\username\AppData\Roaming\SAS location, which gets purged upon logout. This requires us to re-create a connection profile everytime we log in. I tried adding the same JavaArg as above to the mrloginmgr.ini and no luck. Something keeps telling the app to look in the users local profile each time.   What am I missing here? I had to play around quite a bit with the Enterprise Guide and Manager Console to get that function to work, but since it isn't seeming to follow the same rules that I applied above, I'm at a loss.  Has anyone dealt with this before? ... View more