SAS 9.1.3 Intelligence Platform: System Administration Guide

Planning SAS Metadata Server Backups and Restores R Using Alternating Backup Locations 47
Backing Up Configuration Files
In order for the metadata server to function properly, the following configuration files
must be present: omaconfig.xml, adminUsers.txt, and trustedUsers.txt. You
should include these files as part of a full backup or full restore. Since %OMABAKUP
does not back up or restore these files, you must use operating system commands or
third-party tools.
Backing Up Associated Data
When you back up the metadata server, it is important to also back up the data that
is associated with the metadata objects that are contained in the repositories. The
metadata cannot be used without the associated data. If you need to recover from a
failure, the metadata that you restore must be synchronized correctly with the
associated data.
Your backup strategy should include the following data:
3 content that is stored in WebDAV repositories, including portal content, report
definition files, and other supporting files for reports (for example, PDF files and
image files). Depending on your installation, the report files might be stored in the
file system instead of WebDAV.
3 other portal content, including custom portlets, custom themes, and applications
3 source files for stored processes
3 packages that have been published to a channel’s persistent store (archive) location
3 stored process results that are stored in permanent packages
3 data sources, including the following:
3 SAS tables
3 OLAP data
3 SAS Scalable Performance Data Server data
3 RDMS data sets
3 custom code, processes, and postprocesses that are associated with SAS Data
Integration Studio jobs
3 XML files and XML maps that are contained in libraries
3 source files for SAS Data Integration Studio jobs that have been scheduled or
deployed for scheduling
Since %OMABAKUP does not back up or restore these types of data, you must use
operating system commands or third-party tools.
Using Alternating Backup Locations
To help safeguard the integrity of your backups, consider alternating backups to
multiple backup locations. For example, you might alternate backups to different
network-accessible drives, depending on the day of the week. Then if backup files
become corrupted, or if a backup host is damaged, you can restore the SAS Metadata
Server from another location. For a sample backup script that uses this method, see
“Example: Backup Program on Windows, Using Alternating Destinations” on page 54.