Best Practices for Restoring Your SAS Content

Perform Full Restores

Like full backups, full restores are the best practice to follow to ensure that the metadata server returns to a consistent state and that metadata associations are correctly maintained. Full restores include the following:
  • the repository manager, all of your metadata repositories, and the metadata server's configuration files (including omaconfig.xml, adminUsers.txt, trustedUsers.txt, and logconfig.xml). If you use the metadata server backup facility to create your backups, then you can use the metadata server recovery facility in the event of a server failure. The recovery facility automatically restores the repository manager and all of the repositories that are included in the backup. You can also choose to restore the contents of the metadata server’s configuration directory and to perform roll-forward recovery to a specified point in time after the last backup was taken.
  • the SAS Content Server, the SAS Framework Data Server, and the physical files that are associated with the metadata. The metadata server recovery facility does not restore these files. Therefore, you must use operating system commands or third-party tools to restore them. For details, see Back Up the SAS Content Server and Back Up Data That Is Stored in File Systems.

Restoring an Unresponsive Metadata Server

The metadata server recovery facility can restore repositories only on a running metadata server. If your metadata server is not responding to client requests, then you must use operating system commands to restore the metadata repositories and the repository manager. For instructions, see What to Do If the SAS Metadata Server Is Unresponsive.