For customers who download SAS, their
SAS Software Depot is the only copy of their SAS order. The depot contains the files from which SAS
is initially installed. For this reason, it is important to use these best practices
when managing your depot:
-
When you keep your
SAS 9.4 depot, applying maintenance and upgrades becomes easier because
you have to download only the changed depot files instead of downloading
an entire SAS order.
-
Locate in an empty directory.
Create or download your depot into an empty directory that will not be the future
location of the
SAS installation directory (SASHOME).
-
Perform routine backups.
As with your SAS production system, it is important to routinely back up your SAS
Software Depot and to verify the integrity of these backups.
Note: Another important reason
for securing and backing up your SAS Software Depot is that there
are limits on the number of times that you can download your SAS order.
-
Secure the depot location.
Problems such as data
loss, virus infection, and file corruption can compromise your investment
in SAS. It is imperative that you have a comprehensive security policy
in place to protect your depot.
-
Store SAS installation data files
with your depot.
The
SAS installation data file for your order contains information that is integral to successfully deploying SAS.
As you get renewal installation data files from SAS—such as the file that contains
your permanent SAS license key—it is important that you store them with your depot
in the
sid_files directory.
CAUTION:
Be careful
to use the correct installation data file that contains the SAS products
that you are planning to install. Using an incorrect file can cause
failure when installing SAS add-on products or other errors later
when attempting to run SAS.
-
Create a SAS Software Depot administrator.
Consider designating one or more users to serve as SAS Software Depot administrators.
Users needing to deploy SAS software or to apply maintenance require
depot Read and Execute privileges. Depot administration tasks such as initially creating
the depot, storing SAS installation data files, and updating order details require
depot Write privileges. Separating depot administration from routine depot usage is
a best practice that further protects your SAS Software Depot.