Returning servers to a cluster

Last Updated : May 06, 2015 |
Prolog information
Metadata
Keywords:
Special consideration must be made when returning certain media servers back to a cluster after they have been out of service for some time. There are two master Content Stores in every cluster. Servers with the role of Primary, Secondary and Backup contain master Content Stores. It is necessary to delete the content from a master Content Store that has been removed from service, before it is returned as a member of an active cluster. This prevents the re-appearance of deleted content that can still be present on the Content Store of a Primary, Secondary, or Backup server that was removed from service for some time.
You can use one of the following methods to delete content from an out-of-service Content Store before returning it to a cluster. Ensure that the server is isolated and not connected to the active cluster while performing these procedures.
  • Uninstall the media server without preserving data, and then reinstall the media server. You can use a backup file to restore the Configuration Data, but do not restore the Application Content data. The newly installed media server has an empty Content Store.
  • Use the Element Manager Media Management tool to remove all the application Namespaces. Restart the media server to run the deletion audit and remove the content.
  • Use another provisioning interface that interfaces with the Content Store Web Services to remove all the application Namespaces. Restart the media server to run the deletion audit and remove the content.
When the server is returned to the cluster, the latest content from the peer master Content Store synchronizes automatically.
It is not required to delete the content from an out-of-service Content Store on a server with the role of Standard. Content Stores on Standard servers are not masters and will automatically delete obsolete content when they synchronize the latest content from one of the master Content Stores in the cluster.