Providing software solutions since 1976

• Log in
• Create profile
• Welcome
  [Log out]
• Edit profile

• Print  |
• Feedback  |
• Share

  • E-mail

  
  
  

  E-mail This Page

  Your Name:*
  Your E-mail:*
  Recipient E-mail:*
  Send a copy to me
  Personal Message:
  
  

  * indicates a required field

Because the metadata server process locks tables when it is active, it is necessary to properly pause the server before you run a backup of the metadata. Normally, running the %OMABAKUP macro is sufficient for this task, because it submits the METAOPERATE procedure to pause the repositories before it begins to make the backup copies.

However, if your metadata server is configured to run in a Microsoft Windows 2003 Failover Cluster environment, %OMABAKUP will likely fail with errors similar to the following:

Note that the name of the data set might vary.

This error occurs because when the %OMABAKUP macro pauses the metadata server, the Cluster Service will attempt to restart it. If it succeeds, by the time the %OMABAKUP macro begins copying the tables to the backup location, the server is again running and has locked the tables.

To circumvent the problem, you must first take the group offline using the Cluster Administrator or CLUSTER command. Then, once the group is offline, you can make a backup copy of your metadata repository data sets.

You can find more information in this paper: Deploying a SAS® Metadata Server to a Windows Server 2003 Failover Cluster. For additional details on the CLUSTER command, see the Microsoft TechNet website.

Operating System and Release Information