Attachmate Worldwide  |   Contact Us  |   The Attachmate Group
Extend. Manage. Secure. More than 30 years in the business. Over 65,000 customers.

Technical Notes

Solutions If Your Master Server Goes Down
Technical Note 2373
Last Reviewed 30-Jun-2011
Applies To
Reflection for the Web 2014 (All Editions)
Reflection for the Web 2011 (All Editions)
Reflection for the Web 2008 (All Editions)
Reflection Security Gateway 2014
Summary

This technical note outlines solutions you can use if your Reflection for the Web or Reflection Security Gateway master server goes down in your replication environment.

Potential Solutions

If the master server goes down, there are two possible courses of action:

  • Restore the master server.
  • Create a new master server.

See Technical Note 2174 for detailed information about configuring master and slave servers.

Restore the Master Server

If it is possible to restore your master server within a short period of time, this is the easiest course of action. Be sure to restore the masterís ReflectionData directory to the state you want to have replicated to all the slave servers. For example, you may need to restore the masterís ReflectionData to the most recent backup, and then make additional configuration changes to the master before you enable the slaves, so that the slaves will replicate the correct master server configuration.

Create a New Master Server

Note: When you create a new master server, all servers in your replicated environment take on the new master serverís configuration, so be sure that your new master server is configured the way you want all your servers configured before you convert any server to a slave server. You may want to use the most recent masterís ReflectionData directory backup as a starting point.

To change the role of a server to master in a replicated environment, follow these steps:

  1. Convert all servers to standalone.
  2. Convert the desired master server from standalone to master, being sure to add all the slave servers in the Add Replication Slave Server section on the master.
  3. Make any necessary configuration updates to the master.
  4. Convert each desired slave server from standalone to slave, redirecting each slave server to point to the new master server in the Add Replication Server section on the slave.
  5. If your original master server is restored follow these steps to convert it to a slave server:
    1. Convert the original master server to a standalone server, waiting a minute or so for the system to stabilize.
    2. Convert the standalone server to a slave server. The new master server configuration will then be replicated to this new slave server.
Related Technical Notes
2174 Configuring Replication in Reflection for the Web or Reflection Security Gateway
2371 Concurrent Administration and Reflection for the Web or Reflection Security Gateway

horizontal line

Did this technical note answer your question?

           


Need further help? For technical support, please contact Support.